#1582

this is not normal for standard norns*, and i can’t reproduce it with the current of the norns software. (that is, assuming i am understanding your report correctly, which seems to indicate that you cannot access any MIDI functionality without rebooting after a device is plugged. it is always helpful to be specific about what actions you took, what you expected to happen, and what actually happened.)

what i’m seeing is:

  • hotplugged devices are immediately usable/mappable, are automatically assigned to open device slots in SYSTEM > DEVICES > MIDI, and are immediately available as selections when manually assigning those slots.

  • devices that are already plugged on boot are also immediately usable/mappable, and also immediately available as selections for slot assignment, but are not automatically assigned to empty slots. if you assigned them before, (or if they were assigned automatically from hotplugging,) those assignments are retained between SLEEP/boot cycles.

i did not design or implement the midi mapping subsystem, but i believe this is intended behavior and it basically makes sense to me, because otherwise you would not be able to manually clear a slot and have that decision be persistent. (though i agree it would be more intuitive if behavior at boot were more congruent with hotplugging behavior, somehow.)

i don’t know exactly what this means. did you use SLEEP, then power up, then use SYSTEM > RESET? (since v2.3, RESET will clear all system state and MIDI mappings and restart the software. it does not shut down the computer.)

in normal operation you should always just shut down with SLEEP, then pull power, then connect power again to boot up.

(* my one caveat is that the device monitoring source is one place where the fates fork has diverged, but i’m pretty confident that the midi device detection functionality is unchanged and unhindered.)

#1583

My fates works exactly as zebra described the “normal behaviour”

(The only difference I see on device monitor is on grid detection so the diy neotrelis can be recognized )

#1584

Yes - I’ve not changed anything with regards to midi devices.

However I am chasing something very strange with 16n - which is a teensy ACM device - when it is set to Serial + Midi. In this case, device recognition works fine and the device is added, but I do not get any CC information (Or any midi data) from the device.

What’s super strange to me is that the shield works just fine.

If you had any ideas why serial might be blocking midi due to some system config I’d be keen to hear your thoughts.

EDIT - Solved this by removing modemmanger

Back to @encephalitislethargi reported problem - I’ve not run into this. Could it be related to the midigrid scripts?

#1585

by sleep & reset, i mean that i: selected SLEEP in the main norns menu and then when it went to sleep, i turned off the switch on my power supply, then turned it back on.

I leave my midi devices plugged in always. none of this involves plugging or unplugging at any step.

The devices are always in their slots where i assigned them when i first power on. I can see for example my slots are: “1: usb20midi” (cable) & “2: nanokontrol2” (midi controller)
but they are not being recognized. because, when i click on them, the list for selectable devices is empty. it says “none” on each slot.

So, every single time i turn on my fates, it will show them in the main device screen, but they will not be recognized and the available list for devices will be empty.

Thus, every time i power on, i have to put it to sleep>power off>power back on Twice, sometimes 3 or 4 times even, but usually twice before the devices are actually recognized and I am able to use them. I do not have to reassign them at this point, they will still be in their slots

#1586

Ok. For debug - please get my midi- demo script and load midi-devices.lua

Then you want to have maiden open to observe its output

Then…
Please test SLEEP, power off, disconnect usb cables, power on. wait for boot to complete, connect usb cables - are

Would you list ALL the devices you have connected (midi or otherwise)?

What is the “usb20midi”? (Interface?) is that connected to other devices?

BTW - this as it reads is very wrong. RESET simply restarts the norns software. RESET is not used to reboot the device.

TO RESTART - you should select SLEEP, wait for blinking pi leds to stop blinking and the power off. Then power on again.

1 Like
#1587

Fates Users w/ 16n (v2) - quickfix

You will need to make an update to your system for 16n (v2) compatibility (or if you are running into issues with MIDI CC’s not coming through on older releases).

via SSH run the following

sudo apt-get -y remove modemmanager

