PreSonus FaderPort 2 (2018) midi remote script

Cubase
,
948

Hello Clement, perhaps your motorfader needs to be recalibrated. I just asked CKB about this here yesterday. He will perhaps reply shortly to this. :upside_down_face:

1 Like
949

@Clement_Panozzo
@butterfly
@all

Dear friends,
it looks like Clement needs to calibrate the motorfader of his FaderPort.
This is actually done automatically on a new device, but as it is not pointed out in the original manual of PreSonus, you may accidentally cancel this calibration without realizing it.

Calibration is required in the following case:
You move in Cubase on the screen with the mouse in the mixer view the volume fader of a track to a new value, e.g. from 0 dB to -6 dB while this Cubase volume fader is synchronized with the motorfader of the FaderPort. If you then touch the motorfader on the FaderPort and this leads to a large jump of the volume fader in Cubase on the screen, a calibration is required.
A minimal jump cannot be completely ruled out, e.g. 0.1 dB close to 0 dB, depending on the value itself. Calibration is (I assume) necessary if the motorfader has been used a lot or if you have accidentally held the motorfader while it is being moved automatically by its motor.

Calibration is somewhat complicated with the single fader FaderPort, but works very well if you pay attention to everything. Note: The calibration runs through twice!

This software must be installed in order to load the latest firmware into the FaderPort:
UNIVERSAL CONTROL Software from PreSonus (Version 4.6.1.104762 or newer)
Note: During the calibration, an old factory firmware is loaded into the FaderPort, therefore the new firmware v3.74 must be reloaded again!

First of all - before starting the calibration - it is important that the new firmware v3.74 is installed on the FaderPort. There are detailed instructions for this in the setup-pdf of fp-wizard.

Now perform a factory reset and reload the new firmware v3.74 like this:

  1. switch off the FaderPort (= power off)
  2. wait 5 seconds
  3. press and hold the Prev button while powering on the FaderPort
  4. wait for the FaderPortā€™s Read LED to flash
  5. release the Prev button
  6. press the Read button
  7. wait until the Read LED lights up permanently red or the Read LED is off
  8. switch off the FaderPort
  9. wait 5 seconds
  10. switch on the FaderPort (then many button are flashing)
  11. wait 5 minutes - While this, the calibration is running like this: the motorfader automatically makes small movements with pauses (Note: The time of a pause can be longer than a minute!) in between, then there is a larger pause, then the motorfader makes larger movements, then there is a another pause, then the motorfader makes many very fast movements, then the motorfader continues to make various movements.
  12. press the (original) Solo button
  13. switch off the FaderPort
  14. wait 5 seconds
  15. switch on the FaderPort
  16. Note: now a wrong old firmware (e.g. v3.21) is installed
  17. reload the new firmware 3.74 with the UNIVERSAL CONTROL Software as described in the setup-pdf of fp-wizard
  18. after that, the Read Button is flashing green
  19. switch off the FaderPort
  20. wait 5 seconds
  21. switch on the FaderPort (then many button are flashing)
  22. wait 5 minutes again - While this, the calibration is running again completely.
  23. press the (original) Solo button
  24. switch off the FaderPort
  25. wait 5 seconds
  26. switch on the FaderPort

Much success and best regards
CKB (Christian) :innocent:

6 Likes
950

Hi CKB
You understood what I described and your calibration process works peefecyly ! Thanks a lot !

2 Likes
951

Nice to hear that the calibration worked for you, @Clement_Panozzo. I have two FaderPorts and the older one also made these jumps at some point. At that time I thought it had to do with the time of manufacture, but then I discovered this calibration option on the PreSonus support pages, but itā€™s difficult to understand there. Thatā€™s why I divided these instructions here into the 26 steps. Now Iā€™m even a fan of my older FaderPort, because the Rotate Knob is smoother due to the longer use and turning it with the attached rubber ring is very comfortable for me. :smiling_face_with_sunglasses:

1 Like
952

new update available - July 15, 2025

Dear friends,

here comes a new update of fp-wizardā€¦
The operability of the Rotate Knob in the EQ Mode has been improved as follows:

(1) Every small step of a rotation now leads to a reaction, i.e. to a change in value. It is also no longer necessary to turn the Rotate Knob more forcefully if the value of the parameter is at a position that typically snaps into a default value in Cubase.

