BrainModular

Hi all. I'm having a very hard time getting Behringer X TOUCH MINI encoders to work properly. I have many faders and knobs that control output gain and other parameters in mi rig, they're are set from -80 to 12 dB limits. Lets say that I have a current value of -10dB which is the proper level for an instrument, and that value is stored and saved in both patch and workspace. In a live situation I may need to increase or decrease that level. In theory everything is set correctly. Behringer encoders are set to relative mode (actually has three relative modes to choose from, I have tried them all) and midi learn on Usine is set up to relative mode too. The problem is that when I reload the workspace and try to use the encoder for the fader or knob they go to the beginning of the scale limit (-80 dB) and start increasing its value from there instead of modifying it from the current value (-10 dB). Relative mode is supposed to send and read +/- 1 CC midi values, in other words increase or decrease a current value of the fader or knob. Why is this happening?. I have to say that most of the fathers and knobs are within a container and are linked to a "display number" module that can be seen in control panel of the patch, just to mention. Any help on this will be greatly appreciated.

Perhaps try with the controller and usine knob set to absolute? This is how I use my BCF2000 and it works as expected, but maybe you are looking for a different usage than absolute allows? Also just to be sure, your Xtouch midi out device is set to be as a motorized device and your midi learned control is also set to motorized? (aka midi feedback)

maybe you could try to reload the preset with a "on init" module ?

Thanks for replying. Absolute mode does not work for me. X Touch mini has no motorized controls only endless rotary encoders, buttons and one fader. i don't see how "on init" module can help

Messing around I found what apparently causes that strange behaviour of the.Knobs/faders, they cannot be attached to any other module, this is: the "display number" module was producing all the problem. I deleted it and found another way to display the value that does not interfere with the correct knob/fader behaviour. I will keep on trying this method and see if it is reliable. Frankly I really don't know technically why this happened, it would be good to know it.Thanks a lot to all.

did you have 'pass if changed' modules between your knobs and your display numbers?

I just got a pocket dial, and I ended up creating an inc button and a dec button for each knob, and triggering those from the encoders (in inc-dec mode).... that works for me. I couldn't figure out which combination of pocket dial logic and usine logic actually worked with midi learn.

hmmm, well this is not working so well for me. When the cpu starts getting loaded, the inc-dec buttons seem to stop getting data..... is a button lower priority than a fader, or something? Doesn't make sense.

I'll mess around with it more. I'm using a regular MIDI input module and filtering. Maybe midi learn would be more reliable. But I would think midi messages would be high priority.