Of course, it's handy to have a return-to-zero, at least for Pan, if nothing else, and I know what you mean that it was almost impossible to get it to exactly zero from the controller - I would often end up just going and double-clicking or ctl-clicking on the on-screen knob. I do think it's a useful thing to be able to do, but if double-click is technically not feasible, maybe there's another way to implement it. Hence my suggestion of moving Trim control to a second page in Pan mode (as there is a second page in the other modes, accessible via a second press of the mode selector button), and using shift-encoder-click as a hardcoded return to zero for Pan, and possibly anything else that makes sense.
 
On the other hand, if the encoder adjustment values are whole numbers, it might be easier to land on exact values, including zero or center, which would make the whole thing kind of moot...
 
I didn't mean that the double-click was arbitrary by the way, I was referring to the resolution of the encoders adjusting Pan etc - the exact values of 'normal' and 'fine' adjustment modes in the original plugin were arbitrary and do not need, in my opinion, to be replicated exactly.
 
And yes, as always, Alexey, thanks for your hard work and attention to detail on this, and absolutely no hurry to implement these details...
 

@Subtlearts,
 
I get you on the pan change value per click appearing arbitrary, but I'm a little doubtful. I've written a lot of code in my life too. If I was arbitrarily picking a value to change it to, I wouldn't pick something that couldn't return to 0 or that moves at even increments. The fact that it it doesn't makes me think that it might be even in midi values and not in percentages (but why wouldn't this return to zero nicely?).
 
So, maybe it had to do with the midi drop-outs? Some sort of change that had a reason.

While you was discussing, I was really coding... Not completely ready yet and I have to stop for several hours.
 
But to let you informed what is going on in my code:
1) new option for Set Value Action, the step size. From 0.2% up to 50% (with 0.2% increment). I will set some default in the preset for coarse and fine, and then you can test which exact value is the best. I will expose it in the preset generation dialog
2) I am going to use "long press" (for 0.5sec for example) for Pan reset (and only Pan at the moment). So, short press change resolution, long press reset the value. That sounds good for me: no shift mess (shift display other parameters), no fine/coarse change with "push plus turn" and no double clicking
3) there will be 1/2 "magnet" in the Endless mode. Quite complicated calculations exists for normal Knob mode to make it jumpless set "nice" values like 0.25, 0.5 and 0.75. But there was nothing for endless (I was not using them). I decide to make at least 0.5 sticky. It took me many iterations to make things work as expected for MIDI, so that can introduce some glitches in endless, but I will fix them once spotted.
 
Ok, I have to go. More this evening.
 

Alexey, that's awesome! You're amazing. Long-press is much better, cleaner, don't mess with what's already working. If it seems like it's a good solution and not hard to implement we can look at putting it other places later - maybe send pan, for example.
 
The Magnet code sounds promising too, that might enable moving towards a 'perfect' solution on encoder resolution. Not that it's an urgent issue, but again, I appreciate your attention to detail and enthusiasm for finding elegant solutions...

TY

I know we are over the double clicking thing, and I would always be against that anyway, but ever since I got my alphatrack, when double clicking things to return to zero like sonar does natively, I liked the idea but I hated the hard work to accomplish the task, I always felt that they should have made it be double touch.  This would have been so nice to use to return any control to it's default value.  like I said, I know we're past it now but if it comes up again, My vote will be double touch. this is the least strain and faster action.
 
Now this has got me thinking,  What if we made use of touch combinations, What I'm about to say I thinking of in realtime and there are hundred of ideas coming so I'll keep this short.  What if we can create new commands that are not possible right now without sacrificing any existing buttons.  touch two left encoders at same time, touch two right encoders, keep left encoder touched while touching middle, touch all three, double touch, tripple touch, two at a time, three at time.  I know I know this all seems so complicated and it probably is, but!! this is how Azslow introduced the AZ controller in the first place, he shouldn't have(just kidding) I'm loving it the way it is, And I sent flowers.

frankjcc
My vote will be double touch. this is the least strain and faster action.

As I have wrote, I do not like "double" actions. That is always "subjective" what is "double" and what it 2 sequential actions. Especially with touch. Example: "I think the resonance frequency is a bit lower..." (touching the control), "hmm" (releasing the control), "yes, just a little bit!" (touching the control, in your scenario the frequency is reset to default). Next thought will be not about the frequency, but about the person who has implemented that "feature"
 