(2) For each EQ Band, the Gain Parameter can now be set within a stable grid. The entire range between -24 dB and +24 dB is now precisely and evenly divided into 120 steps with an interval of 0.4 dB. As before, this interval offers the option of controlling the EQ Gain Parameter musically and dynamically via recording as automation data.

(3) For each EQ Band, the Frequency Parameter can be set in a special high-resolution grid. This grid contains 224 values, which are all individually defined and provided as fixed values by fp-wizard. The provided values are common and understandable values, i.e. no ā€˜crookedā€™ values.

(4) Depending on different frequency ranges, the interval between the individual frequencies varies as follows:
(a) Interval of 5 Hz for the frequency range between 20 Hz and 120 Hz.
(b) Interval of 10 Hz for the frequency range between 120 Hz and 400 Hz.
(c) Interval of 20 Hz for the frequency range between 400 Hz and 1000 Hz.
(d) Interval of 50 Hz for the frequency range between 1000 Hz and 2500 Hz.
(e) Interval of 100 Hz for the frequency range between 2500 Hz and 8000 Hz.
(f) Interval of 200 Hz for the frequency range between 8000 Hz and 20000 Hz.

(5) While setting the Frequency Parameter, it is still possible to reset the EQ Bands to their default frequencies (100 Hz, 800 Hz, 2000 Hz, 12000 Hz) using the Section Button. Some values of the high-resolution grid that are less close to these default frequencies are skipped individually for each EQ Band when the Rotate Knob is turned, so that Cubase does not perform an automatic ā€˜snap to defaultā€™, that would be uncomfortable when turning the Rotate Knob.

For this update (July 15, 2025) this zip-file is published here, which contains only the file PreSonus_FaderPort.js:
fp-wizard_20250715.zip (105.0 KB)

If you are installing fp-wizard for the first time, please download the latest complete version, which can be found here:
PreSonus FaderPort 2 (2018) midi remote script - Cubase - Steinberg Forums
Then you can update the file PreSonus_FaderPort.js to the version of July 15, 2025.

Best regards
CKB (Christian) :innocent:

4 Likes
953

Hello m.c.

Thanks - Thatā€™s a great hint !

Deactivating the scripts like LluisV mentioned sadly didnā€™t help to get Cubase more responsive after loading a project in my case (nonetheless Thank You for your reply !) - it nearly took 8-10 sec for the FaderPort to react.
(makes me wonder what the use of deactivating these scripts actually is, if whereā€™s
no performance gain with it ?)

I created a backup of the factory remote scripts, deleted those -
now I am at around 2 seconds on start up - way way betterā€¦
Before I was wondering if the scripts I use (only 3 in total) would cause this delay, but No !

Also Thanks to butterfly to brought up this topic !

Kind Regards,
Frank

2 Likes
954

Thanks Christian,

seems I donā€™t have a need for some calibration (I just have very minimal differences in values),
but thatā€™s usefull information and I saved your instruction, if I ever need it in the future.

Thanks,
Frank

1 Like
955

Youā€™re restless, arenā€™t you ? :laughing:

Good for all to usā€¦

Thank You,
Frank

1 Like
956

Hi , just some updates after re-calibration process done.

My physical fader stays a bit above of " U" mark on the controller, but on Cubase it shows 0 Db.
It used to be like that even before calibration process. Should it be that way or i am missing something ?

  1. Another question regarding controlling automation.
    When track is selected and its automation with W/R enabled with any plugin parameter , the physical fader is not reacting on anything ( only main Volume automation supported but not Steinberg Volume Plugin) What mode should I enable on the faderport for inserts and sends automation reaction of the fader ?

Thanks in advance !!!

957

Hi Ivan,

My physical fader stays a bit above of " U" mark on the controller, but on Cubase it shows 0 Db.
It used to be like that even before calibration process. Should it be that way or i am missing something ?

Fader labels on controllers are often stretched slightly differently. Therefore, they often do not fit perfectly with every software. This is why the ā€œUā€ does not correspond exactly to 0 dB. This can also occur with other controllers. Some controllers (e.g. ā€œConsole 1 Fader Mk IIIā€ from Softube) even have NO labeling for this reason.

When track is selected and its automation with W/R enabled with any plugin parameter , the physical fader is not reacting on anything ( only main Volume automation supported but not Steinberg Volume Plugin) What mode should I enable on the faderport for inserts and sends automation reaction of the fader ?

