What's new

**UPDATE: New Firmware/Features 2/26/20** PreSonus FaderPort 8 and 16 Support MIDI CC Finally

PaulieDC

Too much gear, not enough composing. Oy vey.
================================================
UPDATE to original post, new firmware allows switching modes on-the-fly! Read More
================================================

ORIGINAL POST:
I've already posted new comments with this news in the existing threads from a few months back when we were still whining and complaining that these PreSonus FaderPort units have 100mm faders and we can't use them for CCs. Thing is, PreSonus DID that very update in the latest firmware, and it's as if they simply marked it complete on the PreSonus Feature Request page, and that was it. One of the reps for them did post here in our forum and announce it, but only in a reply, not a specific thread. I'm stumped.

Nonetheless, huge news, you can have eight 100mm faders plus a variety of knobs and buttons all with CC commands assigned to them. JL Cooper FaderMstr on steroids, with Transport control. Downside is, I believe the commands are pre-assigned by PreSonus, so what you get is what you get. I may be wrong, OR, they could add Midi Learn support in future firmware updates. But CC1 and C11 on Faders 1 & 2 will be where most spend their time I would think. Coming from a Mod wheel, I'll take it and learn it!

Anyway, here's how you upgrade if you have this unit or will be buying one, and here's how I got it working in Cubase 10 Pro. FYI, FaderPort 8 & 16 support MIDI CC, not the single fader units (original and V2):
  1. Download the latest Universal Control (right now it's v3.1.0.53214 for both OSX and Windows, released July 10th)
  2. Install UC. NOTE: If you run Waves Soundgrid and you work in Windows, disable the Soundgrid service. Otherwise, the UC installer will fail.
  3. Using UC, now update your firmware on the FaderPort. Even one purchased new will probably need this upgrade.
IMPORTANT: 5 years of working with various kinds of PreSonus hardware has shown something consistent--their stuff seems a little more susceptible to RF interference. I used to have a lot of connection problems with the FaderPort 8 and the Studio 192 interface, even firmware updates would fail. EASY SOLUTION: Use USB cables with ferrite chokes, those will filter RF interference. You may already have these laying around, wondering what the black barrel was for, lol. I would say this suggestion is mandatory, and very inexpensive to execute. You can get https://www.amazon.com/dp/B008VOPCGY (good quality cables) made by TrippLite on Amazon for under 7 bucks. I use expensive all-digital USB cables on my gear... wish I found these inexpensive ones earlier!

OK, setup to use the FaderPort (8 in my case) is super easy:
  1. Hold down the 2 Select buttons above fader 1 and 2 on the FaderPort, and power on the unit (you need the wall wart, it's not buss powered)
  2. Let go of Select buttons once it fires up.
  3. Select MIDI in the choices along the top of the FaderPort. Then select Exit in that same section. The FaderPort MIGHT reboot, mine used to but doesn't with this new firmware. The unit is now ready to transmit CC. Next, the DAW.

In your DAW (in this case, Cubase 10 Pro):
  1. In the Studio-->Setup window you should see the FaderPort listed (if not, add it as an external device).
  2. Then in the MIDI Port section, make sure it's Active, and that All MIDI Inputs is selected. The FaderPort didn't work for me until I did that.
That's it! At this point if I go to my M-Audio keyboard controller, the mod wheel will still work. BUT, once you move Faders 1 & 2, they take over and the mod wheel does nothing (at least on my CODE61).

I opened Spitfire Chamber Strings to test for the first time, and the smoothness of that long throw fader was a dream come true. I get it now, why 100mm is needed.

I've attached a 3-page PDF of the new MIDI section in the user manual. That's all PreSonus put into the manual, one page of setup, two pages with all the CC commands assigned to controls.

Hope all this makes sense. Holler if you have a question!
 

Attachments

  • FaderPort MIDI CC Chart.pdf
    653.3 KB · Views: 85
Last edited:
Sounds tempting. So you still get all the transport control functionality plus faders for midi CC's? What about the rest of the controls? I mean, where do they draw the line between the midi CC's and the rest of the functions? I'm guessing not, but is there at all a way to switch between the two modes while working?
 
Sounds tempting. So you still get all the transport control functionality plus faders for midi CC's? What about the rest of the controls? I mean, where do they draw the line between the midi CC's and the rest of the functions? I'm guessing not, but is there at all a way to switch between the two modes while working?
Great question, I will test that tonight. I'm going to assume that v1.0 of the CC addition doesn't support that. The thought is probably "hey you want a free JL Cooper? Then you lose the other stuff!", lol. I can create more than one instance of my M-Audio CODE61 in Cubase and have the keyboard instance drive libraries, then have the Mackie/HUI instance accept transport commands on the keyboard. I'll probably keep using the transport on the CODE61 because I'm used to it but I can test the FaderPort. It would have to allow multiple instances of course so that's the big question.
 
Does the Faderport 8/16 follow track selection in Cubase like the original Faderport classic?
Another good one to add to the list.

ALSO, you might be able to remap controls because it says it loads default CC commands nto the unit, allowing you to make a custom map. That's it, that's all it says.
 
Interesting.
It's not a hardware change so they did not add a button to switch from CC controller to mixer controller.
How doesn it work then to know what you're controlling? Does it recognize when the mixer session is on screen?

Edit: Actually the same question as Studio E. Sorry.
 
Interesting.
It's not a hardware change so they did not add a button to switch from CC controller to mixer controller.
How doesn it work then to know what you're controlling? Does it recognize when the mixer session is on screen?

Edit: Actually the same question as Studio E. Sorry.
On Page 59 of the latest user manual they give you a chart telling you what CC## is assiged to each control.

Funny, they HAVE a VI MIDI button but that just gives you control over MIDI tracks you've recorded. Doesn't do ANYTHING in MIDI CC mode.
 
Interesting.
It's not a hardware change so they did not add a button to switch from CC controller to mixer controller.
How doesn it work then to know what you're controlling? Does it recognize when the mixer session is on screen?

Yeah they need to impliment a way to switch from Mackie Control to MIDI CC mode without powering off and on.
 
Thanks a bunch for this! This convinced me to buy the Faderport 8 - haven't quite figured out how to get it working in Logic Pro X yet though. Luckily, I'm currently migrating to Cubase 10, and it works like a charm there. (However, if anyone have any idea of how to make it work in Logic I'm all ears)
EDIT: It works fine in Logic now, I just had to activate it in the "Midi Studio" in the audio/midi setup app.
 
Last edited:
Does anyone find motorized faders as or more useful than the faders included In a keyboard controller? I splurged in an Arturia MkII, which is still in customs, but hopefully will get to me in a few weeks. Of course, the faders in the controller are not motorized, nor do I know how good they are yet. I had decided I would use just these faders for mixing and midi CCs, but there are a few renewed Faderport 8 units on Ebay at a good price...here in Mexico prices are just ludicrous.

Do you find non-motorized faders that much inferior compared to motorized ones? The fact that the FP can now do midi CC is tempting. However, I was leaning more towards a breath controller rather than the FP faders.
 
Last edited:
I am using a Faderport 8 to control Studio One and a Behringer X-Touch Compact for CC control. Every fader and knob on the x-Touch can be assigned to whatever CC you want with the editor app.
 

Attachments

  • Studio 2019   2 (1 of 1) (2).jpg
    Studio 2019 2 (1 of 1) (2).jpg
    240.3 KB · Views: 57
I am using a Faderport 8 to control Studio One and a Behringer X-Touch Compact for CC control. Every fader and knob on the x-Touch can be assigned to whatever CC you want with the editor app.
I am sure that having dedicated devices is better, but I don't think that I'd do the same, mainly for the price. If I did buy the faderport or similar, I'd think of it doubling roles as a mixer, midi controller, and plugin control. So... Tripling duties, I guess.
 
I am sure that having dedicated devices is better, but I don't think that I'd do the same, mainly for the price. If I did buy the faderport or similar, I'd think of it doubling roles as a mixer, midi controller, and plugin control. So... Tripling duties, I guess.
I agree at full price. I got them both on eBay for a really good price. They were both like new, in the box. :)
 
Can you switch between midi CC and DAW control on the fly?
Nope, you have to turn in on and off to switch. And apparently midi CC is only fully supported for Studio One - I've been in touch with their customer support about the midi CC being quite laggy from time to time for Cubase, and the only reply was "please try and reproduce the error in Studio One and let us know if the lag persists".

There are a few buttons that simply don't work for Cubase and Logic with the Midi CC mode, but they do work for Studio One, and that's again what matters for PreSonus customer support.
 
Nope, you have to turn in on and off to switch. And apparently midi CC is only fully supported for Studio One - I've been in touch with their customer support about the midi CC being quite laggy from time to time for Cubase, and the only reply was "please try and reproduce the error in Studio One and let us know if the lag persists".

There are a few buttons that simply don't work for Cubase and Logic with the Midi CC mode, but they do work for Studio One, and that's again what matters for PreSonus customer support.


Thanks for the info..Do you regret buying it for Cubase?
 
Thanks for the info..Do you regret buying it for Cubase?
I would definitely hold off on it. I don't have the energy to try to find a new one - there are no perfect alternatives for it in the same price range. So I'll hold on to mine for the time being. But the lag is super frustrating - the reason for wanting full size faders is to get the super smooth control over expression and modulation etc. When it works, it's awesome. But then the fader stops working for 10 seconds, and sometimes 1 second, and the lag throws you off and ruins your flow.
 
I would definitely hold off on it. I don't have the energy to try to find a new one - there are no perfect alternatives for it in the same price range. So I'll hold on to mine for the time being. But the lag is super frustrating - the reason for wanting full size faders is to get the super smooth control over expression and modulation etc. When it works, it's awesome. But then the fader stops working for 10 seconds, and sometimes 1 second, and the lag throws you off and ruins your flow.


What Version of Cubase?
 
I would definitely hold off on it. I don't have the energy to try to find a new one - there are no perfect alternatives for it in the same price range. So I'll hold on to mine for the time being. But the lag is super frustrating - the reason for wanting full size faders is to get the super smooth control over expression and modulation etc. When it works, it's awesome. But then the fader stops working for 10 seconds, and sometimes 1 second, and the lag throws you off and ruins your flow.
+1
 
Top Bottom