What happened
I've been using the Faderport 16 for over a year on dialogue mixes, usually non-overlapping stuff but I've noticed a serious problem, and I need to find out if its just my unit or not.
If a fader on my unit is moving due to volume automation, recording volume automation with any other fader results in the image I've linked to below.
Three images of volume automation recordings from the Faderport 16 for Reaper 6, Ableton Live 10 and Studio One 4 :
https://imgur.com/a/aymvkaT
This is likely to be noticable only on quicker movements of the fader, which as a dialogue mixer can happen a lot.
It essentially means the unit sends out less data, seemingly truncating it both in time and data range.
I've confirmed this behaviour in Reaper, Studio One and Ableton Live. Protools 11.3.1 unfortunately does not work at all with this units HUI mode.
I've already excluded USB connection issues, power supply troubles and system update issues(with the help of Presonus support).
What am I asking of you, fellow Faderport 8 / 16 users ?
Please record a few seconds of fast fader moves as volume automation on two tracks.
First pass on one of the tracks, second pass overlapping the first on a different track while the first tracks volume automation is played back on one of the faders of the Faderport unit
Make a screenshot of the volume envelopes you've recorded and attach it to your reply in this thread. Thanks.
Presonus support seems to think this isn't such a bad issue. :facepalm:
Note: I've received one verified report from a Faderport 8 user on MacOS Sierra with the same issue. Please keep those reports coming.
Presonus Faderport 16 - could this be a systemic issue ?
-
- KVRist
- Topic Starter
- 234 posts since 30 Sep, 2002
This problem has no been confirmed to me with screenshot evidence by two users of Faderport 8/16 users.
The Presonus support folks have told me today that they're passing this on to the dev folks, so we'll see what comes of it. Meanwhile, it can't hurt to check if your unit is affected. I did buy mine about 7 months after it became available, so I'm hoping it's a general firmware issue and I don't need to hand my unit in for repairs.
The Presonus support folks have told me today that they're passing this on to the dev folks, so we'll see what comes of it. Meanwhile, it can't hurt to check if your unit is affected. I did buy mine about 7 months after it became available, so I'm hoping it's a general firmware issue and I don't need to hand my unit in for repairs.
Will mix for fun