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

The version with "Medium" display size is uploaded.

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.

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

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

For PreSonus FaderPort owners:
 
In cooperation with Watercourse we have almost finished Faderport preset:
http://www.azslow.com/index.php/topic,163.0.html
 
Highlights:

• Focus and WAI follow device and device follows focus (also for buses)
• ACT "Quick dial"
• Hi/Low resolution for encoder (Pan and ACT)
• Time jogging (using encoder)
• Shortcuts to set Loop In/Out points

And as with everything else in AZ Controller, you can change/remove/add any functionality.

gustabo
azslow3,
Tried to register on your site but I never received the activation email, nor the two others that I had the forum software resend.
Any help?

I have just tried myself and I have received the confirmation e-mail immediately. Have you checked your spam folder?
 
In any case, you can also ask something here (on in PM) till we find some solution.

And answered
 
For other. There is no "for users only" section on my forum and I do not ask to register to download the plug-in.
 
Awesome, free, not calling home program from site without adverts and Russian owner. Sounds suspicious, I know

Hello LunaTech,
 
I am glad you still use the preset for zed.
 
After first look at QU-24 documentation, I see the following. It is more targeted to be remotely controlled then control DAW, but it can. They provide complete MIDI specification, which is nice. I do not see they transfer everything they can, for example they do not transfer "Fader touched" and fader resolution is just MIDI.
 
I do not understand your question about HUI. The device itself is not HUI capable and Sonar is not able to understand HUI. They have software translator on Mac for other DAWs, but such translator on Windows is not going to help with Sonar integration.
 
I am a bit busy these days, but something basic like ZED preset (with adopted number of controls and Fader/LED feedback) can be done quickly. In any case there are going to be some try/error/fix cycles, I mean I doubt it will work instantly since I do not have anything comparable for checks. Do you have time and possibility to test the preset and describe problems?

I have tried to understand QU24 MIDI specification, again and again, without success
 
So, I have created a thread on my forum: http://www.azslow.com/index.php/topic,178.0.html
In general I want to understand what you can see QU is sending. There must be some NRPNs from faders, according to the specification with just MIDI (127) resolution. But the number you see in lower position should be not 0 but 7. Just write what you see, I think that should help me.
 
About HUI and my plug-in. The plug-in is written specially for Sonar. It can not be used with any other DAW, it can not be used "stand alone", by design. I guess it can work with HUI devices, but that is not tested.

Is there any update info about Alphatrack preset?

I can beta test the Alphatrack! I have one here, using it so far with the original Sonar plugin but happy to give it a whirl with yours! I'm a bit more familiar with the plugin now and can hopefully be helpful...

Hi Azslow3,
 
I have added a translator txt file that details midi commands coming from the QU 24. It is on your site (Very informative I might add). I hope this helps. Thanks.

azslow3

mudgel
Is there any update info about Alphatrack preset?

http://www.azslow.com/index.php/topic,172.0.html
 
In short, I am waiting for beta testers

I have downloaded the test file and will start test this week. Once I have tested I will report back.

I sent you some feedback on the Alphatrack preset, on your site. More to follow as I explore it a bit further...