X Touch XML Scripting

[TimC340]

Yeah, the V-1M is huge for no great capability advantage over the P-1M other than a ninth fader, a decent sized scroll wheel, and more touchpads! Touch wood, I've had no issue with my Icon controllers and I do prefer the workflow to what I had with the Behringers (I had both the X-Touch and the X-Touch One (two different computers)).

 

[Amillio]

Yeah, the V-1M is huge for no great capability advantage over the P-1M other than a ninth fader, a decent sized scroll wheel, and more touchpads! Touch wood, I've had no issue with my Icon controllers and I do prefer the workflow to what I had with the Behringers (I had both the X-Touch and the X-Touch One (two different computers)).

I’m kind of a sucker for the “studio console feel” since I was a kid. You’re probably right though. It’s just bigger compared to the other units they offer.

I may consider one if I can get one for a steal. Or I maybe I wait to see what midi 2.0 has to offer to controllers. I’ve also been contemplating building one myself that does everything but a better universal protocol is needed other than mackie and needs to be adopted.

 

[TimC340]

I got my P-1M from Amazon as a 'refurbished' unit, with full manufacturer guarantee, for around £300. I bought the meter bridge, new, separately. I got the P-1 Nano from Bax with meter bridge last month for £250.

 

[bassface]

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.

Sorry bit confusing...the file that i have modified to change the x touch behavior to my requirements is an XML file
do i have to add something to this?

 

[Amillio]

I got my P-1M from Amazon as a 'refurbished' unit, with full manufacturer guarantee, for around £300. I bought the meter bridge, new, separately. I got the P-1 Nano from Bax with meter bridge last month for £250.

That's not a bad price at all.

 

[Amillio]

Sorry bit confusing...the file that i have modified to change the x touch behavior to my requirements is an XML file
do i have to add something to this?

Adding the color functionality isn't as simple as adding some things to the XML. You'd have to modify the javascript files as well. So for example, if you took the stock Mackie Control script files and only made changes you wanted to the XML file, that would not be enough to just add color functionality from my experience.

The XML is final layout for the controller. The javascript files are responsible for functions like tracking the channels in focus, matching the closest color, defining the available colors, sending the sysex messages that the x touch understands to change to color, resetting the lcds to "white" ( or the light blue that we all know so well ) when you close a session or enter plugin mode.

It took me a lot of trial and error to figure it out but you can do it. The other thing is there's really no place or set of script files to start from. If your script that you're using now is using the mackie protocols that won't work for color.

The good news is if, if you are just using a stock mackie script where you only modified the XML. I could convert that from mackie control protocol to a presonus javascript control surface protocol with the files that I currently have. Or you can try and modify the script files I sent you and get it to work from there.