gswitz
It would be so cool if the EQ control could enable/disable low-pass and high-pass filters, control Freq and Slope for both.

Can you check either it works as you want in the Test version? You can find test version throw Download menu, the versions is "b221M" at the moment.
 
PS. Just to make it clear... After installing new version, it is required to regenerate the preset by selecting "Alphatrack" again.

The HP/LP EQ control works very well in the test version, no problem there at all. A bit strange to have two controls to turn the band on/off, one on each 'page' and on different encoders, but hey - two knobs are better than one, what?
 
The only thing missing from EQ control is now the switches for the High/Low EQ bands from bell to HP/LP respectively. Not something I've ever used, but they're there, so obviously we need to control them, right! Right?
 
They could be mapped to the function keys in a mode-specific way. I'm still playing around with the function keys as I'm not sure I want them always mapped to the track store/recall behaviour, especially when mode-specific functions are possible...
 
I have not seen anything like frankjcc's fader issue, I suspect he may have implemented the fix wrong or something, because I definitely do not have that happening here at all. So from what I can tell the current version should be working with no problems.
 
I can also confirm that your proposed fix for the Marker movement works perfectly - I made a copy of the logic command and made them both transport-dependent, so if transport is stopped it goes back -1, if transport is in play it goes back -2. This works perfectly. I didn't put in an entry for if transport is in Rec, which means that in Rec mode the knob does nothing, which is probably best.

subtlearts
The HP/LP EQ control works very well in the test version, no problem there at all. A bit strange to have two controls to turn the band on/off, one on each 'page' and on different encoders, but hey - two knobs are better than one, what?

In the first attempt, 2 and 3 was controlling the slope, looking at the result, I decide to change that to On/Off
 

The only thing missing from EQ control is now the switches for the High/Low EQ bands from bell to HP/LP respectively. Not something I've ever used, but they're there, so obviously we need to control them, right! Right?

We need some "place" for that and Gloss. We can put them on the second page encoder 3 for LP/HP, but that is a bit ugly... We have Shift + Encoder 2 (since there is only one EQ for now). We can distinguish Page1 Shift from Page2 Shift. Let think a bit more, may be some brilliant mapping solution visit us in dreams.
 

I have not seen anything like frankjcc's fader issue, I suspect he may have implemented the fix wrong or something, because I definitely do not have that happening here at all. So from what I can tell the current version should be working with no problems.

There can be other issues, I hope he let us know either the problem is away.
 

I can also confirm that your proposed fix for the Marker movement works perfectly - I made a copy of the logic command and made them both transport-dependent, so if transport is stopped it goes back -1, if transport is in play it goes back -2. This works perfectly. I didn't put in an entry for if transport is in Rec, which means that in Rec mode the knob does nothing, which is probably best.

I will put it into the next update.
 
Thanks for testing!

Sorry for late reply I'm in and out today.  The Marker issue does allow for moving back two marker instead of nearest, however I was not asking to eliminate the original function, it is still necessary to move to the nearest marker going back, I just thought if I turn the knob faster, it should allow for going beyond the nearest marker.  I have my qwerty keyboard set to use the arrows to move to previous and next markers, if I press the left arrow twice rapidly it will move to the left marker that precedes the nearest left marker, The way hardware cd players work.  This is the way it functioned in the original plugin.
 
My fader issue remains, but it does atleast finally come to rest where I set it, so I can live with that.

I tested marker movement and it works as I would expect. The only logic change which might be handy it to RTZ (return to zero) when there is no preceding marker.
 
The HP/LP filters work great. Since the slope always moves in increments of 6dB, perhaps each tick on the rotary could move 6 in that case rather than 1dB. But whatever, it works great as is.
 
In addition to the gloss choice, there is the choice for the shelf switch on the Low and High bands. I'm not sure if there's a place for that too, but I mention it, just in case.
 
On the latest version I'm again getting Audio/Midi device was disconnected from your system when I'm twiddling the nobs a lot. Not so sure what's up with that. I haven't seen it happen when using the AlphaTrack for Sonar. No one else is seeing this?

