Page 1 of 1

Faderport MIDI mode problems

Posted: Sun Jul 18, 2021 11:15 am
by fl16
Hello everybody,

I'm new to this forum so I don't know if this has already been discussed.

I find Faderport useful as a Mackie controller but I find its MIDI mode very frustrating.

First of all you can send MIDI values from the faders to the DAW but if you try to update the faders from the DAW values, the faders are not updated correctly, which is one of the points of having motorized faders in the first place...Here's a long video where I explain in detail what is happening:
https://user.fm/files/v2-18550f7a42d1cf ... roblem.mp4
(jump to minute 3:10 to skip the setup and see what is not working)

Second, I mainly use the MIDI faders to control expression parameters for string ensembles, winds etc. As a result, I need to play, stop, record all the time while I move them however the play, rec, stop, rew, ffd buttons are not working as usual in MIDI mode and can't even be mapped to normal MIDI CC parameters.

Any help would be appreciated.

Re: Faderport MIDI mode problems

Posted: Sun Jul 18, 2021 9:06 pm
by Trucky
Welcome to the forum!
Are you using the latest FaderPort 8 firmware?
Any reason why you're not just using native Studio One mode and the [Edit Plugins] button, transport, etc. for this?
It's nice to have many of these mappings already done for many of these effects.

Also, don't forget Link mode. When [Link] is enabled, the Pan / Param encoder will control any parameter beneath your mouse. To lock a parameter to this encoder, press SHIFT + [Link].

Re: Faderport MIDI mode problems

Posted: Mon Jul 19, 2021 2:22 am
by fl16
Trucky wroteWelcome to the forum!
Are you using the latest FaderPort 8 firmware?

Thanks! Yes I'm using the latest firmware.

Trucky wroteAny reason why you're not just using native Studio One mode and the [Edit Plugins] button, transport, etc. for this?
It's nice to have many of these mappings already done for many of these effects.


Those problems in the MIDI mode are also present in the native Studio One mode but, regardless of that, there are several reasons for me to not use the native mode and Edit Plugins functionality:
1) I still have to use Cubase in many projects. Studio One still misses critical features for complex projects. So I switch quite often between Studio One (to play live or in simple recordings) and Cubase (orchestral scores). It is too time consuming to switch my Faderport between Mackie mode and native mode all of the time.
2) I need the plugin parameters to be predictable and adapted to my personal needs, so the default mappings don't suit me always. In particular I always map 4 parameters to the same faders to be able to develop muscle memory.
3) I often record a MIDI part and change instruments later to test different sounds or double certain melodies. It is essential that the parameters are recorded with the same MIDI CC data to be able to change the plugin and get the same or a similar expression.
4) Last and not least, standards are useful and I want to be able to use the same gestures in different DAW's. Proprietary gear is often a waste of time, particularly when products get discontinued. Mackie and MIDI are simply excellent and work with all DAW's and external hardware! No DAW is perfect so I will always need to use different ones for different environments. I also need to share projects with people working with other DAW's. Actually, Presonus also benefited from this: I started using Studio One because I was looking for a Mackie controller for Cubase and I got a free license with my Faderport.

Trucky wroteAlso, don't forget Link mode. When [Link] is enabled, the Pan / Param encoder will control any parameter beneath your mouse. To lock a parameter to this encoder, press SHIFT + [Link].


Thanks for that but both of my hands are busy already to take care of the mouse: one is on the MIDI keyboard and the other one on the faders 😅

Re: Faderport MIDI mode problems

Posted: Mon Jul 19, 2021 7:31 am
by Trucky
No worries. Have you reported your issues regarding MIDI mode to PreSonus support?
If not, I'd recommend submitting a Support Ticket (see link below) or creating a Feature Request.

Here's a PreSonus FaderPort 8/16 MIDI Mode setup and how to use video:
phpBB [video]

Re: Faderport MIDI mode problems

Posted: Tue Jul 20, 2021 3:28 am
by fl16
Trucky wroteNo worries. Have you reported your issues regarding MIDI mode to PreSonus support?
If not, I'd recommend submitting a Support Ticket (see link below) or creating a Feature Request.

I did. They basically encouraged me to buy another device (from another company, I guess) and closed the ticket.

Trucky wroteHere's a PreSonus FaderPort 8/16 MIDI Mode setup and how to use video:
phpBB [video]

I watched the video and I don't think that I have missed any steps.
Here you can see in detail how I set it up: https://user.fm/files/v2-18550f7a42d1cf ... roblem.mp4

Re: Faderport MIDI mode problems

Posted: Tue Jul 20, 2021 6:10 am
by Trucky
Thanks for reporting back and yes the setup steps in your video looks correct to me. Please note that direct comments from your support ticket were removed as that's not allowed in the forum.

Here's what I found (per the latest manual) in regards to why the FaderPort 8 is not receiving communication back from the software:
Image

I don't know if there's plans to change the implementation but you can always submit a Feature Request for this or vote it up if one already exists.
https://answers.presonus.com/search?q=faderport+feature+request

Re: Faderport MIDI mode problems

Posted: Wed Jul 21, 2021 6:43 pm
by pauldecesare
The transport controls don't work in MIDI mode, why is there discussion about firmware updates, etc etc? MIDI mode gives you preset CC numbers, there's NO programming and transport is disabled. Now of course you want motorized off when doing CC Expression, etc, but you have to stay in MIDI mode, don't hit both Shift buttons and go to DAW mode because the faderPort 8 WILL pick up where your channel faders are and move them there. That in itself is OK, but when you switch back to MIDI mode, there is NO memory of the CC faders plus the motorized is turned off. So your CC positions are totally messed up. You have to commit to MIDI mode and keep it there, and you have to MIDI-Learn everything in your library to match the hardcoded CC numbers in the FaerPort, nd you have no transport. This was a nice thing to try and bring us CC control for free, but unless those issues are fixed, it's not actually usable. Thats'a shame, because those 100mm faders for CC Expression are WONDERFUL, but the limitations and the huge footprint for three CC faders kills it.

I submitted a product idea to PreSonus for a 4-fader 100mm MIDIPort in the same case as the FaderPort, but I got told that submitting a product idea was in violation of something. Wow. The members of the VI-Control website went bonkers over the idea but PreSonus told me, it's customer, that I was in violation. Whatever.

Re: Faderport MIDI mode problems

Posted: Thu Jul 22, 2021 5:38 am
by fl16
Thank you Trucky, it was a very helpful post. I had missed that part from the manual.

Trucky wroteI don't know if there's plans to change the implementation but you can always submit a Feature Request for this or vote it up if one already exists.

Here are the links for the Feature Requests:

(I encourage those who believe like me that those are important features to vote for them!)

Make MIDI mode exclusive to faders (i.e. enable transport buttons ) + Friendlier MIDI mode shortcut
https://answers.presonus.com/62639/excl ... r-shortcut

Motorized faders in MIDI mode (to react to the CC values set from the DAW)
https://answers.presonus.com/62143/moto ... om-the-daw

Re: Faderport MIDI mode problems

Posted: Thu Jul 22, 2021 8:29 am
by Trucky
I agree @fl16 and voted for both of them.