Remote Script for Behringer X-Touch

[RobrechtV]

Hey Kik07L, thanks so much for reporting, great to hear it's working well!

About the swapped DISPLAY and GLOBAL VIEW buttons: I though at the time that it made more sense that way, grouping GLOBAL VIEW with other buttons that control "screen options" (show/hide browser pane, device/clip view, session/arrangement view). But there are two disadvantages: the DISPLAY button has no LED (not a bug, just a hardware restriction) and the swap breaks muscle memory for those who already used those buttons. Maybe I underestimated that. So I would definitely consider rolling the change back if you think that would be better.

[gregjar]

Alright, that's it, I'm working on a new feature.

This looks like it will completely replace the expensive extra thing I'm thinking about buying, the Melbourne Instruments Roto-Control. ))
I'll try!

[RobrechtV]

Haha! I can't make your knobs wiggle but I hope macro mode works for you!

[gregjar]

Haha! I can't make your knobs wiggle

It is not necessary to physically rotate, it is enough for the LEDs around the knob to light in the required position! ))
this is just optical feedback. Rotation does not bring any other benefit.

[Kik07L]

Hey Kik07L, thanks so much for reporting, great to hear it's working well!

About the swapped DISPLAY and GLOBAL VIEW buttons: I though at the time that it made more sense that way, grouping GLOBAL VIEW with other buttons that control "screen options" (show/hide browser pane, device/clip view, session/arrangement view). But there are two disadvantages: the DISPLAY button has no LED (not a bug, just a hardware restriction) and the swap breaks muscle memory for those who already used those buttons. Maybe I underestimated that. So I would definitely consider rolling the change back if you think that would be better.

oh... it has no led ? that's sad but not that problematic, rn i start to get confortable with it this way no need for me to change that back ty !

[RobrechtV]

New feature, based on an idea from j-cuc: Single Send mode. It allows you to choose a single Send/Return channel and assign its Send levels on all tracks to the respective rotary encoders.

Still in beta (but seemingly working well), direct download here.

The default Sends mode, activated by pressing SEND in the Encoder Assign section, assigns the Send levels for all Send/Return channels for the current track to the encoders. For example, if your project has five Send/Return channels (A-E), pressing SEND will activate the first five encoders to control Sends A-E for the current track.

The new Single Send mode does the opposite: it assigns the Send levels for one selected Send/Return channel to the encoders across all tracks. You can, for instance, select Send/Return channel B to see and control its levels for all tracks all at once.

How it works:
- Press SEND to go into normal Sends mode.
- Press SHIFT + rotary encoder to select one of the Send/Return channels.
- The Send levels for the selected Send/Return channel will now be displayed across the scribble strips for all tracks and can be controlled using the rotary knobs.
- The scribble strips light up blue and the SEND button blinks to indicate Single Send mode. The 7-segment Assignment display indicates the currently selected Send/Return channel (e.g., sB).
- You can advance to the previous or next Send/Return channel directly by pressing the EQ and INST buttons (they will light up to indicate whether there are more available).

Notes:
- Pressing one of the rotary encoders without SHIFT still works as before, resetting the current parameter to its default value.
- As in all other Encoder Assign modes, you can press FLIP to swap the encoders with the faders, and use the faders to control the Send level for the selected Send/Return channel across all tracks.

[j-cuc]

fantastic work! highly appreciated!

[j-cuc]

Say, I have a question. I find myself constantly in need to control just one parameter per track that is essential to the track. However, it seems not possible to use the encoders on the x-touch/-extender for that. If I assign the parameter via regular MIDI control… all encoders of the same relative track on each of my x-touch will control that parameter. I would love for a solution/page/setting that allows the assignment of the encoder to an arbitrary parameter (of that track).

For anyone interested in such per-track solution: ya_MixMod allows you to “catch” UI elements of a track to control anything. Additionally, if you switch a track to split-stereo mode (via the context menu), the X-Touch pan encoders still function as modulation sources — even though they no longer affect actual panning. This frees up the pan encoder to control whatever you need on that track.

ya_MixMod is available for free here: https://yarhammer.gumroad.com/l/knpmy

Of course, a script-side solution with parameter names, etc., would be even more desirable. And what @RobrechtV is working on — a centralized macro control mode — is also looking awesome. Thanks to his work things just keep getting better, and the X-Touch hardware is having a real second life.

Cheers!

[RobrechtV]

