I have to check this the next days.
Some of your request (select button habit and display color) will work if I would use the Midi instead of the MCU mode.
By using the Midi mode the high resolution (16384. to 128 steps) of the fader would get lost.
Script is working well (except the 4 bypass buttons, but that doesn’t really matter to me). The only thing I’d like to figure out is when I open a project it, the x-touch one doesn’t do the autobank thing unless I use the channel buttons to first select the track. If I simply select the track with my mouse, it doesn’t see the channel, if I use the channel buttons, it does and then after that I can use the mouse to select the channel and it sees it. It’s like I have “load” the tracks using the channel button first by manually cycling through them first. Do you know a way around this? Am I doing something wrong?
Thank you for this script though, it really improves the X-touch one!
Do you use it with Mackie custom mode?
I have no problems with auto banking, it perfect follow selection by mouse clicking on track etc. Do you remap next\prev channel buttons in xtouch settings? Tested with latest 12.0.7 and 13.0.10
I am using it in “U” mode on the X-touch. Is that correct? I checked the start guide but it doesn’t mention “Mackie custome mode”. What is it listed as on the X-touch. Thanks for the reply!
No, I didn’t remap any buttons, I’m just using the script as is.
What is the letter on the behringer, so I know I’m doing it right?
Do you see how everyone is using different names for what the mode is? The other guy says Mackie Custom mode, you’re saying Mackie mode. There are several Mackie modes and there is nothing in the start guide that uses the term “Mackie Custom mode”. I have tried several modes with varying results but haven’t found one that makes everything work correctly. I would like some clarification to know if I’m using the same one everyone else is. Where is this information provided in this thread?
hey guys.
i just sold my console 1 and fader to buy the mk3 version…
being stuck without a fader to write automation i got myself the behringer AND this script.
Maybe because I have a custom logical editor presset assigned to select button, but you don’t have it, so the signal goes to the device… Try map your action for this button.
One problem I seem to have with X-Touch One scripts is that touching the fader cap will initiate writing of automation but it won’t hold that state. It’s only the movement of the fader that keeps it ‘live’.
If you are riding volume on a track and you want to hold it at a set level for a second or two, Cubase will drop out of recording it until you move again. So you have a gap where no automation was written.
If you use ‘Auto Latch’ to work around this then it doesn’t snap back when you release the fader.
Is this a setting I have missed or is anyone else experiencing this?
Hello! I’d like to know if the “master” button can be programed to the control room volume level instead. I don’t usually move the master fader in the mixer.