Presonus FaderPort: Good, Bad Ugly?

I bought a used Faderport for around half the price, but got the money back because of the pan knob was randomly jumping when used. I googled it and it seems to be a pretty common bug, but then if you get a Faderport with a working knob they seems to hold.
I have looked for alternatives, but I haven't really find anything in contention so will probably buy a new one close-by to reassure the knob will work.

I've had one for about 4 years, and it has always been rock solid. I love it. I'd buy it again in a second.

-edited for spelling

Leadfoot
I've had one for about 4 years, and it has always been rock solid. I love it. I'd buy it again in a second.

-edited for spelling

I am impressed to see that a new driver was just released last December, this could have addressed some of the issues people are referring to.

I have been using my Faderport since 2007, I got it for free with the purchase of a presonus firestudio project.
Actually they both work great but I don't use the FSP anymore cause I have a Focusrite Scarlett 18i20.

I would never connect any USB device with a 30 foot cable. There is your problem right there. Try a 6 foot cable and see what happens.  It has never mal functioned for me either.  It still works best in Studio One. 
 
Be advised that Faderport 1 runs at USB 1 speed.  And it will drop everything else that is on that same USB port down to USB 1 speed too. (Presonus make that quite clear BTW) So you really should not share it with anything else.  Most computers do provide separate USB ports which are often in pairs.  I found an unused USB port pair on my motherboard and just had to install a PCI type panel that connected to the unused ports. 
 
Another option is a PCI card that provides USB ports.

Your symptom indicate the device disconnects/reconnects. When that happens, devices/ports in Windows change. Sonar (current version) is especially picky about that (some bugs).
 
I would recommend:
1) check that USB power management in Windows in disabled.
2) try powered USB hub. F.e. I use 10m powered hub and all devices are working fine with it.

iRelevant

Audioicon
[...]
I connected it via a 30ft USB cable, the performed the setup as required.
[...]

I'm not absolutely certain about this, but think the specifications for USB indicates a max. cable length of 5m (ca. 15 foot) for USB2, and max. 3 m for USB3. For USB1 I don't know, but assume it's the same as for USB2. 
Problem with a to long cable is that you likely get communication error between device and computer.

Do you have trusted reference for exact length? I have seen many places which reference "5m". Interesting that I have not found this (not any other concrete) number in the USB specification 
They describe it in different terms:

* The maximum allowable cable length is determined by signal pair attenuation and propagation delay.
...
* The maximum cable length is limited by the voltage drop across the GND lead

Followed by the table for particular electrical limits.
 
From theory to practice. As I have already mentioned, I use 10m (32.8ft) separately powered USB hub for more then 3 years. And I was using it with: TC Helicon GTX Play (firmware updates, presets exchange, audio interface), DP (MIDI) and VS-20 (MIDI controller, audio interface). I had no problems with any of these devices. They all are USB1.1. But (one strip) Faderport is also USB1.1 
 
 

azslow3
Your symptom indicate the device disconnects/reconnects. When that happens, devices/ports in Windows change. Sonar (current version) is especially picky about that (some bugs).

So here is something else I am noticing:
I have several Mackie MCU/XT, the main MCU unit is connected to the computer via USB but I do not keep the device on when not in use. When I turn the MCU off, it's USB port under devices in Sonar disappears. When this happens, the FaderPort jumps to another MIDI device port.
The Mackie MCU USB Ports are not available in Sonar when the MCU is switch off.
NOTE: The MCU is not USB Powered.

This morning I went to the studio and turn on the computer to confirm that the FaderPort has stopped working and when I checked connectivity I noticed the FaderPort was communicating on a different MIDI device port.

I switched it back to "FaderPort" and everything started to work as needed. I restarted the computer and even shut down the computer and everything still works. However as soon as I add another USB device and turn the device off, the FaderPort jumps ship.

Unlike the FaderPort, the MCU does not have drivers of Firmware for computer so they are like removable devices, meaning as soon as you plug it in then the ports come to life.

azslow3
1) check that USB power management in Windows in disabled.
 

Yes I noticed the Power setting were set to balanced, I switched to High Performance and it's like the world has changed, I can feel gravity. Hopefully this helps.

azslow3
2) try powered USB hub. F.e. I use 10m powered hub and all devices are working fine with it.

I have never used a USB hub before but you've got me thinking. Lets say I get a HUB and use like a 15FT Cable  to the HUB, will using another 15 from the Hub Mitigate any issues with USB cable length?

Given the FaderPort cost me $129.00, I honestly do not mind the extra headache. At least it does not screw up between projects for me and so I am happy with it.

Thanks my friend.

Audioicon

JonD
There's always the wireless alternative.  If you already own an iPad or Android tablet, it might be worth looking into the controller apps out there.

