10-08-2025, 10:35 AM
(This post was last modified: 10-08-2025, 10:56 AM by beep.et.cetera.
Edit Reason: cleanup
)
(10-06-2025, 01:04 PM)XORadmin Wrote: OK, I connected a Midi fader (not a faderfox but I expect that makes no difference) and did set it to the mentioned channels but I can't see any problems with the Midi CC input stream.
Often but not exclusively, the problem occur when multiple faders are being pushed or turned down.
Quote:Just as a question, you are using one of the basic midi interfaces, not the multi-IO, right?
Yup! It's the old school IO-Expander with DIN MIDI.
Quote:Lets investigate more deeper:
In the mappings you can see your current Midi CC values (range scaled to 0-4095). Check out the current value in the mapping screen of CC29 and CC24. Then change C29 until you think it happen again. Go back to the CC24 value and see if it has been affected in a way (slight changes are always possible caused by fader precision of course, but that shouldn't cause your mentioned problems).
I did that, and it does. :o Hence this detail below.
Quote:It adds a specific value to different channels (ie. CC33 will be set to a value between 0830 and 0930)
Quote:So it is interresting to see if the midi input stream does really affect others or if it might be something else after the Midi input internally, either with the mappings processing or further in the CV16 stream.
This is not happening in the CV16 stream. It sets a CC value to X, so the volume on my Assimil8or, controlled by CC out, is affected as well - (MCON section of mappings)