Thanks! Already answered... something wrong with MIDI mapping of touch/push for encoders. I have specified how to test that in the answer.

azslow3

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

Thanks! I had a quick look and I think I understand QU MIDI documentation better now. If I get it right, I just need "normal" MIDI part, ignoring NRPN part which is to control the mixer from Sonar.
 
That piece because this is a surface is an important function to me. Is it my understanding that two way communication is not configurable?  Thanks.... 

LunaTech

azslow3
Thanks! I had a quick look and I think I understand QU MIDI documentation better now. If I get it right, I just need "normal" MIDI part, ignoring NRPN part which is to control the mixer from Sonar.

 
That piece because this is a surface is an important function to me. Is it my understanding that two way communication is not configurable?  Thanks....

Sure 2 ways communications are possible! Sorry, I had no time to prepare working preset. I think till the end of this week there is something.
 
What I understand now is the following. QU has 2 different MIDI protocols:

1. the first one (for which you have the translation table) is to control DAW from QU. I mean in case you move fader one in this mode, it will change some Sonar strip volume. It should work other way around, so in case you change Sonar strip volume, the fader is moved. But that does not affect QU channel volume.
2. the second one is to control QU hardware. It is there not to work with DAW, but enable iPad application control the mixer. Theoretically it is possible to "synchronize" that with DAW, so for example in case you change Track 1 volume in Sonar, it changes QU Channel 1 Volume inside the mixer.

While some fancy staff is possible with the option (2), for example record/edit some QU parameter automations as Sonar Track automations, I am going to concentrate on the use case (1).
 
This duality, in addition to mentioned HUI translator for Mac, is what has confused me originally.

Build in presets for A&H QU-24 and Frontier Alphatrack are available in the latest release.
 
QU24 has basic functionality, but support LEDs, Motorfaders and parallel control of tracks and buses. All features list:
http://www.azslow.com/index.php/topic,178.0.html
 
Alphatrack preset mimics original Alphatrack plug-in. It has working ProChannel EQ control and ACT "Speed Deal" mode (instead of original ACT mode). More details: http://www.azslow.com/index.php/topic,172.0.html
 

On my Alphatrack, with the AZ controller plugin(only), My fader returns to it's starting position after I slide it. It registers the movement in sonar and it keeps the adjustment i made in sonar until I touch the fader again, then it jumps to the position I'm at on the AT.  If I use the mouse the fader follows and stays put.  This does not happen with the original plugin.  Thanks

Please help me to understand whats happening.
 
Do you have Track volume automation? In this case Sonar return to it for me (on other devices), so that is kind of expected (may be original AT process it different way).
 
I also hope you do not have AT connected to both plug-ins at the same time.
 
If you do not have volume automation. What you me by the "starting position" to which it returns after you touch the fader again? While touching? By logic, when you touch the fader (till you release your finger), plug-in should not operate motor. If that happened, I want to understand why. But I need some assistance, may be we can continue on my forum. Please understand, it is hard to debug problems with device I have seen on pictures only...

I have definitely not seen anything like this, and I've tested the Alphatrack preset extensively at this point, so it would surprise me greatly if there were a fundamental issue with the plugin/preset.
Is Automation Read/Write enabled properly? Are you using the latest (release) version of the plugin/preset?
 
As Alexey pointed out, if you have Alphatrack's MIDI routed to and/or from both plugins at the same time, this will cause mucho interference, but it looks like you're saying you are using the AZ plugin only.

Thanks for the replies, I do not have both plugins connected at the same time.  As far as the starting position, I'm referring to where ever the current position is on a given fader in Sonar.  If I start a blank project, the fader is at unity, If I Slide the fader down to -10db on alphatrack, It will actually register in Sonar -10db but as soon as I take my finger of the alphatrack fader, it returns to unity while Sonar continues to read -10db, at this point, if I only touch (not slide) the fader, Sonar jumps from -10db to unity, since that is where the fader on alphatrack moved back to.  
 
Everything else is working fine, I would suspect something may be going bad with my unit, but this behavior does not exist using the original plugin. Automation works perfectly except the above mention problem.

Sorry frank, the discussion is going it 2 different threads.
My co-developer has reproduced the problem and I have an idea from where it comes. Your observation confirm that. I have asked to check the fix: http://forum.cakewalk.com/FindPost/3225817 but there is no reply till now.
At least I understand that the problem is in the preset (not in the unit and not in the plug-in). And the problem can be eliminated by one line. We just have to check either it is the one I have already proposed or the modification should be in one word at other place.

I will post in that thread then, thank you for reply, your time, your will to get it right, you are a man after my own heart.