then reboot.

This will get updated in the next fates/norns update

4 Likes
16n Firmware 2.0.1: release and official thread
#1588

like @okyeron says, this is very wrong, is messing up your MIDI configuration, and could be damaging to your hardware.

use SLEEP before disconnecting power

#1589

Is there a workaround for hotspot mode?

#1590

Sorry I meant “sleep”. Fixed now

I do wait until the light blinks and then powers down before switching power off. I’ve been doing this since I’ve built my fates. I only use sudo shutdown now or sudo reboot if it freezes or something like that

The usb20midi is a usb to 5 pin din cable that I use to run midi from fates to my octatrack. I have that in slot 1, nanokontrol2 in slot 2, and I also have my launchpad pro connected via usb but I don’t use that for midi much, I typically just use it as a grid. Then I have a usb keyboard too which is in the hid slot.

I will try your midi demo and maiden once I get to my fates, sorry for the delay, I have a weird schedule. I’ll try getting back here with info as soon as possible. Thanks

image
image828×825 151 KB

Usb20Midi

#1591

So you ARE running midigrid? This may be the source of your problems.

1 Like
#1592

Yes I am
I see, you still want me to try your midi demo?

If that’s the issue, then I’m ok with sacrificing that small inconvenience to be able to use my launchpad as a grid I think

#1593

okay. a usable bug report looks like this:

environment

  • (for me: vanilla factory norns)
  • (for you: fates with raspberry pi 3b+, using fates image <??>, using midigrid library, using <…?>)

steps to reproduce:

  • boot norns with nothing connected
  • hotplug USB-MIDI device
  • verify that new device is assigned and can be used in the parameter-learn menu
  • SLEEP
  • disconnect and reconnect power

expected result

  • slot assignment is persisted and device can be used / mapped

observed result

  • device is in the assigned slot, but:
  • it doesn’t show in the selection menu when assigning a slot,
  • device doesn’t work in parameter-learn menu.

i cannot reproduce the issue as described above. i get the “expected result.” this is also true after performing a RESET to clear all system state data.

i concur that the midigrid library could be your issue. it is hacking the virtual port behavior to pretend that your launchpad is not a MIDI device, but a monome grid device. so i suppose you should expect it to show in DEVICES > GRID instead of DEVICES > MIDI, but i am not responsible for this library, it is not provided by monome or the core norns dev group, and i am not familiar with subtlelties of its intended behavior or known issues.

3 Likes
#1594

Yes please. You can DM me details if you want to take it off thread.

The important thing is is we need super detailed information to be able to offer any useful suggestions for troubleshooting.

1 Like
#1595

Could this be related to the problem i was having sending cc from my teensy midi controller into fates?
Thanks!

#1596

Maybe… If your controller was set to serial + midi.

#1597

thank you all for this, it is invaluable in this time. every few days i install something new and it is like buying a completely new piece of gear. i haven’t even installed Orac yet! a heartfelt thanks to monome and the whole community of software and hardware folks, this little world provides me with so much hope.

4 Likes
#1598

Nope, just midi :frowning:

Got to test again

#1599

Okay, built my Fates, Pi4 installed, flashed the latest image (20200218) using Etcher. It works! Hook up to wi-fi, ssh in, try to expand the filesystem. I get “There was an error running option A1 Expand Filesystem.” I have reset, turned off, etc, and am still seeing “Disk 0M.” Any ideas?

#1600

Did you read all the install instructions? :stuck_out_tongue:

under https://github.com/okyeron/fates/blob/master/install/norns/Norns_disk_image_install.md#expand-filesystem

If this errors and says the filesystem can't be resized, try the following from the command line:

sudo raspi-config --expand-rootfs
sudo resize2fs /dev/mmcblk0p2

Then reboot
1 Like
#1601

Oh man, obviously didn’t read all the instructions. Thank you! That worked.

1 Like