Remote Script for Behringer X-Touch

[Kik07L]

do you mind if i post your code on github with a readme link to here and ur name ?

I've been thinking about that. I've never worked with Github myself (not a "real" coder, just a curious tinkerer) but it would be cool if others could benefit from and add to the project. So sure!

okey ! i posted it on github with all the links and things to help peoples come and discuss here
here is the link : https://github.com/Kik07L/Behringer-X-Touch-for-ableton and i will keep it updated with all the updates you make here
( sorry for my bad english lol )
have a good day !

[RobrechtV]

Excellent!! Looking great!

Is there a way to include the XtouchXT part? It's in the other folder in my Dropbox, just a small extra script you need if you want to use extender devices. Or maybe it's already there and I didn't see it?

[Kik07L]

Excellent!! Looking great!

Is there a way to include the XtouchXT part? It's in the other folder in my Dropbox, just a small extra script you need if you want to use extender devices. Or maybe it's already there and I didn't see it?

oh yes i justed added and it can be downloaded in the release section ^^

[StefanL]

Hello everyone,

I just got my behringer XTouch yesterday and already ended up here in this forum post because I'm not satisfied with the onboard Ableton Live integration (first of all the often missed colors of the channel strips and the lame channel level meters).

This is really great work, what you have realized and made available here! I would love to dive a little deeper into it and experiment myself, unfortunately I'm not particularly talented at it. Are there any links to the API/interface documentation? Where does the original source code come from?

Many thanks and best regards,
Stefan

Update: Found the original scripts and API documentation on https://structure-void.com/ableton-live ... e-scripts/

[shpongled]

Hi.

Just a very basic question please - where exactly do I copy these scripts ? I don't have a "remote scripts" folder in Documents\Ableton\User Library\...

And I just place the scripts in there and select within preferences in Live 12?

Apart from the additional functionality I am having consistent crashes when X Touch is powered up before loading Live since the most recent Windows 11 sp H24 so am hoping this more refined script will get round that AND provide a better experience.

Thanks.

[shpongled]

I found where to put the scripts - appdata\roaming\ableton\Live 12.1.5\preferences\user remote scripts\

are there any requirements to edit userconfiguration.txt ?

In Ableton settings I reference "Behringer-X-touch-for ableton-main" with default port 1 presumably? With Track/Sync/Remote enabled?

Or is the user remote script addressed differently?

So far it seems the script isn't being picked up by Live so I am missing something here.

apologies for the the basic question I have only just picked up Live after a long time...!

[StefanL]

I found where to put the scripts - appdata\roaming\ableton\Live 12.1.5\preferences\user remote scripts\
are there any requirements to edit userconfiguration.txt ?
In Ableton settings I reference "Behringer-X-touch-for ableton-main" with default port 1 presumably? With Track/Sync/Remote enabled?
Or is the user remote script addressed differently?
So far it seems the script isn't being picked up by Live so I am missing something here.
apologies for the the basic question I have only just picked up Live after a long time...!

The Folder with the script (python files) should be put in "Documents\Ableton\User Library\Remote Scripts". There is no need for editing any files.
The Name of the folder must not contain special chars like "-", as Arthur Montvidas mentoined earlier in this topic. So just use "XTouch" as folder-name. After this you choose "XTouch" under Link, Tempo & MIDI instead of MackieControl and the X-Touch as device/input.

Apart from the additional functionality I am having consistent crashes when X Touch is powered up before loading Live since the most recent Windows 11 sp H24 so am hoping this more refined script will get round that AND provide a better experience.

I also have this phenomenon, but only if the “Remote Scripts” folder exists or has been created. It does not occur for me before or otherwise.

[RobrechtV]

Apart from the additional functionality I am having consistent crashes when X Touch is powered up before loading Live since the most recent Windows 11 sp H24 so am hoping this more refined script will get round that AND provide a better experience.

I have this too, consistently, so – unfortunately – the custom script won't change that. It's annoying and I hope Ableton will be able to fix it!

I also have this phenomenon, but only if the “Remote Scripts” folder exists or has been created. It does not occur for me before or otherwise.

Ah, interesting, I've had the “Remote Scripts” folder for a long time so I didn't know that made a difference!

As for installation, StefanL explained it well. You can just put both of the folders from my Dropbox link in the “Remote Scripts” folder. XTouch is for the standard Behringer X-Touch, XTouchXT is for the Extender. Both scripts should then show up in the Control Surfaces drop-down menu in the MIDI settings. Select the appropriate script, then the device in both the Input and Output fields next to it.

