PreSonus FaderPort 2 (2018) midi remote script

The 1.000 th post - is @Clement_Panozzo going to win a price?

If so, I assume it’s not going to be the Behringer X-Touch … :wink: :rofl:

2 Likes

Hi Clement,

since there are many, many settings related to automation and the need to change these settings varies among users., the script does not provide a direct keyboard shortcut for toggeling the trim setting. Furthermore, this would only be useful if the Automation Panel is open at the same time.

However, there is a simple way to achieve what you want with fp-wizard:
In the Custom Mode on Custom Page 0, you can assign the trim function to the Write Button and the function for opening/closing the Automation Panel to the Read Button.

The fp-wizard release notes explain how the Custom Mode works. There is now also a key combination, Bypass + Shift, which allows you to call up the Custom Mode directly from anywhere.
So once you have assigned the Write Button and the Read Button as described above, simply press them in the Custom Mode and your desired function will be executed.

Best regards
CKB

1 Like

:grinning_face:

1 Like

Thank you, very clear !

2 Likes

Hi CKB, regarding your announcement to make Combined Panners available in fp-wizard, do you currently have any other features on your to-do list that we can perhaps look forward to? Sorry for being so curious. :smiley:

1 Like

Hi everyone.
I recently bought the Faderport v2, and I can’t get it to work with my Cubase 14. I came across this thread, but I don’t know what to do with the script you configured. Can anyone tell me what to do? Or is there another thread that explains it?

1 Like

https://forums.steinberg.net/uploads/short-url/v8dUmDurAhsQcnc6nPEQQjWDixF.pdf

this should be the link to all the pdfs that explain how to set up the system.

I copied it from above:

scroll up to 2. Okt 2025 by CKB ( the maker!) but use the latest script from the 3 Nov. 2025 (CKB)

It is quiet a bit to read but it’s absolutely worth it!

Good luck and enjoy it once you got it going

3 Likes

Hi butterlfy,
a major update of fp-wizard with many new features is in progress.
If what I have planned works, I will report on it so that you can be sure that you will actually get it. In any case, I have already had success with the implementation of Combined Panners.

Best regards
CKB

3 Likes
I think my head is going to explode

:exploding_head: . I can’t get it to work. I think I’ve followed all the steps in the PDF, but the script isn’t showing up in the MIDI manager. Any help would be greatly appreciated :folded_hands:

1 Like

I think you should give us a little bit more information here.

Are you on Win or Mac ?

Is your Faderport Firmware up to date and is your Faderport set to native mode ?

What’s the path to the script on your system ?

1 Like

Hi Christian,

cool to hear - I’m sure you’re busy, so I keep it short…

Reading currently thru the documentation about the mixer view/seeing your anouncement about the panner function I came to think it would also be convenient if “Solo exclusive”, “Solo defeat” and “Listen” could be accessed via button combinations - if possible at all via the MIDI remote API. Just a thought…

Thanks for all your hard work,

Best wishes,

Frank

1 Like

I’m using Windows 10, Cubase 14 Pro version 14.0.20 Build 240 (x64), and I’ve updated the Faderport firmware as described in the manual Volker Petersen gave me. I’ve configured the Faderport to native mode by turning it on, pressing Next, and then Solo. The script path is D:\Documents\Steinberg\Cubase\MIDI Remote\Driver Scripts\Local\PreSonus. The scripts that come with Cubase also go to the D drive, but instead of \Local, they go to \Public\

I had a Windows update problem. It hadn’t updated in years, and I was running version 21H2. With that version, I couldn’t install Universal Control, so I downloaded an update from Microsoft for 22H2. For what it’s worth, my PC now takes longer to shut down.

1 Like

Hm… looks OK so far.

I assume you powered on the Faderport Controller before you start Cubase -

if you open up the lower zone in Cubase (MIDI Remote) - can you see the PreSonus Script there ?

Is the Script listed in the “Studio” Menu/MIDI-Remote-Manager - in the tab “scripts” ?

1 Like

Hi Chuso,
that’s wrong, because you didn’t create the folder FaderPort under the folder PreSonus.
The folder FaderPort is where the script file needs to be copied.
Here’s the relevant excerpt from the Setup PDF:

Note: If you have defined the FaderPort in Cubase somewhere else because it didn’t work for you, you will need to change this back. * Best regards * CKB :smiling_face_with_sunglasses:

1 Like

Hi Frank,
the ‘solo defeat’ function was already on my todo-list and is working well here in my test version of the next update of fp-wizard. To perform the ‘solo exclusive’ function, you can use the existing functions. For example, if you are in Pan Mode, press Shift, Solo, Shift, Solo. I like it that way. The ‘Listen’ features will not be implemented, but maybe at a later date.
Best regards * CKB :smiling_face_with_sunglasses:

2 Likes

No, it does not appear in the list :man_shrugging:
From the remote MIDI manager, is it not possible to insert the script?
I added the folder that CBK told me to, but it still doesn’t work

Heyyyyyyyy, it’s fixed now. Sorry for the inconvenience. Thanks so much everyone.
It was a problem with the location of the scripts folder; for some reason, I have several.

3 Likes

Hi Christian,

thanks for the hint how to perform the “solo exclusive” function, though I

still think a button combination like “Bypass + Solo” would be more convenient - but at least one does not need to reach for a modifier key and the mouse.

Thanks, and for now I let you do your work :grinning_face:

Signing off

No, Frank. :wink:
We have Solo and Mute on the Main, Audio, QC and (Cue)Send Page.
We have unSolo all and unMute all on the Shift, EQ and PF Page.
Solo Exclusive is a functional extension of unSolo all.

Since in practice the unSolo all function is used much more often than Solo Exclusive, more users ‘think’ of the Solo Exclusive function as two steps in practice. Sacrificing the Bypass+Solo combination would therefore be far too disproportionate. We still need it for more important things later, but however, this would only be possible to a limited extent because:

If you have swapped the Mute Button with the Solo Button in the script using “const SwapSoloMute = true” so that the buttons and their LED colors on the FaderPort correspond to the colors in Cubase, and if “const no_Swap_for_Bypass_Mute = true” is also set, the combination of Bypass+Solo is already assigned to the ‘toggle monitor state’ function.

By the way: I also didn’t assign the ‘Solo Defeat’ function available in the upcoming version of fp-wizard to Bypass+Solo, but to double-click Solo. I always try things like this out for a longer period of time and then see what feels most ergonomic. :slightly_smiling_face:

1 Like

I agree with that also. If you plan to implement the listen function in your script later on, I think ‘Bypass + Solo’ would be the best fit. That’s probably your plan anyway, CKB.

1 Like