You can compare fader automation with the autopilot in an airplane. You have to switch off the autopilot to be able to control the plane yourself. Only small corrections during the flight are possible. This means:
(a) In Stop Mode with automation = W/R, you cannot move the fader if automation data already exists. The fader position is determined by Cubase according to the automation data.
(b) In Play/Rec Mode with automation = W/R, you can move (= correct) the fader, but you must observe any existing automation.

Best regards
CKB (Christian ) :innocent:

2 Likes
958

Thanks Christian, i just refine my problem, i would like faderport react on my other plugins automation ( apart main gain volume , which works) but opening another instance of automation lane for my Valhalla , faderport gives no reaction whether its in Stop mode or record mode . I can neither physically with fader record automation for Valhalla no see the movement of the fader after automation made with mouse. Both Stop mode / record mode.

1 Like
959

Hi Ivan, unfortunately, I canā€™t help you with this because I donā€™t use any plugins from Valhalla.

960

My point was any other plugin or which one you use .

I am asking is it generally possible to have physical feedback for other plugin automation parameters or only one parameter Volume?

( For now i found the solution for the input parameter, its Faderport Shift+Section and hoover mouse over.) Which is written in your manual.
When i playback the written automation fader does not move. Only if i hoover mouse over parameter . If its like that its ok with me.

2 Likes
961

Ok, now Iā€™ve understood you correctly, Ivan.

Yes, it works, I tried this:

  1. I tried it with the plugin ā€˜Pianoteqā€™ on an instrument track.
  2. In the Pianoteq plugin, I used the ā€˜QCā€™ button to display the Quick Controls.
  3. In fp-wizard I selected the Motorfader Mode ā€˜+QC1ā€™.
  4. Now I was able to record automation with the Motorfader.
  5. After recording the automation, I set the projectcursor to the beginning of the recording.
  6. In fp-wizard I have now activated the Zoom Mode (not the AI Mode!) on the Shift Page.
  7. In the Zoom Mode, the motorfader has the function ā€˜value under mouseā€™ with ACTIVE motor. The AI Mode is for using the knob as ā€˜value under mouseā€™ so the motor is switched off in the AI Mode.
  8. In the plugin Pianteq I now set the mouse to the parameter that I had recorded as automation.
  9. Now I pressed the Play Button on the FaderPort.
  10. During playback the motorfader moves automatically, according to the parameter from the plugin.
2 Likes
962

Thanks !

1 Like
963

I had this issue, the fader do no sits at 0dB when de track volume selected is at 0dB.

The solution was to set the max fader level the same value in cubase and in the script. The options are 6 or 12 dB.

The default value for the script is 6dB.
But Cubase could be at 12 or 6.
This misaligns the father.

Regards,
LluĆ­s

2 Likes
964

I reask, just to be clear , in the Faderport Script ( FP wizard script) i have to change from 6 db to 12 ?

1 Like
965

Yes, this is explained directly in the code of the script from line 51 :

// If 'Volume Max' in 'Other Project Settings' of Cubase           // CKB
// is set to +6 dB                                                 // CKB
// the code below should be: const CRLevel_Value_0dB = 0.78909     // CKB
//                                                                 // CKB
// else if 'Volume Max' is set to +12 dB                           // CKB
// the code below should be: const CRLevel_Value_0dB = 0.74828     // CKB
//                                                                 // CKB
const CRLevel_Value_0dB = 0.78909

If you are working with +12 dB, you must adjust this in the script.

Nevertheless, the fader on the FaderPort is not exactly at position ā€œUā€ when the fader in Cubase is set to 0 dB, even if you have set this setting [+6/+12 db] in the script as in the project.
But there is hopeā€¦ I am currently testing a possible solution for this, which seems to work. :wink:

2 Likes
966

That sounds good, CKB. :blush:
I donā€™t mind this little detail, but when everything is perfect, producing is of course even more fun.

1 Like
967

Hi Christian,

a have a question in regards to the shift page -

usually, if you switch from the main page to the shift page the last used mode in the shift page is recalled -

but (in my case) not the EQ-Mode !?

To make it (hopefully) totally clear:

if I used the EQ-Mode on the shift page, when going back to the main page, when again
going to the shift page - the EQ-Mode is not selected, but instead the mode on the shift page, which has been used prior to the EQ-Mode.

Is there a reason for this behaviour or is this a bug ?

Kind Regards,
Frank