Question

The Faderport is a wonderful piece of equipment which is well built and well designed. However, it can be improved by better accuracy.

When opening a project in Studio One with all faders to Unity Gain, it's clear that not all faders on my Faderport 16 are at Unity Gain. Some are slightly above, some slightly below Unity Gain. The devations can be pretty high: when reversing the test (setting all faders to UG and check the S1 prroject) I saw differences ranging from 0.8 to as high as 2.2dB. I had two in my possession the past month, and both suffered from this issue (although the first one was much worse than the second one). After mentioning it on the FB page, I learned that more people have noticed it. I've also seen it mentioned a couple of times on forums (both with Faderport 8 as Faderport 16)
 

I think the calibration routine should contain a step that asks the user to move all faders to UG position, after which the software can counteract any technical deviations in the faders. Or the problem should be solved in a different way.

Please vote if you think this part of the Faderport could be improved.

Answer 1

Thank you for the feature request. 

If anyone else agrees or disagrees, then please vote it up, or down. 

To vote:

In agreement click on the little blue triangle pointing up.

In disagreement click on the little blue triangle pointing down.

The developers pay close attention to those that are voted on the most. 

You are allowed one vote. 

Just viewing and agreeing but not clicking on the vote does not help the issue. 

Please click on one or the other. 

Answer 2

Hello

I have exactly the same issue on my faderport 16

It´s quite annoying

A little upgrade would be more than welcome

Answer 3

Yes, I had`nt noticed at first but it is slightly askew, not as far as 2db mind but definitely between 0.5db and 1db.

Here`s hoping for another update to rectify.

Answer 4

Same issue in Ableton live 10, On Mac OS, with Faderport 8.

When I launch my daw, faders in it are at 0 db, but the faders on the controller are between 2 or 3 db (randomly and not accurate) under 0db. So when I touch for the first time a fader, Live fader is going down to join controller's value ... It's very annoying !

For other faders under 0db in Live, when I touch for the first time the associated controller's fader, it brings up for 2 to 3 db !!!!

It's not good for the price of this unit ...

EDIT :

Talked to technical support :

My Ableton Push and my Presonus Faderport power supplies was inverted ! Too many power supplies under that desk, in a closed box with an APC anti-surge ...

So, with the good power supply, I could change fader speed and the controller entered in calibrating mode without any problem. The way faders are working is a lot better.

It still not 100% precise, with a -0.3 db at the very first touch of a fader, with any touch sensitivity.

Answer 5

Have an upvote! I have the same problem with my Faderport - at unity, the fader is slightly above 0 - very annoying.

Answer 6

Just got my Faderport16, download the latest firmware, but still the fader are not right calibrate.

The problem is still there!!!!  

I Hope Presonus will fix this probleem

Regards Cor

Answer 7

Been using mine since about April and this bugs me.  Especially as the scribble strips are flat and aren't particularly easy to read from a sat down position.  

Answer 8

I recently bought Faderport V2 and it is the same in Cubase. -3dbfs at the faderport label and 0 dbfs in the DAW mixer. When i reach + 6 in Cubase, which is the maximum, the faderport label shows 4. Right now i rely completely on the Cubase meter rather the label of the faderport V2 which is quit useless at the moment. Is there any way to tweak this ?

Answer 9

Same issue here, with Cubase.  Latest firmware, calibrated multiple times.  Seems like the last firmware update improved it very slightly, it was off by 3dB, now maybe 2dB.  It's a decent piece of kit, just needs more fine-tuning ability.

Answer 10

Almost 3 years later, still nothing new...

Answer 11

I brought it back to the store last year. The support answered as expected: It's a Steinberg (Cubase) problem, call them. I did, and Steinberg said: It's a Presonus problem. No good for me, so it's off my table now. A shame, since i really liked the product. THX !