StefanL, the Live Object Model is a good place to start! The script was adapted by Arthur Montvidas based on the original Mackie Control script. I remember there was a download somewhere of all the factory included scripts but I don't remember where I found that. (Edit – you found it already )

So basically the python script runs in Live, interacting with Live on the one hand through the API, and with the XTouch hardware on the other hand through MIDI SysEx messages. There is very little documentation available on the SysEx side of things, unfortunately. Most of it follows the Mackie Control protocol, of course, which is a little more documented, but Behringer-specific things like the colored scribble strips are hard to track down. I've looked everywhere for a way to invert the LCDs, for instance, which is supposedly possible in Xctl mode (I was hoping to use that as a way to identify group tracks), but I don't think it can be done in Mackie mode.

[jellybelly57]

Thanks to all that have contributed and provided updated scripts for the Behringer X-Touch/Ableton integration.
This makes an expensive piece of kit much more value for money than the default script.
I am still learning Ableton and the controller but already can see it is worth it's weight in gold.

Well done!

[shpongled]

Hugely appreciate responses from @RobrechtV and @StefanL but I still can't get a response from my X Touch in anything other than Mackie Control mode.

I have flipped the X Touch to "HUI" and "usb".
The python remote scripts are exactly where you suggest current user\documents\Ableton\user library\remote scripts\XTouch.
And Live options are set as Behringer-x-touch-for-ableton-main checked track/sync/remote both input and output.

X Touch just entirely blank.

Can anybody see what is wrong here?

Live updated to 12.1.10 - no difference to this issue.

Thanks again to both.

[jellybelly57]

Dear shpongled.

I'm no expert but the updated X-Touch scripts need to be here: C:\ProgramData\Ableton\Live 12 Standard\Resources\MIDI Remote Scripts or wherever your Ableton application resides. Here you will find a whole list of compatible controllers including the default Mackie scripts.

Hope this works for you

[jellybelly57]

Hello All

I have an X-Touch and Ableton and have updated to the coloured scribble scripts which are great! I would like to use a footswitch with the X-Touch to be able to Start/Stop Recording whilst holding a guitar etc. The X-Touch has 2 sockets for a footswitch but they don't appear to do anything. I managed to map the footswitch via the Ableton edit Midi map but this has to be done per project and would be a pain if you have several things mapped.
I was wondering if our clever friends out there could include this in the next script?

Meanwhile I have managed to achieve a workaround by using ClyphX and a lot of trial and error. If anyone wants any further info on what I did, please let me know.

[shpongled]

Hi.

and thanks for your reply @Jellybelly57

That's a rather different path to where the XTouch scripts currently reside - I initially followed the path in this - https://help.ableton.com/hc/en-us/artic ... ace-script. But that didn't work.

And then another copy in documents\Ableton\user library\remote scripts\ as per advice here.

Looks like neither are being referenced (but the latter has "Behringer-X-Touch-for-ableton-main" scripts in there)

So I now copied to "C:\ProgramData\Ableton\Live 12 Suite\Resources\MIDI Remote Scripts" and as you say behold the other midi scripts for other gear.
So I got optimistic and copied both XTouch and Behringer-X-Touch-for-ableton-main folders to that location and restarted. Still nothing

I am correct setting the XTouch firmware to HUI and USB?

I am going to get this going - it sounds like its well worth it!

[jellybelly57]

Hello shpongled.

Your X-Touch needs to be set to Mackie Control (MC) mode and the Ableton midi control surface to the updated X-Touch scripts. This is mine but please ignore the highlighted entry.



Here is how to change the X-Touch Mode:

To set the mode on a Behringer X-Touch controller, turn off the device, then press and hold the "Select" button on channel 1 while powering it back on; use the rotary encoder on channel 1 to choose the desired mode (like Mackie Control or HUI) and then release the "Select" button to confirm the change.

Please let me know how you get on - You are nearly there!!

[shpongled]

You my friend are a star! Yep that was it.

I knew how to switch between modes and had tried both HUI and MC but at that time my scripts weren't in the correct place - obviously they are now and at the path you specified.
I somehow convinced myself that the scripts weren't using Mackie mode - hopelessly wrong there! In my defence I was feeling pretty rough with strep throat and normally my approach is a lot more engineer-like. But I just wasn't thinking straight....

VERY grateful for your help - you are a credit to the forum .

I will now dig in and take better advantage of the XTouch which has already been a really useful tool - about to get better.

Thanks again.,