When I am mixing in Studio One 4.6 using the Faderport 16, the fader jumps up to zero db when I release my finger if I stop moving the fader at -2.7 db or louder. It is occurring on all of the faders.
Any suggestions? Thanks. Edit: I just noticed that this behavior only occurs when the "Shift" button has been selected. Is this fader behavior a bug or is there some logical reason for this? Seems like a pain to always have to be sure the shift button is not selected when using the faders. |
this has been happening to me too, no automation involved anywhere in the song.
It started with the last firmware release and I can find no pattern of when, what fader, etc makes it happen. |
darrenporter1 wrotethis has been happening to me too, no automation involved anywhere in the song. Is your Faderport also only exhibiting this behavior when the "Shift" button is engaged? |
OK I had time to test this out this morning and YES I CAN confirm that this is ONLY happening when the FP8 is in a "shift lock" state; ie: the "shift" button is lit-up orange.
This needs to reported as a bug, but at least I know now what to do if it starts happening. Thanks for helping to confirm that this is not just "all me" and a huge relief my hardware isn't broken! |
Its not a bug but a feature. It allows quick resetting of channel faders to unity if one wants to reset and start again from that position. Its actually really excellent once you start using it. Simply disengage SHIFT mode for normal operation. It is not hard to do.
Shift mode has alternate functions and will probably get more. Best to use Faderport in non shift mode for normal expected operation.
Specs i5-2500K 3.5 Ghz-8 Gb RAM-Win 7 64 bit - ATI Radeon HD6900 Series - RME HDSP9632 - Midex 8 Midi interface - Faderport 2/8 - Atom Pad/Atom SQ - HP Laptop Win 10 - Studio 24c interface -iMac 2.5Ghz Core i5 - High Sierra 10.13.6 - Focusrite Clarett 2 Pre & Scarlett 18i20. Studio One V5.5 (Mac and V6.5 Win 10 laptop), Notion 6.8, Ableton Live 11 Suite, LaunchPad Pro
|
Well then that feature sucks IMO.
Faders should always operate "normally" no matter what the shift state is. Having to verify that shift is not locked every time I want to adjust a fader is just nonsense and a workflow killer. |
It depends on how you look at it. It is not a workflow killer for me. It is an enhancement.
Undo will put any faders back if you have accidently moved them in Shift mode.
Specs i5-2500K 3.5 Ghz-8 Gb RAM-Win 7 64 bit - ATI Radeon HD6900 Series - RME HDSP9632 - Midex 8 Midi interface - Faderport 2/8 - Atom Pad/Atom SQ - HP Laptop Win 10 - Studio 24c interface -iMac 2.5Ghz Core i5 - High Sierra 10.13.6 - Focusrite Clarett 2 Pre & Scarlett 18i20. Studio One V5.5 (Mac and V6.5 Win 10 laptop), Notion 6.8, Ableton Live 11 Suite, LaunchPad Pro
|
darrenporter1 wroteOK I had time to test this out this morning and YES I CAN confirm that this is ONLY happening when the FP8 is in a "shift lock" state; ie: the "shift" button is lit-up orange. Thanks for documenting your find. After I saw the moderator's response I looked and did see it mentioned in the manual. (Page 8 I think.) IMHO I think that it could be a useful option, but perhaps it would be better if we could enable this function using one of the "User" buttons. At least we are aware of it now and will have to work with it. Cheers! |
robertcollins4 wroteWhen I am mixing in Studio One 4.6 using the Faderport 16, the fader jumps up to zero db when I release my finger if I stop moving the fader at -2.7 db or louder. It is occurring on all of the faders. Wow This happened to me this morning exactly as you described. I had 3 vocal tracks and was balancing using my F8 when the Fader on the first track snapped to Unity. I also suspected maybe some automation was written that I didn’t know about but nope that wasn’t the case. Weird that of the 3 vocal tracks only the first one exhibited this behavior. I use console scenes and have “Shift + All” enabled so my scenes are replicated on the F8.
Mac Mini (Late 2014)
Processor: 3.0 GHz Intel Core I7 Memory: 16 GB Presonus. Studio One Pro V6 Presonus Quantum Hardware DBX 160a Hardware DBX 160XT GA. LA2A (clone) GA. LA3A (clone) WA76 1176 (clone) WA EQP Pultec (clone) WA 73 Neve (clone) Softube. Console 1 MK3 (pending) Presonus. Faderport 8 (dual) "God's grace" |
frank.crow wroterobertcollins4 wroteWhen I am mixing in Studio One 4.6 using the Faderport 16, the fader jumps up to zero db when I release my finger if I stop moving the fader at -2.7 db or louder. It is occurring on all of the faders.
Mac Mini (Late 2014)
Processor: 3.0 GHz Intel Core I7 Memory: 16 GB Presonus. Studio One Pro V6 Presonus Quantum Hardware DBX 160a Hardware DBX 160XT GA. LA2A (clone) GA. LA3A (clone) WA76 1176 (clone) WA EQP Pultec (clone) WA 73 Neve (clone) Softube. Console 1 MK3 (pending) Presonus. Faderport 8 (dual) "God's grace" |
Jemusic wroteIt depends on how you look at it. It is not a workflow killer for me. It is an enhancement. It’s actually a significant inconvenience for me because I learned from a link on this forum to “Shift+All” so that my console scenes would be replicated on the F8. I mix in sections so moving from section to section or even just being able to jump to a section (group) to make an edit or update using scenes and having my faders ready to go has been great (actually a game changer) but now that is compromised.
Mac Mini (Late 2014)
Processor: 3.0 GHz Intel Core I7 Memory: 16 GB Presonus. Studio One Pro V6 Presonus Quantum Hardware DBX 160a Hardware DBX 160XT GA. LA2A (clone) GA. LA3A (clone) WA76 1176 (clone) WA EQP Pultec (clone) WA 73 Neve (clone) Softube. Console 1 MK3 (pending) Presonus. Faderport 8 (dual) "God's grace" |
Jemusic wroteIt depends on how you look at it. It is not a workflow killer for me. It is an enhancement. So yet another step to "fix" a workflow killer? yeah... that's helpful.... |
frank.crow wroteJemusic wroteIt depends on how you look at it. It is not a workflow killer for me. It is an enhancement. This hits the nail on the head right here... it neuters what I consider an essential function of the FP8/16... scenes and quickly navigating them. I have my navigation keys mapped to user F-keys and leave my FP8 pretty much shift-locked almost all the time. Even when tracking I leave it shift-locked for easy one-handed access to Save and Undo. |
I put in a support ticket but I’m not too optimistic. I was reading the most recent manual and this behavior is actually listed as an updated feature.
Mac Mini (Late 2014)
Processor: 3.0 GHz Intel Core I7 Memory: 16 GB Presonus. Studio One Pro V6 Presonus Quantum Hardware DBX 160a Hardware DBX 160XT GA. LA2A (clone) GA. LA3A (clone) WA76 1176 (clone) WA EQP Pultec (clone) WA 73 Neve (clone) Softube. Console 1 MK3 (pending) Presonus. Faderport 8 (dual) "God's grace" |
Cool. Thanks for opening that. Be sure to point them to this thread so they can see that not everyone is thrilled about this "updated feature" they stuck us with!
|
frank.crow wroteI put in a support ticket but I’m not too optimistic. I was reading the most recent manual and this behavior is actually listed as an updated feature. Did you get any feedback from Presonus on this? It's starting to drive me absolutely NUTS. I am about to ask for the previous firmware so I can downgrade because this sucks. |
The tech asked me to send a spx file with the faderport connected. The response was that he was in the process of testing it out. But then he asked for a video of the problem. At that point I gave up because the issue I felt was super clear and I took it as an indication that it was going no where. My ticket was closed.
I actually just got a second monitor and put the console on that screen and I just bank. It sucks but it will have to do for now.
Mac Mini (Late 2014)
Processor: 3.0 GHz Intel Core I7 Memory: 16 GB Presonus. Studio One Pro V6 Presonus Quantum Hardware DBX 160a Hardware DBX 160XT GA. LA2A (clone) GA. LA3A (clone) WA76 1176 (clone) WA EQP Pultec (clone) WA 73 Neve (clone) Softube. Console 1 MK3 (pending) Presonus. Faderport 8 (dual) "God's grace" |
Users browsing this forum: No registered users and 10 guests