I'm attaching two files: (a) an SPP file with my current setup for using the X-Touch One with AZ controller; and (b) a PDF file with a table that shows the functions of all the keys on the X-Touch One using this preset.
In this version, I believe that all of the keys, meters, and other controls on the X-Touch One are working. I've assigned the F1 key on the X-Touch One to be the M1 modifier key found on the Mackie Controller. This provides the possibility of a second command for each key when pressed in combination with the M1 key. In version 6.0 these second functions are assigned for most of the X-Touch One keys (see table in document file for all current assignments).
A few comments on the version 6.0 preset:
a. I am using the latest version of AZ controller (0.5r8) and the current version of Cakewalk by BandLab (Version: 2018.11 (Build 31, 64 bit).
b. I upgraded the X-Touch One to firmware version 1.07 and am using it in Mackie Control mode.
c. The level "meters" on Cakewalk for the selected channel are displayed on the LED strip on the X-Touch One except when the Master bus is selected (this is also the case when using the Mackie control surface interface that comes with Cakewalk).
d. The X-Touch One indicator lights should work properly for all the transport keys and the major channel keys (record, solo, mute) and will stay in "synch" with the same indicators in Cakewalk. The indicators also work and stay in synch for the keys that toggle looping and punch-in. The lights for the other custom keys (F1-F6, and the Marker-Solo row) are not active
e. To label the X-Touch One I used the LOGIC cutout that comes with the X-Touch One and added custom labels for the F1-F6 and Marker-Solo rows of keys. The rest of the labels on that cutout are pretty accurate for the functions of this preset.
I am happy to share this preset with other users if you think they would find it useful. I'm not 100% certain that I generated the .spp file correctly, but hope you can check and verify. Other users may want to make different assignments to the custom keys, add additional modifier keys (there is coding in your original controller for M1-M4 modifiers), and hopefully expand the indicator lights. The brilliance of your work is how it makes it possible for interested end users to make these kinds of changes. Bravo!
Thank you for sharing. I will later move your post into "Presets" section.
I can not test how it works, but at least I can confirm SPP is correct.
Interesting post.
I'm also trying to use an XTOne with my Sonar DAW. Didn't realise AZ Controller cold help with that. Couple of questions though.
- What does 'M1' mean or signify for the F1 key
- How do you create a 'selection' with the XTOne as implied by
"Set Loop Times to Selection" for the Cycle button?
I do not have XTOne, but from the documentation...
F1/M1 (Modifier 1). When you use it other buttons change functionality, as in PDF.
I guess there is no key to set selection, assuming you are working with mouse as well. But as everything in AZ Controller you can add it yourself, if you need that and time time to do that.
First off thanks AZ Slow for this software, amazing stuff!
I have loaded this preset and everything works great except moving the fader on the X touch One does not change the fader in cakewalk (additionally after a few seconds after moving the fader it moves itself back to where it is for that channel in cakewalk).
But moving the fader in cakewalk moves the physical fader on the x touch one.
I do not see anything happen in the overview tab when moving the fader (but I do for any other button / knob on the device.
Thanks!
Check "Last MIDI event" (on the top). There should be (a) something when you just touch the fader (and a bit different message when release) (b) something when you move the fader.
If at least something does not produce messages, check that you have latest firmware. In worse case your device is defect...
If you see messages, let me know and I will check the preset (I do not have the device, so I can only check "theoretically". Better if you can write exact messages you see when operating the fader).
So...super late reply, sorry for that (life sometimes gets in the way). On the latest firmware and latest version of az controller & cakewalk. I see nothing in "last midi event" when moving the fader. I don't think it's necessarily a hardware defect though.
When running midi-ox I get the following data when moving the fader:
TIMESTAMP IN PORT STATUS DATA1 DATA2 CHAN NOTE EVENT
000B92A9 2 3 90 6E 7F 1 D 8 Note On
000B92A9 2 3 E6 20 31 7 --- Pitch Bend
000B9362 2 3 E6 04 32 7 --- Pitch Bend
000B9377 2 3 E6 04 34 7 --- Pitch Bend
000B938C 2 3 E6 34 36 7 --- Pitch Bend
000B93A1 2 3 E6 54 38 7 --- Pitch Bend
000B93B6 2 3 E6 74 3A 7 --- Pitch Bend
000B93CB 2 3 E6 04 3D 7 --- Pitch Bend
000B93E0 2 3 E6 48 3F 7 --- Pitch Bend
000B93F5 2 3 E6 68 41 7 --- Pitch Bend
000B940A 2 3 E6 10 43 7 --- Pitch Bend
000B941F 2 3 E6 34 43 7 --- Pitch Bend
000B9542 2 3 90 6E 00 1 D 8 Note Off
I'm wondering if the issue is the X-Touch sending the master fader as pitch bend and that is why it's not recognized?
Again thanks for the help!
Messages from MIDI-OX is what they should be. In Mackie, faders are sent as PitchBend since it is the only "simple" MIDI message which allows 14bit resolution.
Check that PitchBend MIDI message type is enabled in Cakewalk preferences. Unfortunately, these "recording" settings influence control surfaces as well.
That was the fix!!!
For anyone else that comes across this same issue:
Preferences -> Midi -> Playback & Recording
check the box next to "Pitch Wheel"
Thanks again AZSlow!
Thank you for this preset for Cakewalk. I downloaded and installed. It works perfectly in Cakewalk by Bandlab.
Thanks for doing this!
C2
Greetings. I've downloaded this preset and it seems to be mostly, if not entirely working, still, in Bandlab Sonar 2026.04 build 078.
The most important feature to add would be to have the bank automatically follow the selected track so that the fader was immediately available on any track/channel I select with a mouse.
Quote from: skullsession on May 03, 2026, 03:03:51 AMGreetings. I've downloaded this preset and it seems to be mostly, if not entirely working, still, in Bandlab Sonar 2026.04 build 078.
The most important feature to add would be to have the bank automatically follow the selected track so that the fader was immediately available on any track/channel I select with a mouse.
I don't have the device, so I can't test how good attached modification is working (if at all). But I see WAI is moving in Sonar, so it does something ;)
Please note BANK<> and CHANNEL<> can no longer work stable, since WAI is auto-moved every time you start working with different strip. It will be reset to aligned blocks (strips 1-8, 9-16, etc.).
PS. Original preset is for X-Touch One Mackie mode, 8 strips. But X-Touch One is one strip controller. To get "optimal" integration, MIDI mode should be used. No one has created such preset and I don't have the device to do so easily. So that is just to note there is theoretical possibility for better integration, bypassing any build-in (and so potentially non optimal) Mackie emulation in the device. Such preset will be way simpler, since it will deals with a single strip and with existing physical controls only. Also WAI indication will be correct (one strip in a time).
But till you are ready to invest significant time in such preset creation, just use what is there.
Thanks, AZ! I'll be able to get a look at it in a few hours. Might take me a few days to digest it because I'm really still trying to get my head around how it functions in the background. I did start noticing last night that there are setting in there for 8 channels. Now that you say this, it makes sense.
I'd love to work out a preset for this unit, specifically. I definitely could make the time if I can learn to understand it all.
I'll report back when I get a chance to try it out. Thanks so much!
Quote from: skullsession on May 04, 2026, 03:29:06 PMThanks, AZ! I'll be able to get a look at it in a few hours. Might take me a few days to digest it because I'm really still trying to get my head around how it functions in the background. I did start noticing last night that there are setting in there for 8 channels. Now that you say this, it makes sense.
I'd love to work out a preset for this unit, specifically. I definitely could make the time if I can learn to understand it all.
I'll report back when I get a chance to try it out. Thanks so much!
"Nothing looks impossible to do, till you try to do that..."
Making simple presets for AZ Controller is relatively simple. Making sophisticated presets for AZ Controller is progressively complicated...
To try with X-Touch one, switch it into MIDI mode. Then follow tutorials (in that sequence):
https://www.azslow.com/index.php/topic,9.0.html
https://www.azslow.com/index.php/topic,138.0.html
https://www.azslow.com/index.php/topic,336.0.html
Try to read the documentation, to understand possibilities.
Warning: the fader is touch sensitive, to "MIDI learn", first touch it, then press "Learn" (by other hand), then move. You will "learn" touch signal in case you touch after start learning. And don't initially try to work with fader as touch sensitive, it can be a bit challenging (till you complete tutorials, so understand monitoring, and find required Action with reasonable parameters in the documentation).
Sure as shit man...it's now auto banking to any track I click on with the mouse - and the fader is responding properly on the channels. The only fader I've seen acting strange so far is the master fader a couple times, but I can't get it to do it again. So let's give it some time.
The WIA is moving in banks of 8 when I click on a track on the console and in the tracks pane.
I've got some work to do here to get all my buttons back to what they were before this mod. And some work to try to clean up all that 8-channel info buried in there.
I'm super excited to see this working like this!
So I found the settings in the plugin on the FEEDBACK tab. I changed the WAI to Align: 1 and Track: 1 and clicked on the INITIAL box. Now the WAI just shows on the single track I've clicked on. FANTASTIC!!
You're right bout the bank and channel buttons not playing nicely but it doesn't matter since I'm selecting the tracks with the mouse, one at a time.
This is a great improvement, for sure.
WAI is a position. Width influence visual representation in Sonar (the number of strip highlighted) and has no other meaning. But internal X-Touch logic "think" it works with 8 strips, so channel buttons move to let say strip 2 in the WAI. AZ Controller get no info the controller has switched to the second strip (it think the controller works with 8+9 strips all the time).
Align:1 (in my mod logic) will move the bank to current strip. It is more "heavy" then Align:8, it has to re-send all information (about 8 strips) every time you change strip, Align:8 is not really changing anything as long as you are in the current bank. But I don't know if X-Touch auto-switch to currently chosen strip within bank (I have assumed yes). If not, Align:1 is the only way to force following.
I can tell you that this is the behavior I was hoping for out of the Touch One, regardless of whatever else noise is going on in the background. As long as I can click on a track and the controller knows where I am without having to change banks, I'm happy. And that's what we've got right now.
Next up...as limited as it would be with just one fader, one encoder and a jog wheel, I need to figure out how to control plugin knobs. Currently, I've not been able to move even one knob on a plugin.
And, even more importantly, to see if I can manipulate automation on varying parameters. So far I've only been able to use the fader for volume and the encoder for stereo balance control.
There is no corresponding buttons on device... I mean to switch into plug-in control mode.
You can re-assign something, f.e. Fx keys. Good start is to have at least "Par" and "Dyn" assigned to some existing buttons. That is for "normal" mode (default) and "ACT Dynamic mapping" mode ("Dyn"). Note there are sub-variations of these modes, if you press the button while already in corresponding mode.
Well, one fader and/or one knob is only good for something "simple", like in https://www.azslow.com/index.php/topic,206.0.html But that will need a dedicated preset for this device.
Perhaps I should just be happy this one is working as well as it is and pick up a more dedicated device to tweak knobs.