I know this is going to sound counter intuitive but I hate touching screens and Wireless connectivity. I am a young but very old soul addicted to knobs and sliders. 

Maybe some day.

A New Age Luddite!
 
All good, dude! I completely agree with you...and I'm probably the age of your grandparents. 
 
Until my stubbornness starts to cost me a lot of money and headaches.
 
My studio is currently in my loft and my vocal 'booth' is elsewhere in the house. I tried lots of different 'solutions'. The one I settled on was Studio One Pro on my PC and Studio One Remote on an old Android tablet that hasn't gotten an update for almost 3 years.
 
That combo works really well. It gives me remote transport control, and metering and gain control for the incoming audio. It's the metering and gain control that stand out. As far as I know, TouchOSC and other OSC apps don't provide live metering. If others know of a way to accomplish that with OSC, please advise.
 
In any case, for this specific narrow use case, wireless proved to be the best solution.
 
So I guess it's kind of a good thing that my voice sucks and I don't use the remote app often. LOL

Audioicon
 
...
So back to this topic, I used to have the same problem but I use a Display Port and a Wireless Mouse. Using a Display Port, you can have up to 50ft Cable from your computer to your Monitor.

In the Booth I have a Monitor, a Wireless Keyboard and a Mouse. And so I can see and control everything.
But I have to tell you, the way you explain this thing has got me thinking.
...

Clever. Not one of the solutions I considered.

WallyG

Audioicon
Very very interesting:
First I have to tell you, the Presonus is growing into an industry giant and they and bringing out some really great stuff. I am thinking about switching to Studio One just because of the controllers alone, I really love what's going on down there....

 
I was thinking about getting the Faderport 16. The 16 faders would look cool, but then I already owned an X-Touch and with the way Studio One works, (with a push of a button on the X-Touch,) I can show AND control, audio, instruments, busses, and VCA, either separately or any combination.  I don't usually need more than 8 faders. In addition with an iPad running SO Remote, I do have 16 channels.
 
With this set up plus my Corsair Gaming Mouse, it is rare when I have to use the Keyboard.
 
Walt

This is really cool setup. I use the Mackie MCU and Some Xtenders. Works very well with Sonar.
I know Behringer released the Xtenders for the X Touch and so you can cascade.

The MCU are great but they have a screen problem when the LCD goes Dark after 4 years. Not sure why Mackie will not address that but something to keep in mind.

Thanks a sharing that image.

Midiboy
I just got my FaderPort 8 maybe 3 weeks ago and I love it.  It's amazing how much it has improved my workflow.  Plus my wife thinks it's creepy when the sliders start moving themselves when I automate a track.  

What are your thoughts on the Pan knob. So far I like everything except the Pan which does not zero out.

Have you noticed that?

Read the manual please! The pan knob only needs to be pushed in order to centre it!
 
I would not connect a monitor either with 50 ft of cable to your display port either. You may suffer picture quality loss when you do this. Well this used to happen trying to feed screens over a long distance and it may be better now but I still would not do it.
 
Faderport 8 and 16 still work way deeper with Studio One than any other program as well. It is designed for Studio One.  The rest are just extras. 

Jeff Evans
Read the manual please! The pan knob only needs to be pushed in order to centre it!
 

 
Are you sure?

The knob on my Unit does not Push in, by the way, by nature and instinctively, that was the first thing I attempted to do. My Mackie MCU does have the feature to pushed in and centered.

Jeff Evans
I would not connect a monitor either with 50 ft of cable to your display port either. You may suffer picture quality loss when you do this. 

I have no signal loss and never experienced issues. I am not doing graphic design or playing video games which would be of signal concerns.

I am using an EVGA, NVIDIA GForce GTX 6060TI, this support ups to 4 independent monitor connectivity. With an ASUS Sabertooth X79 MOBO.

Audioicon
I have several Mackie MCU/XT, the main MCU unit is connected to the computer via USB but I do not keep the device on when not in use. When I turn the MCU off, it's USB port under devices in Sonar disappears. When this happens, the FaderPort jumps to another MIDI device port.

Ok, thats it.
That is known Sonar bug. Introduced in some 2017 update. After that update, Sonar hates any changes in MIDI devices and break all Control Surface assignments once such change is spotted. Sometimes it does that without showing (so you still see correct ports in Sonar preferences, but it really use different ports). Sometimes INI file has to be removed before it can work normally again.
I guess nothing can be done with that till new owner starts the development (and consider that issue is a priority problem).
 
The only proved workaround: read lock INI file and always start Sonar with the same set of MIDI devices powered (and attached to the same USB ports).
That is not feasible for me and one of the reasons I was running fast once Cakewalk was closed...