• SONAR
  • What is link WAI indicator and track strip selection (p.2)
2016/10/30 18:46:20
tenfoot
....and don't forget to re enable WAI and track strip selection:) They won't be an issue once the midi I/O is sorted.
 
2016/10/30 19:10:27
Mosvalve
@tenfoot, I tried your solution. It seems to work to some degree but not on all projects. The Faderport will function fine once I remove and re-install but even after saving the project I have to repeat the process. It won't correct the midi I/O which is what you found to be the issue. On some other projects I can't get them to load even moving the fader. The Fader starts to shutter very fast so I have to shut down Sonar  from the task manager. I'll play around with it and see what happens but for now I'm ok with the WAI not checked. Thanks for this info it's real helpful. So it's a midi I/O issue. Interesting. I'm curious as to why it effects some and not others. Hopefully other will chime in and maybe this can get resolved once and for all.
2016/10/30 21:44:17
tenfoot
Hey Bob.
 If you are disabling the WAI link track function under utilities/Presonus faderport its usefulness is severely impacted as the motorised fader does not move with track selection. On the other hand if you are talking about the WAI setting under preferences/control surfaces, that is only the colour indicator showing which track is currently being controlled, so it will have no adverse effects on the faderport functioning. If disabling only that has fixed your issue, problem solved:) If it is the first I certainly encourage you to explore further!
 
I found consistency is paramount in getting the faderport to work correctly, and one thing that certainly helped was to ensure that the faderport was last on the list of both midi input and output devices, and to ensure that once set the order never changed. This setting is in the ttseq.ini file, located in appdata\roaming\Cakewalk\Sonar Platinum. Open the file in a text editor and the I/O order is located at the very bottom of the page, the LAST two numbered sections labelled 'midi in device map' and 'midi output devices'. Just cut and paste the device names after the '=' symbol to reorder them so that the faderport is last. Once you have them set either make a backup of the file in case of future problems or set the file properties as read only so that Sonar never reorders the devices. Just remember to change it back temporarily if you ever add any new midi devices.
 
The other thing, that you probably have already done, is to check that both key after touch and Channel after touch are enabled in preferences>midi>playback and recording.
 
Unfortunately for me at least there was no way around resaving projects with the Faderport enabled and working, even after setting the ttseq input and output settings,  but it certainly fixed the same issue you are having on my system and the faderport has been ticking along for a couple of years now.
 
if a project still won't load even when you move the fader, remove the control surface, then load the project and add it back in before saving.
 
As tedious as all of this is stick with it Bob - it is such a handy device and works transparently once it is behaving!
 
Other than that no doubt others here will have good ideas, and with a little luck Azslow will be along sometime soon and there is nothing he does not know about control surfaces:)
2016/10/30 22:31:52
Jimbo21
Every time I boot my computer the faderport "write" button is lit up. With it lit up, if I open Sonar the fader on the faderport will move back and forth quickly and like others here have mentioned, the project won't complete loading until I move the fader by hand.
 
But if I press the "write" button to where it is not lit up before opening Sonar, the project loads just fine and faderport works great.
 
i know it's not exactly what you've experienced, but maybe someone else is having this problem.
2016/10/30 22:33:27
Mosvalve
Bruce, I am disabling the WAI link track function under utilities/Presonus faderport. Yes I keep checking to make sure the key after touch and Channel after touch are enabled. Even though the fader doesn't move when clicking on tracks with the mouse it does move using the channel select arrows so it may take longer to get to a track depending on how many I have but I see that as a better tradeoff. I checked the ttseq.ini file and the order is correct. I am going to keep trying and hopefully I will get it to work with the WAI enabled. Right now with the exception of the WAI function the Faderport is working just fine. Thanks to your input I have a chance of getting it sorted.
2016/10/30 22:41:13
tenfoot
Cool - best of luck with it mate:)
2016/10/31 07:10:01
azslow3
For those who still go AZCtrl way.
Please check http://www.azslow.com/index.php/topic,163.msg1773.html#msg1773 and let me know if that preset solve the problem with initial FP recognition.
 
I do not have FP, FP has no documentation. I try to help but I do so blindly. I am not asking anyone to do any complicated things, just test what is working. F.e. I have asked (in other mentioned thread) OP to check switching modes on device itself. I can only help you if you help me to help you. If you do not need it, no problem from my side, just ignore this post
2016/10/31 08:21:28
BobF
azslow3
For those who still go AZCtrl way.
Please check http://www.azslow.com/index.php/topic,163.msg1773.html#msg1773 and let me know if that preset solve the problem with initial FP recognition.
 
I do not have FP, FP has no documentation. I try to help but I do so blindly. I am not asking anyone to do any complicated things, just test what is working. F.e. I have asked (in other mentioned thread) OP to check switching modes on device itself. I can only help you if you help me to help you. If you do not need it, no problem from my side, just ignore this post




A - I have downloaded and installed this preset and turned WAI tracking back on.  Quick question ... can you post the changes you made to implement this INIT function?  I would like to add this to my already existing and modified AZ preset.
2016/10/31 08:56:25
azslow3
BobF
azslow3
For those who still go AZCtrl way.
Please check http://www.azslow.com/index.php/topic,163.msg1773.html#msg1773 and let me know if that preset solve the problem with initial FP recognition.

A - I have downloaded and installed this preset and turned WAI tracking back on.

Sorry, but I do have not understood that statement. "WAI tracking" option exists in the original (Presonus) plug-in only. And AZController can not be used in parallel with it...
So, have you tried this preset with AZController only, after power cycling Faderport, so bringing it in position where it was not recognized before?
 

  Quick question ... can you post the changes you made to implement this INIT function?  I would like to add this to my already existing and modified AZ preset.

* One software state, "Initialize" with "Pending" (default) and "Done".
* One system hardware control "Init", with logical control attached.
* The logical control has single action, "Monitor" "Initialize" state
* In that monitor I check the state of "Initialize", and for "Pending" send 2 SysEx messages, then change the state into "Done".
 
If you publish you current preset (on my forum), I will apply the change (can save you some time, I need ~1minute to do this).
 
2016/10/31 10:15:15
BobF
azslow3
BobF
azslow3
For those who still go AZCtrl way.
Please check http://www.azslow.com/index.php/topic,163.msg1773.html#msg1773 and let me know if that preset solve the problem with initial FP recognition.

A - I have downloaded and installed this preset and turned WAI tracking back on.

Sorry, but I do have not understood that statement. "WAI tracking" option exists in the original (Presonus) plug-in only. And AZController can not be used in parallel with it...
So, have you tried this preset with AZController only, after power cycling Faderport, so bringing it in position where it was not recognized before?
 

  Quick question ... can you post the changes you made to implement this INIT function?  I would like to add this to my already existing and modified AZ preset.

* One software state, "Initialize" with "Pending" (default) and "Done".
* One system hardware control "Init", with logical control attached.
* The logical control has single action, "Monitor" "Initialize" state
* In that monitor I check the state of "Initialize", and for "Pending" send 2 SysEx messages, then change the state into "Done".
 
If you publish you current preset (on my forum), I will apply the change (can save you some time, I need ~1minute to do this).
 




This is where I had disabled WAI

 
I'll try to export my preset and post at your forum ...
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account