thats fine in my case
(and preferred actually)
My problem is it’s not forwarding the midi to the correct midi output. So when I’m recording I can’t hear what I’m playing.
I just dived a bit deeper in it.. There’s some code in zynthian_gui_patterneditor.py that tries to automagically set the active chain based on the midi channel of the zynpad
That’s where the problem is!
# Set active the first chain with pattern's MIDI chan
I have 1 track, for clock purposes (see: Using Zynthian 5.1 with external synths, midi chain, clock and transport duplication issues - #8 by rv5 ) that is currently configured to “ALL” channels. Even though it doesn’t need a channel, it’s just for clock.
For some reason, to automagic chain selection prefers that “ALL” chain over chains with specific channel. Even if I put that “ALL” chain at the very end, it will always select that one:
I set it to channel 16 (which is currently unused) and BAM, it works now as it should ![]()
But.. how to fix this properly..
- A setting to disable automagic chain selection? (edit: actually, no, this is very useful..)
- More magic code to prefer specific channels over “all” channels?
- Allow a chain to not have a channel (that would be great, but might break things?)
- In my case, I could probably get rid of the “CLOCK” chain and instead remove the Midi Event Filter on one of my MIDI chains. Screws with my head but would work. EDIT: works fine so far
- Something else?