For anyone interested in such per-track solution: ya_MixMod allows you to “catch” UI elements of a track to control anything. Additionally, if you switch a track to split-stereo mode (via the context menu), the X-Touch pan encoders still function as modulation sources — even though they no longer affect actual panning. This frees up the pan encoder to control whatever you need on that track.

That's a cool approach actually. The drawback being that you don't get parameter names, indeed. But it looks very useful, and not just for us X-Touch users.

I haven't forgotten about Macro Control mode! Still not sure why locking doesn't work for you. Apart from that, there's a couple of things I want to figure out before I wrap it up as a new release together with the new Single Send mode.
- How can I make sure the Macro Mapper device (a customized rack of M4L devices) works for everyone? My laptop hadn't updated to Live 12.2 yet: if that's the reason I couldn't load it there, that would potentially affect some other users too.
- I'm thinking about a way to implement rack snapshots. That way you could save the current state of everything you've mapped to the macro controls and even flip through different snapshots. Although I might keep that for a later release.

[Kik07L]

hey ! i have a suggestion from my discord server from an user for some features :

"I found your very cool X-Touch Custom Script for Ableton Live 12! Thanks a lot for that!

I have one suggestion that would make me very happy:
when in Send mode it would be really cool, if the colors of the scribble strips would be in the color of the send channels
when in Plugin mode and there is an instrument rack or audio effect rack selected, it would be nice if the scribble strips would reflect the color of the macro (or white for the default color)

Does that make sense to you? "

from TMP on my discord

have a good day !

[RobrechtV]

Good ideas! Actually I just added adaptive colors to the new Single Send mode (all scribble strips get the color of the currently selected send channel), but it would be helpful to have them in normal Send mode too. I'll look into it as soon as possible! (Edit: could take a while, as it requires shuffling a couple of things around in the code and I have a lot of work right now.)

For Plugin mode, that would be even better, but unfortunately the custom colors for macro controls are not visible to the API – I already checked because I really wanted the possibility to color code parameters in the new Macro Control mode! And it would be useful in regular Plugin mode too. I'll experiment more to see if there's an undocumented way to get them but it's not very likely.

[lectro]

Hello. Just come across this thread. all sounds great.

Does this script enable you to work on the faders panning and sends when you expand drum racks?

Just checking before I go out and buy an X-Touch.

[Inghenio]

Hello! I'm new here. I have bought a Behringer Xtouch One. After watching that my fader and the leds don't reflects ok the values and after searching a lot... I have found your script.
The problem of the fader is the same, the scale on the Xtouch I think is wrong. 0dB on Ableton is 5dB on the scale showed in the controller.
By the way, I have downloaded your script and configured it with Ableton, but what mode should I choose on my Xtouch one? I only apreciate at the moment the changes on the led vumeter.
I have read a little the forum, but I can see that the buttons Shift, etc... are not available on my touch one. What's the alternative or how can I access to the configuration that the "script" allows us on the Xtouch?

[RobrechtV]

I don't have an X-Touch One, so I can't test how/whether the features of the script translate to that device.

There's no user-facing way to easily change button assignments as they're defined in code, but you could try editing the file Consts.py (you could do that with a simple text editor). If you switch, say, the definition of the SHIFT button with that of the SCRUB button, it might work (but you lose the SCRUB button, of course). Try it like this (search and leave the definitions in place but change the values):

Code: Select all

SID_MOD_SHIFT = 101 # changed from 70
...
SID_JOG_SCRUB = 1010 # changed from 101

For the regular X-Touch, the script works with MC (Mackie Control) mode.

The scale discrepancy on the faders is caused by the fact that the scale graphic on the X-Touch goes to 10, while Ableton treats 6dB as its maximum. Can't be helped, I'm afraid.

Does this script enable you to work on the faders panning and sends when you expand drum racks?

Haven't had time to test yet, I'll post here when I can.

[Inghenio]

I have changed the values from 70 to 101, and changed also the value of the JOG_SCRUB from 101 to 1010. But, when I save and turn on Ableton again my Xtouch One doesn't respond to any command send. Also, the display in the XTouch ONE says: No conected to Ableton. :S
By the way, I have been thinking that If we can use the buttons F1, F2 ... F6 to assign functions like: SHIFT, ALT, OPTION, CONTROL. And I was thinking also to being able to assign a F5 button for example, to assign the encoder to track send levels.
It would be amazing! But I'm not sure if it will be easier to change in consts.py.
Thank you very much