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.

Mosvalve:
 
The WAI indicator stands for "Where Am I".  It is an indicator which spans the tracks that are able to be controlled by an external controller through ACT.  (In the console view it is a colored indicator on the bottom of each track that is a candidate for being controlled.)
 
Track strip selection is the capability, through ACT, for an external controller to select a track in order to make adjustments or changes.
 
Hope this helps,
Paul

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.
 
 

Thanks for the description of WAI. The only thing I noticed different with this unchecked is when I click on a track the faderport doesn't follow. That makes sense now by your description. I have to use the channel select arrows on the Faderport. Other than that everything works fine and I'm happier with this because now Sonar see's the Faderport every time and all my projects open, even much older one's now so it's a good tradeoff for me to use the channel select arrow buttons. I got tired of opening a Studio One project just to have Sonar see the Faderport.
 
I was using AZ and had to open a different DAW for Sonar to see it to as well. Now I don't need to use AZ. You should try using the Faderport and uncheck the WAI I think you will be much happier.

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.
 
 

BobF
So AZ is what is keeping the FP from being recognized initially? 
 

No, I was experiencing the same behavior with the Faderport Dll. Sonar began to see the Faderport every time after I unchecked the WAI. So it seems to have something to do with WAI at least in my case. I probably don't use all the functions of the Faderport like you do but it would be interesting to find out if all functions well for you with the WAI unchecked.
 

OK ... check it out.

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.
 

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. 

It sure is! Make sure that after loading your project, then removing and re-adding the faderport under control surface>preferences you reassign the Input and output in the dropdown list as well or the faderport will not function. 
 
The good news is once you get through your old projects you will never have to do it again!