• Hi and welcome to the Studio One User Forum!

    Please note that this is an independent, user-driven forum and is not endorsed by, affiliated with, or maintained by PreSonus. Learn more in the Welcome thread!

X Touch XML Scripting

B

bassface

Member
Hi All

I have recently moved over from Cakewalk

and am so glad i did...

I have a Behringer X Touch Control Surface and

one thing (among many) i would like to learn is how to alter the MackieControlSurface XML .. I have found some YouTube clips and downloaded some already altered scripts

and by comparing them i have made some

crude adjustments to my own..

But i really need some help to understand

more fully how to make more meaningful alterations .

Thanks
 
Thanks for the reply
thats one of the videos i was refering to in my original posts..
and by examining the original examples in the folder you mentioned and the one i downloaded from that guys youtube video
i was able to make observations and crudely alter my own script...
but i want more than that...i want to understand the syntax so i can modify
my script to include more buttons on my x touch and also maybe creat some macros
Thanks again for responding
 
The Behringer BCF2000, BCR2000, FCB1010, UMX and Korg nanoKONTROL and nanoKONTROL 2 device files provide plenty of syntax examples (buttons, faders, encoders, transport, etc.) for everything you need.
 
Thanks for that....
but unfortunately my powers of observation are at their limit..
I need some clear examples....i.e on x touch How do i change
the fader bank button (x touch) to also change the page view in my studio one console (combine two commands)
(also a mentioned in that youtube clip)
Or how do i change the assignments of buttons on the x touch across the "global View" line
which in the mackie script are referred to as "radio control" and have different syntax to the
the other buttons (command control) ..
please feel free to treat my like a complete newbie ..coz i am
 
bassface said:
Thanks for that....
but unfortunately my powers of observation are at their limit..
I need some clear examples....i.e on x touch How do i change
the fader bank button (x touch) to also change the page view in my studio one console (combine two commands)
(also a mentioned in that youtube clip)
Or how do i change the assignments of buttons on the x touch across the "global View" line
which in the mackie script are referred to as "radio control" and have different syntax to the
the other buttons (command control) ..
please feel free to treat my like a complete newbie ..coz i am
Click to expand...
You could DL the Mackiecontrolsurface.xml that is linked in the above video comments and try it. Rename the current default from *.xml to *.OLD and back it up FIRST.
I'm not sure that there is a way (yet) to bank through the faders on the X-Touch AND horizontally page in the console view with one button in the xml script, I'm working on having a macro in S1 do it by assignment to a function button on the surface. If I have any luck, will report back.
 
Tthanks....
ive done all that and also been successful in assigning a few things myself...
but some of the buttons seem to have a different syntax as i have not been able
to re assign them....The F buttons we know are easy...
its the ones the macro called "radio buttons"
that are proving difficult.
 
I've had a bit of a dive into the xml with xtouch and it would appear the implementation in S1 is limited to the basics. No colored strips, no parameter pages for plug ins (limit of 8) etc.
It's pretty easy to map the buttons to do any commands you want that are available. I've got mine running pretty well, no unused buttons, lights working with a few more options using the modifier keys and some custom stuff I like to use in S1.
 
Hey guys, does anybody know how to trigger macros from the mackie xml?
I tried multiple things but nothing works for me.
What I tried so far
Code: 
<Command control="inputsButton"       command.category="Macros" command.name="M2"/>
<Command control="inputsButton"       command.category="Macros"  command.group="MyMacros" command.name="M2"/>
<Command control="inputsButton"       command.category="Macro" command.name="M2"/>
<Command control="inputsButton"       command.category="Macro" command.group="MyMacros" command.name="M2"/>


MyMacros is the macro category name I assigned in S1.

Does anybody see what I'm doing wrong? TIA
 
Cypher said:
Hey guys, does anybody know how to trigger macros from the mackie xml?
I tried multiple things but nothing works for me.
What I tried so far
Code: 
<Command control="inputsButton"       command.category="Macros" command.name="M2"/>
<Command control="inputsButton"       command.category="Macros"  command.group="MyMacros" command.name="M2"/>
<Command control="inputsButton"       command.category="Macro" command.name="M2"/>
<Command control="inputsButton"       command.category="Macro" command.group="MyMacros" command.name="M2"/>


MyMacros is the macro category name I assigned in S1.

Does anybody see what I'm doing wrong? TIA
Click to expand...
have you tried mapping it to one of the F(keys) on the xtouch to confirm it works from within S1? If so then it should work as per the first line you posted. Of course this depends on how your entering the line in the xml and if there is another command set to the button somewhere else or if your using modifiers for the button.
 
when I assign them on the F-Keys on the external device overlay they work as expected.

I can also assign any other function to the button in the xml and it works, just not macros.
 
cookie70 said:
I've had a bit of a dive into the xml with xtouch and it would appear the implementation in S1 is limited to the basics. No colored strips, no parameter pages for plug ins (limit of 8) etc.
It's pretty easy to map the buttons to do any commands you want that are available. I've got mine running pretty well, no unused buttons, lights working with a few more options using the modifier keys and some custom stuff I like to use in S1.
Click to expand...
Hi, can you Share your XML file?
 
I had an X-Touch - still got the X -Touch One on my reserve rig. The X-Touch never had a Studio One specialist script, and I never found one online. I had it working with track colours and plugin control for FL Studio and it worked really well, but not for S One. The X-Touch One, otoh, has a specific Studio One mode and works well (still no track colours though!). I replaced the big X-Touch with an Icon P-1M, on which I get all the features I wanted plus a Stream Deck-alike custom panel of controls- and its about a quarter the size.
 
