I use a slider of my MIDI controller to generate as output for example CC#07 from 0…127.
Moving the slider in Webconf I can see the generated values in Zynthian.local/ui-midi-log
Now when I add a MIDI filter, for example MIDI Scale CC value , I would like to see the trasformed values.
You can’t. The processor / chain’s MIDI output are not available in the MIDI log.
Let me think about it and open a feature request in our issue tracker
I written the previouus question because I can’t understand how MIDI Scale CC value works. Mayby it could be useful also to other users.
As example I have an instrument chain with EPiano → Calf Rotary Speaker.
Calf Rotary Speaker has 6 Speed Modes: Off, Chorale, Tremolo, Hold Pedal, ModWheel, Manual
Assigning a CC to this parameter, the total range (0..127) should be split in 6 ranges
I would like to use a slider with CC#84 to toggle between Chorale and Tremolo so I add a MIDI-FX using MIDI Scale CC value and I assigned CC84 to Speed Mode parameter.
As the slider has a range of 128 steps and then I need to transform it to get a range of 41 steps (63-21) so:
the Value Scale should be 3,1
the Value Offset should be +22. Value Mode is set as Clamp to 0.127
but when I move the slider the Speed Mode parameter is not affected by MIDI Scale CC value.
Because the CC scale output is not being used as input for the MIDI learning subsystem. It’s simply not used at all.
MIDI CC is intercepted before reaching chains and used by the MIDI learning subsystem. For this, all CC, except pedals, is blocked (unchecked) not reaching chains.
When you check a CC num in the chain’s MIDI CC list, this doesn’t change how MIDI learning works.
Checking CC nums in this list can be useful for special cases, but you need to understand how things work.
In your case, you could create a MIDI processing chain for your MIDI controllers and then, route back the output to the zynthian router, so It can be used by the MIDI learning subsystem.
This approach has limitations but It could be enough for many use-cases.
For fully solving this, some important changes are needed, like having per-chain MIDI return ports in the zynmidirouter and modifying the autorouting code acordingly.