BretB
REW = "URT 70 6 5
...

 

LunaTech
I had a chance to play with the encoder settings and I believe I am happy with Instant/Convex.  This allows me to not have to wait for the encoder to catch up and I like the action more.

The latest version includes MMC Device configuration and Instant/Endless(low resolution) modes for encoders. The installation instructions are updated.

Normally you should install the latest release you can see, linked from the topmost News "AZ Controller XXX" post.
This time it is b166 (big chance it will change to b167 today...). You can see the version you have in the lower right corner. Then you can check the changelog between what you have and the latest, to see either some changes are interesting for you (like this time). Note that changes marked as "FIX" are important only in case they are marked SEVERE (in bold) and/or you use fixed features (up to now there was only one such bug fix).
 
Periodically there can be special purpose "Test releases", but they are not linked from "News".
 
You can not use preset generated in newer version with older version but you can install old version and use it with old or generated presets. It is not possible to have more then one version installed

OK after a lot longer than I had hoped, due to crazy performance schedule, I am finally back in studio mode for a while and I thought I'd give this a whirl to see if I could make any sense of it.
 
Background: I have a few different controllers including an Alphatrack, which works decently with Platinum with the original (no longer supported) plugin, a Contour Shuttle Xpress (ditto), and a NI Kore version 1 controller (which never came with a Sonar template but which I had some luck setting up under ACT in the past). I also have a tablet and am interested in setting up Humatic TouchDaw and possibly other control apps on that to see what fun I can get up to.
 
I thought I'd have a go at the Kore setup first, since I've mucked about with it in the past and I had one showstopping problem, which is that I could never get the jog wheel working properly - it would only work in one direction, regardless of which way I turned the wheel. The only way I ever figured out to override that was to use a button as a modifier, in which case it would always turn the other way, again regardless of what I did with the wheel. Not ideal.
 
So at first glance the AZ dialog box is disorientingly complex, I could tell it could probably be made to do just about anything but goodness me, how to get it doing anything? Luckily I found the quick start guide and managed to load the Mackie HUI preset, and set my Kore to do its kind of fiddly Mackie emulation, and lo and behold, everything pretty much worked right away, including the jog wheel! Right away, no fiddling necessary. Whoa!
 
The only stumbling block was that a) the scrub function, which is engaged with a little button below the jog wheel on the Kore, seemed to crash Sonar, and b) I couldn't for the life of me figure out how to change the control group so as to be able to work on buses insted of tracks. However, since I work mainly with MIDI and scrub is of limited use in that context, and I rarely ever use it anyway, I thought I could see if I could figure out how to make the scrub button toggle between tracks and buses. That took me about 10 minutes, not reading the manual (I'm really not much of a manual reader) but just futzing about with the Logic commands, before I got it, using a pair of linked Logic commands. to do just that. Now I'm trying to figure out how to get it to update the WAI display so it's clear what it's controlling.
 
So basically I can see the power of this thing - you really can get it to do pretty much anything, if you're willing to spend a bit of time on it. What a crazy amount of work must have gone into it! Impressive. I'll try to get in touch with you if I can think of any useful feedback... thanks for this! Very impressive!

Hi azslow3. Yeah I suspect my poor old machine is not up to the demands of scrub. so I'm going to leave it alone at least until something dies here and I'm forced to upgrade...
 
I guess I was mistaken, the Kore template is probably Mackie MCU not HUI, it just says Mackie Control. I'm still fiddling with it now. It seems to do a lot but I need to tweak it some more - either what Kore outputs or how AZC handles it or (likely) both. I can't for example seem to change banks at all, so I'm limited to 8 tracks - usually not a problem for my music, which is often based on low track counts of soft synths with really complex textures... but still, I know it's possible from when I set up Kore previously, and your obviously enormously flexible plug-in.
 
I'll keep you posted as I go along. I know there are/were a couple of other people here who use (or at least used to use) Kore controllers and were interested in how I had it setup a couple of years ago, but I don't know if they're still around.

Hi again and thanks!
 
I will have a look at the Kore controller editor later today and see what I can see. I realize the Mackie emulation is likely not the best or most efficient way to interface the Kore as a control surface, but it was an easy way to start and it works surprisingly well - I was very pleased to have proper jog wheel functionality after trying and failing for ages to get it working under ACT. I'll likely use it as a starting point for a more comprehensive preset, rather than starting from scratch, since I have limited time to throw at this... again, I'll let you know how I get along and if anyone's interested, happily share the resulting preset(s)!

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

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

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

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.

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

No problem!
 
The key is "AssDisplay" (Assignment Display) Feedback Actions list.

• Change text in first 3 actions to add space, so 'Tr' is 'Tr ' (note the space after). That is for readability. And remove "Assign:Par" condition (set it to <Any>).
• In "Se" "Pn" "P" "EQ" and "F1" change "Replace" to "Append". Do not do this for D1 (it is not strip dependent).
• In Format Text change "Trim to 2" to "No format" (or delete that Action)
• Delete "LC/MC Assign Display" Action. Even in case your device somehow imitate it, we no longer produce "correct" strings.
• Test the result

subtlearts
And I'm going to hold myself back from joking about "AssDisplay"...

I think that is good abbreviation for 2 characters 7 segments display in 2015...

This is so confusing but I want to learn lol. It'd be nice to just shove any control service in and map in freedom. You've said you slowed down aslow due to lack of community interest, but it might just because this thread is at a technical level higher than most of the users knowledge. 
 
If you can get me to understand how to set it up you can get anyone else in the world to =p. Keep up the good work!

Genius Animus
But it might just because this thread is at a technical level higher than most of the users knowledge. 
 
If you can get me to understand how to set it up you can get anyone else in the world to =p. Keep up the good work!

Most technical discussions is this thread was about one of two most complicated presets available in Sonar, Mackie Control. And the details was how to use it without the original device
 
Most configurations are significantly simpler. There is "Startup" preset, to use out of the box. There is "ACT MIDI Explained" with click by click guide and explanations, I have reworked it a bit recently. I also offer to build basic preset for any particular device, as we have done with ZED.

ACT buttons are not there...
 
You can add "ACT Switch <button number> + OffAct X 8" let say in "MuteX" action list, right after "WAI CtrlGroup Mute" (before "Toggle"). Add condition "Assign:Dyn" to it. Done.
 
With display it is not so difficult too (since we do not need imitate anything). In the same action list, add action and position it right after "Parameter Value Monitor". Set it to "Parameter Name Monitor". In the Feedback (you will see new monitor there), add Actions "Text Para. Name Parameter" and "Display Row 3 Column <button number + 1>".
 
In display options, change "Group" to "No", "Rows" to "3" and then "Group" to 3.
 
With that modification, the third row will show what "Mute" button is going to control (Mute or ACT parameter name).
 
Note that if you copy/paste Monitor Action in the Logic list (to second "Mute") it will copy also monitor actions. Do not forget to change <button number> in 2 places after copy.
 
And since you have asked... Good Luck!