So as of a couple of days ago I have been able to get the color screens to work on the xtouch with studio one. The scripts that I had to use to make this happen were the Presonus Faderport, the ICON script from Paul Henty and the QMAP script from Modern Idiots.

The Faderport script is a Javascript based script where as the Mackie script does not support certain things.

The QMAP script is freaking awesome and integrates pretty deep with studio one. More hands off the mouse and keyboard. I bought it the moment I came across it a few years ago but sadly it does look like Modern Idiots isn’t still active. Originally the sad part was the in S1v6 they updated the controller scripting and the QMAP script wouldn’t work with anything past S1v5. I was actually able to rewrite it to make it work with S1v6 and was thinking about the color screen functionality so I went down the rabbit hole.

The Paul Henty script was the one that took the RGB capability from the Faderport script and modded it to work with the new color LCD screens for the ICON series controllers.

So....

I now have a working QMAP based script for the X-Touch that has working color scribble strips that picks the closest color on the xtouch ( which only has 7 colors ) to match the channel color based on how the human eye perceives color. I also modded how the track names are shortened and abbreviated ( concatenated ) to make it a bit better to read and have been playing with some other small functionalities.

I want to share the QMAP script with everyone but I also don’t want to take any credit for all the heavy lifting that Modern Idiots and Paul Henty did. You would also need Bome Midi Translator because some of the buttons on the xtouch actually work as keyboard commands. If anyone is interested send me a PM.

If you have a ICON controller then visit Paul Henty's website and get the scripts he has for those controllers and lets get some colors on our DAW controllers
 
hey Amillio ..
i have the files you generously made available to me but since my initial request last year
i have hacked the the studio one supplied files to get the x touch to generally do what i want....
my question is can i use your modded ICON file that enables colored scribble strips
with my exiting hacked file?
if so how would i do that?
thanks
 
Last edited:
Amillio said:
So as of a couple of days ago I have been able to get the color screens to work on the xtouch with studio one. The scripts that I had to use to make this happen were the Presonus Faderport, the ICON script from Paul Henty and the QMAP script from Modern Idiots.

The Faderport script is a Javascript based script where as the Mackie script does not support certain things.

The QMAP script is freaking awesome and integrates pretty deep with studio one. More hands off the mouse and keyboard. I bought it the moment I came across it a few years ago but sadly it does look like Modern Idiots isn’t still active. Originally the sad part was the in S1v6 they updated the controller scripting and the QMAP script wouldn’t work with anything past S1v5. I was actually able to rewrite it to make it work with S1v6 and was thinking about the color screen functionality so I went down the rabbit hole.

The Paul Henty script was the one that took the RGB capability from the Faderport script and modded it to work with the new color LCD screens for the ICON series controllers.

So....

I now have a working QMAP based script for the X-Touch that has working color scribble strips that picks the closest color on the xtouch ( which only has 7 colors ) to match the channel color based on how the human eye perceives color. I also modded how the track names are shortened and abbreviated ( concatenated ) to make it a bit better to read and have been playing with some other small functionalities.

I want to share the QMAP script with everyone but I also don’t want to take any credit for all the heavy lifting that Modern Idiots and Paul Henty did. You would also need Bome Midi Translator because some of the buttons on the xtouch actually work as keyboard commands. If anyone is interested send me a PM.

If you have a ICON controller then visit Paul Henty's website and get the scripts he has for those controllers and lets get some colors on our DAW controllers
Click to expand...
Well done! I already use Paul’s scripts for my P-1M and P-1Nano. They work very well, though I need to get around to re-mapping the touchpads to suit my workflow.

The X-Touch is a great device, but it was a bit too big for my desk!
 
bassface said:
hey Amillio ..
i have the files you generously made available to me but since my initial request last year
i have hacked the the studio one supplied files to get the x touch to generally do what i want....
my question is can i use your modded ICON file that enables colored scribble strips
with my exiting hacked file?
if so how would i do that?
thanks
Click to expand...
Hey buddy. So basically you would have to have your script as a JavaScriptController.

So if you look in the folder that your scripts are in there will be a .device file. If it says mackie in there then all then all the scripts need to be rewritten like the faderport8 scripts for example.

You could probably have AI do the conversion for you. Once you have the scripts working the way you want them to you add the color functionality in. It’s all hit and miss since there’s no official documentation.

Can it essentially be done in an afternoon? Yes absolutely!

If you feel comfy shooting me over your controller scripts I may be able to implement the color functionality for you easily depending on how it’s currently set up.
 
TimC340 said:
Well done! I already use Paul’s scripts for my P-1M and P-1Nano. They work very well, though I need to get around to re-mapping the touchpads to suit my workflow.

The X-Touch is a great device, but it was a bit too big for my desk!
Click to expand...
Thank you.

I’ve been playing with the idea of getting an icon controller for a few years now but I’ve personally seen and seen people online having quality issues with them like faders and pots stop working correctly or completely after a while or even out of the box brand new or issues with freezing or lagging.

So the idea of buying a thousand dollar controller and replacing the xtouch to have hardware issues kinda bothered me. Now with the color functionality I have and the QMap working on newer versions of studio one I may be cool with my xtouch until we start seeing midi 2.0 controllers that rival Avid Eucon stuff

I would have almost the same size problem. The xtouch fits on my desk with my computer keyboard in front but if I get the v1 it’s a few inches deeper and I’d have to replan my desk layout as there would be no room for my keyboard in front.
 
You must log in or register to reply here.
Back
Top