ah. fates might have different issues. i’m frankly confused about where the fork lives, how upstream changes are integrated, and if there are still custom patches applied to the low-level device management routines. (same code affted by PR #886.) @okyeron would be the one to ask whether one should expect fates image to include the upstream fixes from october 2019.
in any case, i’d like to see a repro case on vanilla norns / shield before opening an issue there. from eyeballing the code, it doesn’t seem like there should be issues, but i’m not sure i have an appropriate device to test. SQ-1 is pretty popular - right? - so maybe someone here can give it a quick spin to verify. (meanwhile i’ll dig around for something else that exposes dual MIDI sink endpoints.)
(folllowup 1)
ok, i did remember that i have a Beatstep Pro and dug that out. (acquired for the specific purpose of testing multiple midi ports, pffff.)
for what its worth, both ports show up on vanilla norns (in separate device slots) and i can use device 1 to produce CV output from norns MIDI output. (i don’t actually understand what role device 2 plays whe using the beatstep pro as MIDI sink - maybe it’s for drum gates or something. will see if i can figure it out or maybe someone reading this already knows the answer.)