What is link WAI indicator and track strip selection

I've been having a hell of a time getting the Faderport to work in Sonar.
See post http://forum.cakewalk.com/Annoying-Process-to-Get-Sonar-to-see-Presonus-Faderport-m3439279.aspx
and post http://forum.cakewalk.com/My-projects-are-toast-and-Platinum-is-unusable-open-case-326713-RESOLVED-m3476790.aspx
Tonight I was doing more troubleshooting and I was going between the AZController and the Faderport Controller and was unsuccessfull with both. If you read through my other postes you will see what I mean. The two main problems was Sonar would not see the Faderport unless i opened a Studio One project first. The other was more inportant where the Faderport was preventing my projects to open. In the Faderport plugin I noticed a checked box (Link WAI indicator and track strip selection) For the heck of it I unchecked it and saved under a new name. Low and behole Sonar is seeing the Faderport everytime and every project is opening. I don't know what this (link WAI indicator and track strip selection) does but I have to assume it is what was causing all the problems. Anyway I thought it may help others to know. I am hoping this finally ends these problems for me.

I also end up having to open a different DAW first to get SONAR to recognize the FaderPort.  I've just accepted that that's the way it is.  Once I do that, the FP is fully functional and configurable using AZ.
 
 

So AZ is what is keeping the FP from being recognized initially?  I'll have to switch and see what happens.  For me it isn't 100% of the time, but often enough to be a PITA.
 
Button assignments are the reason I use AZ.  [Proj] does a File>Save.  [User] toggles input echo, [<<] and [>>] move by measures.
 
 

tenfoot
I use the faderport and have no issues with it being recognised or using both WAI and track strip selection. What I do remember is that when I first got it I had issues loading old projects that were saved prior to attaching the faderport as they messed with the midi I/O assignments and would cause a midi feedback loop which stopped projects loading. File loading would freeze and the fader on the faderport would shudder. If I moved the fader, the project would continue to load, but the faderport would not function until I removed and re-added it in the controller list. The solution was to load the project, then remove and re-add the faderport under preferences>control surfaces, then re save the song. I could then load the re-saved project without issue. It was a PITA resaving all of my old projects at the time, but it has worked flawlessly since.
 

this describes what was happening to me for the most part. I am going to try this. It's a pita as you say to do this with each project but it's worth a try. 

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

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

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.

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

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

I understand it now ;)
I have uploaded your preset version with initialization added.
 
EDIT: second typo within last 3 days... the first one was a broadcast that huge computer center is going into downtime (while the meaning had to be that it does NOT going to have downtime )

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.

Jim, thanks for this info. I just gave it a try but no cigar. It is amazing how the same product and driver works differently on different systems. There must be a common denominator somewhere.

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

When I load the AZcontroller my control surface window does not have ACT or WAI check boxes. It has the letter A and N checkboxes. Why is mine different. Also How do I install this preset? I installed AZ ver azctrl_0_5r2b337.exe.

Mosvalve

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

When I load the AZcontroller my control surface window does not have ACT or WAI check boxes. It has the letter A and N checkboxes. Why is mine different. Also How do I install this preset? I installed AZ ver azctrl_0_5r2b337.exe.

Widen the columns.  The A is the first part of ACT, the N is actually part of the W in WAI

I have found Ardour source for FaderPort! I will implement proper initialization tomorrow (there is "are you there?" -> "Yes I am... " -> "Use native mode please" conversation, not a problem to put that into the preset once it is known what to send and expect...).