+1   If USB Power management is powering down the Faderport, it could be causing the problem.
 
Go into "Device Manager" in the control panel and click the "Universal Serial Bus Controller" tab to open.  Double click each device in the list, to see if they have the "Power Management" tab.  If they do, make sure the "Allow the computer to turn off this device to save power" box is not checked.
 

 
Also check control panel "Power  Options".  First to see what Power Plan you are using, then secondly to go into advanced settings for the plan and check each setting in the list.
 

 
 
 

gustabo
Do you have USB Power Management turned off?

gustabo
Do you have USB Power Management turned off?

No but I changed it to off, can't hurt.

bapu
The only support I can provide is that my faderport works solidly *without* the AZController.
 
It works in Reaper, Mixbus 3/32C and of course Studio One Pro 3 no matter which one I open in any order.
 
IIRC on my system I had to go one rev lower on the then current driver.

I changed to the Presonus Controller and so far Sonar see's it every time, every project. After changing it I shut down my system and restarted just to be certain any settings were cleared out. Hopefully I'll have no issues now. I don't know how to set it up to use with plugins though. Do you use it to control plugins?

So far so good since changing to the Presonus Controller. What is the advantage with the AZ Controller?

Mosvalve
So far so good since changing to the Presonus Controller. What is the advantage with the AZ Controller?

Pro:
+ it does more out of the box
+ it can be modified to do what you want
+ you have "no name", but quick and existing support
Cons:
- if there are problems, some cooperation is required

azslow3
 
Pro:
[...]
+ you have "no name", but quick and existing support
[...]

I always get a chuckle reading these hidden comments... quick translation "Alexey, get him while he is still here!"

Mine seems to work with both, but the motorized fader does not move.  Any magic required to get this to work?
 

mettelus

azslow3
Pro:
[...]
+ you have "no name", but quick and existing support
[...]

I always get a chuckle reading these hidden comments... quick translation "Alexey, get him while he is still here!"

Nothing hidden, in direct comparison with original plug-in, "Alexey" does not sound as convincing as "Presonus", but there are more chances that I fix/change something.
 

patm300e
Mine seems to work with both, but the motorized fader does not move.  Any magic required to get this to work?

That is bad.... Only one check: in the AZController, go to the Overview tab and in the Current Software State select "Fader touched". Touch the fader for a while then move your hand away from the device. Do you see that line is changing from (No) to (Yes) then again to (No) ? If that indication follows your operations, "Motor" (in the same list) is "On" and LEDs on buttons are working correctly, sorry to say but your Fader is broken...

patm300e
Mine seems to work with both, but the motorized fader does not move.  Any magic required to get this to work?
 

You may have already done so, but make sure you have enabled key aftertouch and channel aftertouch in Sonar. Go to preferences>midi>payback and recording. The motorised fader also only works with the power adapter attached.

BobF
I can't help beyond offering encouragement.  The FaderPort/AZ Controller combo has been rock solid for me in Sonar.  It also works quite well in Reaper (I use a user contrib controller there too).  Switching back/forth is no problem.
 
Hopefully you'll get it figured out and have the same great experience.  Hang in there - it's worth it.

Same here. I just recently picked up a Faderport and love it with SPLAT.