AZSlow

Thanks Alexei
I thought I had checked that but I will double cheeck tomorrow and let you know.  Its totally possible I missed it

Hi Don,

please check that in MCU XT preset you initiate communication with XT, not MCU.
So check that "Prod. spec. send" "LC/MC/C4 Hello" Action has "MCU XT" parameter set.
This parameter should control all following SysExes ("MCU" = 14, "MCU XT" = 15).

I don't claim there is no bug, it can happened I mess something in co-operation mode. But as safety responsible at my mothers work was always saying (~60 years ago...): "before starting to fight with the fire... check there is a fire..."

Hi Alexei
I know most people are not using AZCTrl with Mackie MCU but I still prefer it because of how I have configured it.  Recently I added an MCU XT to my setup and modified my plugin using the "co-operation mode" (Master-slave).  Everything is working fine except I cant write to the XT LCD Screen.  I'm pretty sure this is due to the fact that you are not sending the correct device ID for the XT to accept screen updates with the LC/MC/C4 LCD command
Here's an example of MCU LCD update sysex:
F0-00-00-66-14-12-54-72-61-63-6b-20-31-F7
for  XT this needs to become:
F0-00-00-66-15-12-54-72-61-63-6b-20-31-F7
Any chance you could fix this small issue ? I would really like to keep using AZCtrl/
thanks
Don

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.

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.

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.

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.

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.

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!

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).