I've spend a long time trying to overcome this limitation, but so far without success. I have controller data coming from a plugin and tried assign it to the exposed Bitwig parameters of another plugin via the learn function. But midi learn is not possible in this case, as the destination plugins knobs in its GUI as well as the parameters it exposes can't be defined as sources. The learn function doesn't work (I also would like a way to define source and destination by typing in the CC number, but there is no such option either?!)....
But its probably easier to take a midimonitor and just set it by hand... Or simply document the CCs you are using...
I verified this shortcoming using a free midi monitor plugin and BlueCat's Remote Control plugin, which allows for the creation of your own control surfaces with knobs and faders that send Midi CCs. I put the midi monitor behind the destination plugin and can verify that the CC data send go through all the way, but the learn function doesn't react to the Remote Control plugins output either.
@Tj Shredder:
You mention assignment of CCs in a midi monitor "by hand". Do you mean an extra program like MidiOx outputting to a Loopback driver? What do you mean by documenting the CCs?
Is anybody aware of a possible workaround? I tried to find the mentioned Midi Modulator but not sure what is meant by that. The free Magic Midi Modulator?
If all else fails I'll route the signal from an extra track to a loopback output.
Bitwig is a nice piece of software but in everything Midi it's much worse than Logic Audio from 1998.
Statistics: Posted by ev0lver — Wed May 08, 2024 10:06 pm