AZSlow

Thankyou Alexey (sorry about misspelling your name)
If you need me to test anything else let me know
Thankyou for all the work you do
Don

Hi Don,

thank you for testing... After reading resulted behavior, it seems like there is "a bug".
I have foreseen multiple Mackie devices, but in several places I am just using the first one. I guess I have just forgotten really support multiple devices.

It can take some time till I make a fix. Please be patient.

Alexey.

Hi Alexei
You're right "not a bug".  However I still need a bit more advice from you if that's OK?
I tried to send the "Prod. spec. send" "LC/MC/C4 Hello"  from the XT Preset by creating a timer which should trigger the feedback  which has the command (These are the only commands in my XT preset).  I want this to happen at startup but I dont think its getting  triggered because teh XT LCD does not come "alive".
If I change the "Prod. spec. send" "LC/MC/C4 Hello"  that runs in the MCU (Master) preset, to send to the XT (slave),  the XT LCD comes alive but the MCU stays dead.  I tried to run both from (XT and MCU prod send) seuentially from the "Hello" feedback but  only the one that gets run first works. Any suggestions what I might be doing wrong ?

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.