OK I'm still discovering just how deep this thing really is - it's really dauntingly complex, but it seems like it's possible to set up everything from simple button-to-function mappings to seriously crazy macros. I haven't even gotten into the ACT interfacing stuff...

EQ, as other plug-ins, has 2 mapping modes. "Direct" with the original parameter order like in listed in Automations and ACT mapping.
 
Original Mackie Control has separate (not ACT) mapping files for plug-ins and use Direct mode only. It supports 3 modes for EQ: Multichannel, Strip and Strip Freq+Gain (on encoders and faders). AZC tries to follow the same logic. "Edit Mod" + Bank keys change "banks" of plug-in parameters. In the preset that is implemented as special State Sets which define which parameter is controlled by the first encode  for each mode (like OffEqTrS for EQ on Track is Strip mode). That is not optimal, since the order of parameter is not configurable in AZC case (no special mapping per plug-in yet).

Hi again. Thanks for trying to help me, but I'm afraid I need to seriously pore over your existing documentation if I'm going to understand it properly, and since I can't devote myself to it entirely that will take some time...
 
I'm not too worried about the native EQ functionality actually, as I find the mouse and flyout EQ a perfectly good way to edit EQ. What I'm really interested in doing is mapping the controls onto ACT parameters, ideally in banks as you say, so that it changes dynamically and displays the parameter mappings in the AZ Display. I seem to have this at least partially working here by using Assign->Dyn in the logic field, which pulls editable parameters of whatever plugin (or EQ, for that matter!) has focus into the Display and maps the bank of 8 knobs I have here (functioning as Mackie Vpots) onto the first 8 of them. But I can't find a way to access the next 8, or any after that - ideally this would function like a bank shift and let me change the group of exposed controls that the knobs are mapped to.
 
So that's what I'm working on, which I am again beginning to think will require some more time with the documentation... Unless of course you can point me to an easy way to do this... ;)  ... either way, thanks for your time and assistance!
 
quick edit... I'm making a bit of progress thanks to your hint above about Edit - Banks ... I've managed to set up a button for Edit (like a shift key kind of) which lets me use the bank buttons to move around, but they don't seem to access params 9-16 etc. - the AZ display simply displays nothing. So I haven't got it licked yet, but I'm on the way...

ACT part of Mackie Preset was not tested deeply: TouchDaw Phone does not has corresponding controls...
 
For all other modes, Parameter Offset is an absolute number. But for ACT, it is "ACT Bank". So, if in Dyn (ACT) mode you use "Edit + <Channel>" buttons, it should do what you want. But in case you use "Edit + <Bank>", it will navigate by 8x8=64 parameters. It is likely you have less then 64 parameters, so you see nothing to control once you switch by 8 "Bank"s.
 
The decision to do like that comes from the fact I have some VSTs with more than 64 parameters. So, switching by 8 AND by 64 make sense. I repeat, that was theoretical decision and I have not tested either it is really practical.
 
For Real MCU that is not a problem, it has separate "<Channel>" buttons. You can either change the multiplier in ACT parameter selection of VPots (from 8 to 1) or "Shift" from 8 to one in "<Bank>" button actions (for Dyn/ACT case only!).
 

OK that explains it perfectly, thanks! I'm sure I could have found that in your documentation at some point but I'm only able to poke away at this in odd moments just now. I've set up an Edit button and Channel + and - buttons and that seems to pretty much do the trick, and now I've pretty much got it set up to do everything I want it to, without too much fuss... Of course a full-size MCU would be easier, with dedicated buttons for most things, but this works better than I ever expected, with my poor old discontinued Kore unit.
 
Thanks again for your help and explanation, and of course for all the work on the plugin! I may see about setting up my little tablet as an alternate controller under TouchDaw next...

Hi again... so, again, I have things set up fairly nicely and am using it happily but occasionally I notice something that doesn't seem quite right and so I go in and try, with my limited understanding of how the thing works, to bend it to my will... the latest was this: I have a button on my controller set up to switch between controlling tracks and buses; rather than cycling through all control groups with a loop command, I just use conditional logic so that if it's on tracks, it changes to buses and vice versa. This works well since I never really need to change anything on the Mains channels.
 
I also have the same button set up to open the AZ display, if it's not already open. And since I noticed that it was not updating in the display whether it was controlling tracks or buses, I managed to get it to do that with the Reset All Monitors command, which was not intuitive but I figured it out and it does the trick. However it only seems to work in volume mode (set state -> assign: par); in pan mode (assign; pan) it will only display Pn in the first box, whereas in volume mode it will indicate the current control group as it switches back and forth. It would be nice to get that happening in Pan mode as well; any tips on how to make that happen?
 
Hopefully that makes sense, thanks in advance...

I have tried to reproduce what the problem is, but I can not. May be I have not understood the problem, sorry.
 
But in general, please check the original configuration for corresponding switches. It is not just changing one state. Look for example "(Ch: 1 N:80) Bus :", which switch to the bus mode.  In addition to CtrlGroup change, it also set WAI and update display.
 
The original Pan also operate with AssignMode (and EQMode), following what the original plug-in was doing.
 
You can "Play" original buttons definitions from the Logic Tab (without any particular action selected, it plays the whole list). If you find some sequence which produce unexpected result, please let me know and I will fix it. If original lists are working fine, check what actions you are missing.
 
In fact, "display" part should be reworked. Unlike buttons, it is extreme complicated mostly in (unsuccessful) attempt to trick TouchDAW. I have introduced some changes to make it simpler (and more transparent) but I have not updated the plug-in yet.

OK thanks! That was helpful in that I figured out how to move WAI and the input focus back and forth while switching, which I didn't have working before. But the display still only changes from Tr to Bu when the assign mode is set to Vol rather than Pan. In Pan mode it just says Pn and never changes. However, everything else now works pretty much as expected, so I'll keep throwing things at it and see if anything sticks...

Morning is better time to understand something!
 
My Preset follows Mackie one. And the original plug-in display "Pn" independent from Track/Bus mode. The display has 2 characters only, so it either can show "Tr" or "Pn", but not both. Software display has no such limitation, so it is possible to show both (in my Startup preset I do this). I have mentioned before that you try to use an imitator of some software with an imitator of related hardware

azslow3
I have mentioned before that you try to use an imitator of some software with an imitator of related hardware

Exactly! I'm aware of the limitations and again, quite amazed at how well it's working after a bit of haphazard tweaking
- it's much more comprehensive, flexible and stable than what I was able to acheive with the standard ACT plugin. So that's cool.
 
This last thing is just a very minor annoyance - I realize I'm stuck with the two character limit, which is kind of arbitrary in a software environment but whatever, that's not the problem. I was just hoping I could figure out how to get the display in position 1.1 to switch (between 'Tr' and 'Bu' when I switch the control group back and forth) in Pan mode like it does in Vol mode. If for some reason that is impossible with the current setup of the plugin, or because of underlying limitations in the MCU specification, I'll be happy to stop bumping my head against it...