I'm running windows 7, so I don't know about windows 10. Also, make sure you have both the AC adapter and the USB plugged in. I know it sounds stupid, but my faderport came unplugged once and I couldn't figure out why it wasn't working right.

Yeah!!!!!! I fixed it. Turns out all I needed to do was exit Sonar when I was done setting up the preferences and then re-open Sonar and Wholla!  (I did have to re-check Aftertouch settings though) But all is OK now. Thanks for your input Leadfoot. Glad you were on line to direct me to the video you recommended.

Glad to help!

I've been thinking about adding one of these for use with Sonar Platinum.
I figure it might be time to upgrade a bit from my Korg NanoKontrol, while still maintaining a compact profile
(My DAW desktop is getting a bit cramped since I added a 61-key controller!)
 
I'm currently running Windows 8.1, but anticipate upgrading to Windows 10 in the near future.
 
A few questions for folks that already use the Faderport - 

1. Are there any control functions on the Faderport that do NOT map correctly for use in Sonar?
2. Can the motorized fader be used as the Master volume fader AND for individual track volume faders & automation?
3. Any issues with Windows 8.1 or Windows 10?

Thanks in advance!
 
RR

Hi RR. 
 
1. No.  All of the buttons work. Mapping of the customisable buttons is also very straightforward. 
2. Yes. Pressing the output button assigns the fader to the first bus output.
3. No.  It works in all windows versions. 

Awesome -
Thanks tenfoot!

Need to resurrect this thread, folks.
 
I've had the Faderport for quite some time and initially used it as a transport control, but since day one I haven't been able to use it to write automation very well.  I set the automation mode to Touch and I'm always able to get a first pass with no problems.  But if I want to go back and redo a pass, SONAR's automation always jumps back to the previous pass if I'm trying to "hold" the fader at a certain level. Once I move the fader again, SONAR corrects itself and writes automation back to the appropriate level.
 
The "Touch" button on the Faderport lights up whenever pressure is placed on the fader, and it's pretty sensitive so I don't think it's the Faderport causing the problems because that button stays lit throughout the entire pass, even when I'm holding it at a certain level.
 
I've tried enabling/disabled the "Read" parameter during passes, thinking that perhaps reading automation while writing it is causing problems when I'm holding the fader in one place, but that hasn't made any difference.
 
Seems several people are using the Faderport in SONAR without any issues...are you successfully using it for multiple pass volume automation like I've described? If so, any ideas on what might be happening?

** crickets **
 
Yeah, so, am I correct in assuming that I'm the only one who's experienced this? Any ideas what I'm doing wrong? Or, could other Faderport users attempt to replicate and let me know?
 
 

I'll check into it later tonight (west coast USA time). I will report back to you what I find.

That would be great, thanks!