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.

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




For the ZED update do I need to install "azctrl_0_3r2b166"?  Want to make sure to install the correct version this time.

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

azslow2, version b168 seems be be working perfectly with my A&H ZED-R16 console!  Thanks so much for your help!
 

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!

Thank you for the comment! I am impressed you have managed to tweak something without reading the documentation.
 
Scrub is quite resources hungry. If audio buffer settings are to aggressive, I also get periodic crashes/audio resets. You can check that by scrubbing with mouse without surfaces.
 
I do not have Mackie HUI preset but Mackie MCU (which is Mackie LC). This protocol is different. And you are the first one who has tried to use it. I know it does not display information correctly with TouchDAW on phone (the only Mackie like surface I have). On tablet it should be better. I still have to polish it, I just was slowed down by no visible interest from community.

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.

I want to give you some tips (described in the documentation, but who read it):
1) switching "Banks" of strips in AZ Controller is implemented as moving WAI. In Mackie Preset, that function is on "<Bank" and "Bank>" controls. You can remap these to some buttons you have (which are not used... likely you do not have such with Mackie preset and you have to sacrifice other functionality).
2) using Mackie preset for Kore is like shooting from big gun tiny animal, you can try "Startup preset". You will have to define jogger yourself and MIDI learn all controls, but existing actions are easy to understand. MCU has over 100 buttons, 9 sliders, 8 encoders, 3 displays. 5 buttons are used just as "Alt/Shift/Ctrl/Mod/Edit". And the preset supports all original combinations/modes for all of them. It is "unreadable" even for me (the PRESET tries to follow several thousands lines from C++ code of the original plug-in!).
3) carefully tuning preset for your device can do much more than Mackie preset can do with it.

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

So it turns out that the bank commands are already integrated into the Kore MCU emulation, I just hadn't noticed them. It works quite well, and the minor tweaks I already made - changing the Scrub button to a track/bus selector, and also setting it up to open the AZ display if it's not already open, as well as looping between EQ edit modes (it defaulted to stepping through them and then becoming stuck at the last one) are probably enough for the moment. I have two monitors, and the AZ display sits nicely at the top of the console display on one of them, acting like a dynamic scribble strip to remind me of what the control surface is set to do at any point. It's actually a pretty comfortable setup, not ideal as there are obviously more pages to navigate than in a larger surface.
 
I'm having trouble at the moment finding a way to cycle through EQ bands - I can cycle between multi-channel EQ enable and single-channel EQ edit, but it only seems to access the LF and would love to find a way to cycle between bands. Not a huge deal as it's often just as well to edit EQ with the mouse, but still... any suggestions?