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.
 

 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

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

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.
 

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!

I will update preset in the next update (and write here when that happens).
 
For Shift+X, my excuse is Frontier documentation: https://www.frontierdesign.com/download/pdf/AlphaTrack/SONAR_and_AlphaTrack_v1.0.4.pdf
SHIFT+REC - Clear All Record Arms (All Safe)
SHIFT+SOLO - Clear All Solos
SHIFT+MUTE - Clear All Mutes
 
May be they have updated plug-in since the documentation was written...
 
Toggle/Set Arm/Mute/Solo for all is currently not available in my plug-in, easy to add.
 
But can you provide more information what this "all" is doing (or you want it to do). There are for example "(Un)Solo selected tracks". Or you mean really all? And at which state I should consider Rec/Mute/Solo All instead of reverse operation, when all tracks are not rec/mute/solo or just some tracks are not rec/mute/solo? I hope you understand the question.

I have validated the fix to the fader movement that didn't match Sonar. Looks good.
 
Christmas wish list...
Definitely not in the documentation for the alphatrack >>
 
It would be so cool if the EQ control could enable/disable low-pass and high-pass filters, control Freq and Slope for both.
 
I think I see stuff for the various plugins as well. Can you share how to access that from the AlphaTrack?
 

Yes, subtlearts >> Exactly what you said.

For controls of low and high pass filters, it would be best if they were choices in the EQ list.

gswitz
Also, I would like to make a flower contribution, but my German is terrible...
Paypal $ to...
Zweck @ ...
To this address?

No, "zweck" is "purpose". The address is written on the top of this page, "admin at azslow.com".
I have tried to figure out how to change the PayPal link so it is shown in English, but no luck so far...
 
I have uploaded new build, b221:
* fader should work as expected (thanks for spotting and testing)
* Shift+Rec/Mute/Solo toggle instead of always switching off
 

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

I think I can manage that before Christmas
 

I think I see stuff for the various plugins as well. Can you share how to access that from the AlphaTrack?

The first "Page" in Plug-in mode should work like on original AT. Does not work with ProChannels no Synth.
The second "Page" in Plug-in mode in "ACT Speed Dial". Touch whatever parameter of synth/prochannel/FX by mouse and control it with the third AT encoder then. Flipping/automations should also work... theoretically.
 

frankjcc
The fader fix mostly works, but something is still going on that not quite right.

Can you test the latest version and report either it works for you?

Second issue (I suspect this is related to the value increment of the knobs)
When you have markers set in the time bar or whatever it is, While the transport is running in playback, I can turn the center knob on alphatrack to go forward to each marker, but I can only go back to the nearest marker.

That is more logical problem... I always go "left" to the next marker. I mean exactly next. In play mode, at the very moment you have moved to marker by one encoder "click", the transport has already moved to the right. So, next click move you to the same marker again.
 
Can you test either one trick works? Go to the "Logic" tab, select "(Ch:1 CC:17) Middle Encoder". Click on "GoTo Marker back from Cursor -1 *". In the lower part of the window, change "-1" to "-2". Test the result (in play mode). If that works as you expect, I will modify the preset (that action should be duplicated, so when transport is in "Play" it moves by 2, and by 1 when not).
 
 

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.

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.

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.

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

Never mind I found it, testing now