edit mappings panel cc value

[iowastate89]

I've got a trackpad controller sending x-y cc values; learning these in BW is only able to get the cc associated with the y direction.. There's no way for me to easily learn the x direction without the y messages overloading things. Is there a way I can just edit the cc values in the Mapping Panel directly or enter those manually instead of going through the learn process? The cc value in there is read only unfortunately

[monolithx]

I'm not sure to understand what you want to solve this way but, concerning CCs manual editing or any other musician friendly controller related feature, there is no way. Unless you write your own control code.

[iowastate89]

Yeah I have a trackpad controller that sends cc values of 114 (y dimension) and 115 (x). Bitwig only catches the first value of 115 whenever I physically touch the hardware trying to use the hardware learn/mapping. So there's no easy way for me to press the pad and map the 114 (y) value to what I want (I've tried a bunch of times it's just my pad seems to send 115 first and I'm not nimble enough to swipe my controller in an x-only motion). If I could just edit the cc value directly I'd be good instead of depending on their hardware learning.

I guess I can edit something at the controller level via moss' Flexi or something but I'd rather keep it in the mapping panel which would do everything I need if it could capture correctly

[iowastate89]

Ok weird, so while I can map a non-touchpad control along with my x value (and bitwig shows both), it never seems to recognize my y axis cc value. Ableton picks it up in their mapping process go figure. I was hoping to maybe map x/y both, and then just delete one of them

[monolithx]

I have reported years ago their controller config limitations. What I do is to use CC modulators on instrument track set to controller input. The only performance drawback is that modulators are continuous (hopefully they don't keep sending value if it doesn't change). Set each CC mod to the nr. that you want to catch.

This also allow to target a given device in case of multi identical mappings (using "normal" controller mode, even disabled devices receive change!).

[Tj Shredder]

XY pads always send the two values together. If you have a plugin, that can only assign a cc by learning, you can use a Midi cc device to send the appropriate cc (in your case 114). The plugin can’t distinguish the source,
The Midi modulator would also work, as you can always manually set the cc number it listens to and then modulate the parameter you want to control…

[aMUSEd]

Something I've suggested too - why is it so hard to just let people enter cc numbers manually? Same issue in Live though

[Tj Shredder]

I just described how to do that… I never had a problem to setup a cc modulation and set the cc manually. If a plugin has a non automate-able parameter and insists on Midi learn, you could just send that cc with the Midi device…
If the cc isn’t documented, you can use a Midi monitor to find out.
I would love to have a native monitor not only for Midi, but also for expressions. Its crucial for trouble shooting…

[monolithx]

There two things here, on two different underlying lanes:

- it's not possible to manually edit controllers mapping manually which is a pain for everything more than a basic controller setup.

- I don't know if modulator lane has performance drawback compared to controller lane (if it's continously modulating). And modulators are not bi-directional. Just another workaround...