Well that worked pretty well! Took a bit of fiddling but as usual once I'd figured out what your instructions meant, they were clear and did the job. Rather than using the Mute buttons as you suggested I went with a dedicated page of 8 MCU buttons, repurposed from ones that did things I'm not particularly interested in (I find key shortcuts are useful for many things, so I'm not looking to make buttons on a control surface do things that I can already do easily with the keyboard). The display works pretty well and tells me what parameter will be controlled by each button, changing dynamically as I select different things to control. Nice! Thanks!
 
A quick question, is it possible to control the size of the AZ Display window (and its text) with a bit more precision? Tiny / Normal / Large / Huge is pretty vague, and while 'Large' is pretty close to what I need, I could imagine making it a tiny bit smaller but not so small as 'Normal'. But I suspect this will be baked into the plugin somewhere, so I don't know if it's accessible.

dmclaughlin
I don't have much to add beyond a huge THANK YOU to Azlow for this tool. I have started programming my BCR2000 and once I have this fully set up it is going to be amazing.

Thanks! After Quick start, Startup preset it something to have a look. Please let me know in case you need some help with it. Also please report any bugs you find, I am still waiting for the first crash report or broken functionality
 

subtlearts
A quick question, is it possible to control the size of the AZ Display window (and its text) with a bit more precision? Tiny / Normal / Large / Huge is pretty vague, and while 'Large' is pretty close to what I need, I could imagine making it a tiny bit smaller but not so small as 'Normal'. But I suspect this will be baked into the plugin somewhere, so I don't know if it's accessible.

As you could notice, the GUI part is bare minimum. I agree that Display should be improved at some point since it is used during operation. But for the moment I will just add more size options (I will make the change tomorrow).

azslow3
As you could notice, the GUI part is bare minimum. I agree that Display should be improved at some point since it is used during operation. But for the moment I will just add more size options (I will make the change tomorrow).

Yes of course, your work has obviously been focused more on functionality than eye candy, and I'm all in favour of that - so I join others in thanking you for it and recommending that anyone looking to improve their experience with a control surface check it out!
 
For me the display is a huge part of the usefulness of the plugin - it sits happily at the top of my console in a 2nd monitor, floating in front of everything, and I can toggle it on and off with a button press. OK it's not pretty, but it's highly functional, which works for me. But sure, if you're bored, I won't complain if it gets a bit of a makeover, or some more size options...
 

azslow3
Also please report any bugs you find, I am still waiting for the first crash report or broken functionality

I'd love to, but every time I think I've found a bug or instability it turns out I just haven't understood or implemented it properly. Everything I have working right now seems pretty rock-solid, which is impressive! I'm sure if I keep refining my setup I'll stumble across something, but so far, no...

The version with "Medium" display size is uploaded.

Works just fine here! That seems pretty close to the sweet spot for my display, and I can make room for a few more characters per text block too...

subtlearts
Works just fine here! That seems pretty close to the sweet spot for my display, and I can make room for a few more characters per text block too...

Do not forget to change "Format" actions, they currently limit each output to 7 characters (as required for MCU).
 
Musicians are sometimes inspired to write music, programmers can be inspired to write... programs
Thinking how to use ACT with Faderport which has one encoder only, I came to the idea to use "ACT Speed Deal". Modify some plug-in parameter by mouse and some encoder start control it. No other operations required. While the idea is not original (used in Automap for example), I have not seen such approach to use ACT API.
See http://www.azslow.com/index.php/topic,165.0.html for details.

Hi again. Out of interest I'm trying out your new function - it seems to work pretty well (once I realized that I needed to download the latest version of the plugin ) so I've integrated it into my MCU emulation setup (which is getting more and more complicated!) as a kind of easy quick access to a control without having to step through pages to find the control for a given parameter...
 
It does kind of expose some instability which may be in the underlying ACT code - sometimes controls don't respond, other times they do... however, it's a nice little addition, so thanks yet again!

subtlearts
It does kind of expose some instability which may be in the underlying ACT code - sometimes controls don't respond, other times they do... however, it's a nice little addition, so thanks yet again!

If you see some instability, please notice which exactly. I have explained 2 possible problems in the tutorial, but there can be other. I mean, does that happens with different parameters, bound to particular VSTs, etc.
 
Please note, that it detects "some" change. If several parameters was changed, it will select "randomly" (not really, but that how it looks like).

OK more specifically:
 
- The ACT Speed Dial doesn't seem to work at all when I first start Sonar, I have to open the AZ control window first. Then it starts to work, but with limitations:
- Some Pro Channel modules seem to be unstable, particularly the Console Emulator and the Concrete Limiter - sometimes they don't respond at all. The EQ module seems to always work... and sometimes one that wasn't working will respond after using one of the more stable ones
- Similarly, Izotope Nectar Elements (a VST3 plgun) seems to not work until I run a VST2 plugin first - I tried Camel Space, which worked fine, and then Nectar Elements worked. Waves One Knob plugins (VST3) seem to generally work.
- It's hard to give you a clear answer since it's a bit of a moving target - things don't just either work or not, they work intermittently. I'll try to observe it a bit more and get back to you...
- finally, when things don't seem to work, generally their ACT parameters do not appear in the ACT tab of your plugin - typically only Enable is there; when things are working as expected this area shows all available controls, as expected.
 
 
Not sure if that's helpful, but that's what I've noticed so far...
 

Thank you for the reply! Any feedback it helpful, it points me on parts to check.

subtlearts
- The ACT Speed Dial doesn't seem to work at all when I first start Sonar, I have to open the AZ control window first. Then it starts to work, but with limitations:

I could not reproduce that with X2, will check with SPlat later. Possible cause: you have no Timer with "ACT Changes scan" function, or it does not work for some reason. In that case, "Speed dial" works only when the Property Page is opened.
 

- Some Pro Channel modules seem to be unstable, particularly the Console Emulator and the Concrete Limiter - sometimes they don't respond at all. The EQ module seems to always work... and sometimes one that wasn't working will respond after using one of the more stable ones
- Similarly, Izotope Nectar Elements (a VST3 plgun) seems to not work until I run a VST2 plugin first - I tried Camel Space, which worked fine, and then Nectar Elements worked. Waves One Knob plugins (VST3) seem to generally work.

Have to check with Splat, where I have more plug-ins.
 

- finally, when things don't seem to work, generally their ACT parameters do not appear in the ACT tab of your plugin - typically only Enable is there; when things are working as expected this area shows all available controls, as expected.

SONAR periodically does not inform plug-in correctly what is going on. Some bug(s) I think. But when some plug-in stably show no ACT Map, it can (and should) be mapped. Theoretically, some default mapping should always be there for CW staff. Practically it is not the case (yet another bug(s)). I have also noticed that some plug-ins are less "stable" then other in that respect. I do not have Concrete Limiter, but Console Emulator glitch for me as well.
VST3 had bug with ACT and I have not used them since that, but I have thought that was fixed. Will check with Nectar Elements (the only big one I have).
 
In general, if ACT Tab is empty, "Speed deal" will not work. To check changes I need access to parameters and ACT Tab is updated once I have such access.
 
I do not want to create noise, but everything related to Control Surface (and in particular to ACT) in SONAR is extremely buggy. Many things are "randomly" do not work,  some are stably return nonsense. I try my best to avoid problems inside AZC, some times unsuccessfully...