What if we made use of touch combinations

2 general problems there:
1) you can use 2 hands to control 2 parameters at the same time. Examples: Freq/Gain, adjusting pan on several tracks (so your left hand is still touching left encoder for fast switching while right hand adjusting pan). I do not think you would like "side effects" there
2) I do not know how good touch is on Alphatrack, but during my short attempt to use Nocturn, I was "touching" near everything on my way to the control I was engaging. Display change - ok, but some changes inside Sonar...
 

I know I know this all seems so complicated and it probably is, but!! this is how Azslow introduced the AZ controller in the first place, he shouldn't have(just kidding) I'm loving it the way it is, And I sent flowers.

I do not say it is not possible! There is no special "double click" support, but everything enabled in Monitors is possible reaction. I just have arguments why I do not see it practical.
 
And in case you want some actions using touch without "upses", it is easy to add "F1+Left encoder touch" and so on. "Flip+Encoder touch" is already in use. Note there are already some side effects from touch. For example, when left encoder is touched in the strip changing mode, Fader motor is disabled (to avoid jumping during rapid track changes).
 
Flowers are "working" by doing nothing (no joke, since I have introduced that idea, my wife has not complained about me programming the plug-in... ). But in case your device will attempt to "work" based on the fact your hand is in the near, I do not think you will be happy.

Thank you for this reply, I agree on all points mostly I considered all the accidental touches could really make a mess of things.   Delete idea

frankjcc
I know we are over the double clicking thing, and I would always be against that anyway, but ever since I got my alphatrack, when double clicking things to return to zero like sonar does natively, I liked the idea but I hated the hard work to accomplish the task, I always felt that they should have made it be double touch.  This would have been so nice to use to return any control to it's default value.  like I said, I know we're past it now but if it comes up again, My vote will be double touch. this is the least strain and faster action.

FrankJCC, for me double touch might force me to stick to the AlphaTrack Controller Plugin because I would be hopelessly confused if, when trying to grab the control, I accidentally reset a value - even if it happened very seldom.

gswitz
FrankJCC, for me double touch might force me to stick to the AlphaTrack Controller Plugin because I would be hopelessly confused if, when trying to grab the control, I accidentally reset a value - even if it happened very seldom.

By nature of AZ Controller you can with several clicks on "Delete" button REMOVE any functionality. Introduction of not existing features is a challenging task, but "killing" existing is not
 
So, I have uploaded new test version. Too many changes to put into the "official" release directly. The version is b222. Do not forget to regenerate the preset after updating.
 
Changes:

1. motor operation according to the "Plan B", with "Plan A" deleted. Please check there is no more unexpected moves and "fighting" after finger release
2. marker movement changed to "native" commands. No "RTZ" as implicit marker, but since marker can be inserted at time zero, I do not see a problem with that.
3. display is updated slowly during parameters changes. I have reduced data flow by half per update and I have reduced updates rate by factor 3. May be it is too pessimistic, may be still too optimistic. Please let me know.
4. encoders speed/resolution is configurable during preset generation. Separately for Coarse and Fine mode. I put some values which are good for me on StudioMix. They can be not so good for Alphatrack. Report what each of you prefer and I change the default (you can test different values without regenerating complete preset: open Property Page, switch to the "Logic" Tab, turn encoder, select action  "Endless User, manual touch" with corresponding conditions (Mode, Resolution, Page, band) for the mode you are currently testing, change the resolution, the effect is immediate)
5. HP/LP slope controlling should be better
6. Pan (strip and sends) can be centered by long pressing the encoder. Not perfect, since it is really setting the value after you release the button (and not just after some time). That is AZ Controller limitation (yes, it still has some). In the future I can add some indication on display that the "time is over". In the long term future, I may be eliminate the limitation. "Long" is fixed by now (~0.7 second, the value I have found good for myself to not wait for too long and not too short for triggering reset by mistake during coarse/fine switching), but I can also add it as a generation time configurable parameter.

Thank you for testing! That part of the "job" is normally underestimated. Without careful beta testers even the best software is just useless collection of bits.