I've been riding on the back of all your efforts for the Alphatrack. I'm using it just not testing it. I'm about to download the latest version.
Just wanted to say thankyou.

Wow is all I can say. It is just so much more responsive than the Frontier version  and for the first time in a long time, to have control of eqs and plugins.
 
Just a question. In some instances a control is exposed that should be on or off but the display and function operates in percentage. 50% >  is On while 50% < is Off.
The encoder starts at Labelled Off. Any movement clockwise then has to be rotated to achieve 50%=/> for On
 
If it has been explained please just mention the post. No need to repeat for me. I have read the thread but I'm sure to have missed things.

Sonar expose all parameters as 0. to 1., throw the whole set (0.2, 0.445, 0.734 as an example). They have foreseen "native" resolution hint (I mean it should return that the "resolution" is 1. for on/off parameters), unfortunately the have forgotten to implement it properly for all cases. That means that plug-in can not ask Sonar either the parameter is On/Off or support 1024 or more different "positions".
 
For most fixed parameters (band on/off, EQ type, etc) I have "hardcoded" the knowledge into the preset, so only one tick is required to switch (point me in case I forgot some). But for VSTs generic procedure is used. Sonar/VSTs process <0.5 as 0 and >0.5 as 1. I send whatever I think is the current value + encoder resolution increment (0.1 -> still 0, 0.2 -> still 0.... up to 0.5 -> 1).
 
CakeWalk is well aware about that inconvenience. For MCU they use separate (from Sonar/ACT) configuration files per VST, which list all parameters with range and resolution, also mentioning some of them are binary. I do not have such configuration yet, but it slowly "rise" in priority. In fact it is possible to scan for such information, so no user intervention will be required. That is relatively complicated to implement, please do not expect in the near future.
 

The work you've already done is astonishing and has helped me a great deal. I mentioned the issue in the hope I had missed something in a previous post. Nonetheless the other functionality is far in advance of where I was with the old Frontier plugin. I'm very happy. Thanks.

I had wondered that myself but hadn't asked because I figured the explanation would be something like that... Anyway, yes, I think the preset is in a very good place to leave for a while...

Welcome to Alexey's party train! All aboard!

gswitz
Welcome to Alexy's party train! All aboard!

I prefer a party boat, I am on the beach in Italy
 
And since you (attempt to) call me by name... I am Alexey. Other forms are: Loesha, Aleoesha, Leoha, Löscha, Alöscha, Löcha, etc... Some try to call me Alex, which I do not like (in Russian online games/chats that is an equivalent of N00b). But "Alexy" is not in the list

I think my "beta testers" read this forum more often than my... I have uploaded new test version. Complete display functionality is implemented (level/pan indicators, resolution, flip, etc). I have tested how it works with internal display and my MPKMini, but I do not want upload it as the release before someone can confirm that real Alphatrack display works as expected too.

Bump... Is my party over?
I want release 0.4, but I need a confirmation it works. Common, full preset (all display features) + working ProChannel EQ + ACT SpeedDial + tunable encoders resolution. No interest?
 

I tested minutes after you posted, and the things I understood did work, but there were some things I was not clear on, which is why I did not report back.  things like level and pan does display correctly on alphatrack.  
 
I like the way I can quickly moving with a parameter on a plugin using act the way you implemented it.  However I also did like to use the original way as in when I'm in plugin mode on alphatrack, my three most commonly used parameters are ready to use and page two was not faraway.  Is there a way to get close to best of both worlds on this?