frankjcc
Sorry for late reply I'm in and out today.  The Marker issue does allow for moving back two marker instead of nearest, however I was not asking to eliminate the original function, it is still necessary to move to the nearest marker going back, I just thought if I turn the knob faster, it should allow for going beyond the nearest marker.  I have my qwerty keyboard set to use the arrows to move to previous and next markers, if I press the left arrow twice rapidly it will move to the left marker that precedes the nearest left marker, The way hardware cd players work.  This is the way it functioned in the original plugin.

Got it. The problem even I sometime have with AZ Controller is the possibility to do the same operation several different ways, which are almost identical, but not completely identical.
If you want try it before I put it into the next update. In the "Logic" tab select "Middle Encoder". Select "GoTo Marker... -1" (or -2 if you have changed that). In the lower part, change "Function" to "Command" and then "<Menu>" to "Previous marker" (the list is long, but it is there, before commands started with "*").
 

My fader issue remains, but it does atleast finally come to rest where I set it, so I can live with that.

Lets try "Plan B" then. In the "Feedback Tab", select "Fader : : Parameter Value Monitor". The first (and only) action is selected automatically. In the "Action conditions" section, select (where you see "Strip") "Fader touched (No)". Right from it, change "No" to "<Any>". Test the result.
 

gswitz
I tested marker movement and it works as I would expect. The only logic change which might be handy it to RTZ (return to zero) when there is no preceding marker.

I will think about that.
 
[qoute]
The HP/LP filters work great. Since the slope always moves in increments of 6dB, perhaps each tick on the rotary could move 6 in that case rather than 1dB. But whatever, it works great as is.

Noted.
 

In addition to the gloss choice, there is the choice for the shelf switch on the Low and High bands. I'm not sure if there's a place for that too, but I mention it, just in case.

The place it the problematic point, as mentioned in the previous post.
 

On the latest version I'm again getting Audio/Midi device was disconnected from your system when I'm twiddling the nobs a lot. Not so sure what's up with that. I haven't seen it happen when using the AlphaTrack for Sonar. No one else is seeing this?

Can you more or less stable reproduce that? Try continuously fast turning one encoder or moving the fader.
The plug-in can not trigger such effect directly. There is for sure no difference between preset versions. The only reason I can imagine is that I send more/a bit different information to AT and it is stuck than.
 
In the "Feedback tab", select "_Display :: Timer" (the last in the list). Press "New" and check "Final (stop...)" flag. You should see "- Undefined *" as the first action.
 
From that point on, there will be no display updates. But the test for disconnect in such "mode" can give me a hint in which direction to think.
 
Thank you for your patience.

https://youtu.be/Ci7XrUSX1TA
 
This video shows the controller dropping out on me.

Thank you for the video!
 
2 points:
1) you say it happens you move encoder for frequency, you see changing value on (AT) display, but it does not change anything in EQ itself. If that is the case, that is Sonar bug. I send new value and display what Sonar say current value is (I do not display the value I send!).
2) About AT crash. Please try to reproduce it with "Display Off" mod.
 
If you can not reproduce it with display is not updated (so, my display procedure makes AT crash), I can optimize Display output.
 
If it still crash, something is wrong on software/hardware level outside the plug-in. Please try again to reproduce the problem with the original plug-in (may be you have not tried yet to crank it really bad?). If you operate encoders without display, I send nothing to AT. And so I have hard time to understand how I can make it crashing (except that my plug-in takes a bit more time to process incoming events and that overflow internal queue in AT system driver... but than in should occasionally crash on heavy projects with the original plug-in, and I do not see such problem reports).

To speedup "turn around" for the problem with "fighting" fader.
 
In case "Plan B" from my post #86 (removing "Fader touched (No)" condition) produce no visible affect when applied, please try to delete modification from the "Plan A". I mean switch to the "Logic" Tab, select "Fader touch" control, select "Note:Off - Reset Fader : : Parameter Value Monitor" and press "Delete" button. Important. "Plan B" should be still applied (you will have original broken configuration otherwise). Test the result.
 
If "Plan B" still does not work (with/without "Plan A"), I have "Plan C" in mind. But I will wait for the test results first...

Never mind I found it, testing now