azslow3

subtlearts
The Function keys are not mapped by default

They are mapped to what I could see in the original documentation as "default":
Save (with shift) and Recall (without shift) currently controlled strip. With bus/track automatic switch.
I thing that functionality is really useful for one strip controller, when you want switch back and force between 2 not adjacent strips.

Aha, I'd missed that. I've never used that functionality, maybe I will give it a whirl!

azslow3

subtlearts
The Function keys are not mapped by default

They are mapped to what I could see in the original documentation as "default":
Save (with shift) and Recall (without shift) currently controlled strip. With bus/track automatic switch.
I thing that functionality is really useful for one strip controller, when you want switch back and force between 2 not adjacent strips.

Auto track/bus focus is a killer add on, bravo!
But I can't see any action when pushing F keys...
 
BTWI've sent some coins for your lady's flowers.
 

Ok, I see what you mean with save/recall, nice. So all 4 F's are assigned to the same action, right?

 But if the Fader is moving to incorrect position, that can be my bug. Please try to find some "pattern" when that happened.
 

 
Just had a quick test using my AlphaTrack and I can confirm the fader moving spuriously.
 
In a new project with three or four audio tracks inserted, use the fader to affect the track volume.
If you move the volume control in the gui with mouse, the fader follows as expected and is stable, and moving between tracks behaves as expected with the fader taking up the value of the current track.
 
However, if I move the fader to alter the volume, the GUI follows and is stable, but after a short time after releasing the fader, it moves itself back towards the 0db position. Moving to another track, the fader again takes up the correct position for the current track, but after adjusting the fader itself and releasing it, it will move again towards the 0db position.
 
It moves towards the 0db position but doesn't seem to get all the way to it.
 
I can also confirm that the fader operates correctly when using the original AlphaTrack control surface plug-in, so I am not suspecting a hardware problem with my AT.
 
Thanks for doing all this hard work! It will be good to get back to using AT with SONAR when the bugs are squashed!
 
regards
 
Cliff

For Function keys: select some track, press "Shift+F1". Select another strip (can be bus!), press "Shift+F2". You should be able now to focus first/second strips by "F1" and "F2".
 
For "self moving fader":
Is it still in sync with Sonar when moving? In other words, after "moved to some position toward 0bB", is position in Sonar the same? Let say you move to -12 dB. You say it is then moving to something like -6dB. What is real position in Sonar?
 
Open the property page, select "Fader touched" state set in the drop down box. Move the fader, release finger (you should see "Fader touched" state changing to "Yes", then back to "No". Now, when it start "moving by itself", do you see some changes in the "Last MIDI event" and/or the state?.
 
Old faders are known to be a bit "noisy". Some of them send sporadic messages. Normally the software from producer is aware and suppress them. Since Subtlearts had no such problem, I have not done any filtering assuming these devices are all "smart" and do this internally. But since several users have the problem, may be some magic is required for proper operation. We have to find out from where it come, I can fix it then.

Hi. Well, this is embarassing, but in all my testing I didn't manage to notice this, but yes, it is happening here too. And as with the others, if I switch back to the Frontier plugin, it doesn't happen. Sorry I never noticed it before! Shows why we need multiple testers... amazing the things that can go unnoticed when you're focusing on something else!
 
In my case - others should confirm this - it seems like when you move the fader and release it, after a second it moves back towards whatever position it was previously, not necessarily towards zero. So if it was at a lower volume before you moved it, it will move back down towards that previous, lower volume. But if it was at zero to begin with, then yes, it moves back towards zero.
 
It's important to note that the onscreen fader doesn't follow it - it stays where you put it with the fader, and if you move to another track and then move back, it returns to the 'correct' position.
 
The visual feedback in the plugin interface shows no change when this happens. The Fader Touched indicator updates when I touch and release the fader, but nothing changes when, I would say pretty much exactly one second later, it moves itself back to (or towards, it's hard to say if it goes to exactly the same spot) the previous value.
 
Hope that helps...
 
 
 

No, on further study it looks like mine 'auto-reverts' to exactly the previous value, wherever it was before I moved it. The onscreen fader stays where I put it, and if I go to another track and come back, it moves correctly to the new value.

Please test the following:
 
1) Switch to the "Logic" Tab.
2) Select "Fader touch"
3) Press "New" (new "Undefined" Action is selected then)
4) in "Action conditions", select "Note(On)", on the right side change "On" to "Off" (in the Actions list you should see "Note:Off - Undefined" then)
5) in "Action configuration" change "Undefined" to "Monitor reset". Down it, change "All" to "Fader:: Parameter Value Monitor"
 
So, you should see in the Actions list for "(Ch:1 N:104) Fader touch" the first action:
"Note:Off - Reset Fader : : Parameter Value Monitor"
 
Test either that helps.
 

Yes, that fixes it, here at least. (Sorry it took so long to get to - still busy with shows here. Better late than never though!)
 
Thanks for that - quick and easy. Not sure if you want to wait to confirm with anyone else first before putting it in the release version, but it works perfectly here!
 

Ok on version 0_3_r8b220 I don't have the disconnect issue.
 
If I open a new project, add three tracks and drag the fader of track 2 down some, after a few seconds the fader on the alpha track moves up (motor), but the value in Sonar remains adjusted.
 
Also, I have noticed that shift+rec button doesn't arm all tracks.
 
EQ stuff working great!! Props!