Thank you!
Maybe I still donāt understand how it works, but in SHIFT mode with Cyan color on Touch button the fader doesnāt send the Pitch bend messages. All other colors of Touch do nothing as well. What can be wrong?
Hi vitaliistep,
as described in the new version of the file FaderPort_setup.pdf,
you must set the In āAll MIDI Inputsā setting for the FaderPort to enable,
if you want to work with the Motorfader Mode direct.
You can find this setting in Cubase here:
Studio > Studio Setup > Remote Devices > MIDI Port Setup > In āAll MIDI Inputsā
I hope this works for you.
CKB
1 Like
Hi CKB,
Thank you very much, you are right. It works now.
Several more questions:
- How can I donate to you for all the work?
- How can I set a specific level, like -12dB, for a specific color of the VU-meter?
- Is it possible to implement such functionality for Faderport 2018 in Pro Tools or Reaper? Or itās only possible in Cubase?
- It seems that the new extended feature of Pan mode on the Main page doesnāt work or Iām again missing something
Thanks,
Vitalii
2 Likes
Amazing ! thanks so much.
1 Like
- Thanks, vitaliistep, but you donāt need to.
- You can edit the script file with an editor. That is something for advanced users. The comments there in the script explain how you can change the threshold values for the colors of the VU-Meter. The threshold values are determined in the script code by the constants
VUMeter_grey_blue_cyan_green_yellow_orange_red_magenta_clip and VUMeter_Scaling.
If you want to set a specific dB value for a specific color, you have to find out by yourself by ātrial and errorā which values you need to set in the code. This is because the range for each parameter is always between 0 and 1 when Cubase communicates with the FaderPort. - Sorry, the script only works with Cubase 12 + 13.
- Youāre right. I will upload an interim update here shortly to fix this. Thanks for the hint.
2 Likes
new interim update available - January 22, 2024
Hello friends,
the functionality in Pan Mode for switching between center and the last value before was broken in the update from January 14, 2024.
That problem is fixed in this update:
20240122_PreSonus_FaderPort.zip (52.2 KB)
(the zip-file contains only a new version of the file PreSonus_FaderPort.js)
Best regards
CKB (Christian) 
4 Likes
thank you so much.
I have seen videos of people using their motorized fader to control midi cc. Is this even possible in your opinion with the faderport?
This script allows for exactly that once set up. Instructions are included and very clear. This script has turned my relatively inexpensive FaderPort purchase into a something valued many times over itās original price.
Once properly set up, double-tapping Shift moves it into QuickControl mode and off you go.
Additionally, thereās a shift mode that allows the fader to control whatever is under the mouse.
1 Like
Hello, I am using the script with great success too
I also discovered the shift thing the other day itās great
but regarding quickcontrol mode, I have to set up the midi cc I want in the quick control of each track correct ? But I thought that in cubase 13, it doesnāt remember the custom QC assignement after reloading the template, am I wrong ?
Iām not sure about that issue with QC assignment. Iām not seeing that with my templates, but Iām also not seeing a lot of other problems expressed here. That said, it doesnāt sound like the issue is associated with this script specifically
1 Like
Hello friends,
here is some clarificationā¦
There are two externally ways to control Quick Controls in Cubase.
Take a look at this screenshot from the Studio Setup Dialog:
(Note: The terms Remote Device and MIDI Remote Device mean completely different things.)
First option: You can configure Track Quick Controls and VST Quick Controls for a āRemote Deviceā so that certain cc data sent by this device is interpreted by Cubase as certain Quick Control values. You have to set exactly which cc numbers are to be used. Some users are overwhelmed by this.
Second (new) option: MIDI Remote has been available as a new alternative since Cubase 12. This defines the device completely as a āMIDI Remote Deviceā. No cc numbers are assigned. The control-elements of the device are assigned to the Quick Controls without having to know what happens internally. Some hardware details are of course defined in the script. The script here is based on the Steinberg API (Application Programming Interface), in which the fader and the knob are defined as control-elements and in the script are assigned to the Quick Controls at certain points in the code, without a cc number being an issue.
This means that for example Cubase receives the command āchange Quick Control Xā from the script in āMIDI Remoteā and not a simple cc value for which Cubase then has to look up in a table what Cubase should do with it. So you donāt have to worry about cc numbers for the Quick Controls if you use them with the script.
But: There are also cases where you perhaps want to work with cc numbers in Cubase. Therefore I programmed the script of the FaderPort in a way that you can send cc data directly from the FaderPort to Cubase with the Motofader Mode direct, while all other functions are still executed in MIDI Remote Mode between Cubase and the FaderPort. In Motofader Mode direct, the fader sends PitchBend data to Cubase. This is done by the hardware. If this does not suit you, you must convert this data IN Cubase to other data, e.g. to other cc values. This can get complicated. So always try first whether your wishes can be solved directly with the Quick Controls, which are now available since the new update of the script.
What follows from this? If you are looking for new plugins, you should make sure that you have a good pre-selection for the assignment of the plugin parameters to the Cubase Quick Controls. This will save you work.
Best regards
CKB (Christian)
3 Likes
Here is a current photo of the rubber ring, I am using now, which turns the rotate knob also into a jog wheel. Iāve been working like this for a long time now and itās the best choice for me. There are several sellers on eBay who offer such a model.
You just have to make sure that the inner diameter of the ring is approx. 18 mm. The rotate knob has a diameter of 20 mm, which means, that the ring is stretched a little, when you put it on. This ensures, that the ring sits firmly on the rotate knob.
6 Likes
Hi Christian! I did (today) purchase a Faderport V2 and Iām right now trying to sort all the many functions. 
Thank you for all your hard work here and, more importantly, for sharing it with Cubase users! This is a very generous gift.
One question, my FPV2 has all the new drivers and firmware, yes, but the fader extends to maybe +3-4 ticks past Unity. I saw a previous poster talking about setting a Cubase setting to +12 as he was dealing with something volume related - but I cannot find the window he displayed, nor can I understand if his problem was my problem? Is it just that all the FPV2s are slightly out of adjustment?
1 Like
@mr.roos
You can set it in Project Seup dialog
1 Like
Hi mr.roos,
the āUā of the motorized fader is not perfectly in sync with the 0 dB of a fader in Cubase.
-
When a fader in Cubase is pulled down from the top to 0 dB,
the position on the motorized fader is different,
than when a fader in Cubase is pulled up to 0 dB from below. -
Projects with +6 dB max. volume differ from projects with +12 dB.
Projects with +6 dB are better adjusted. -
0 dB for midi tracks results in a different position than audio tracks.
This is not due to the script, this is also the case in the Cubase factory mode of PreSonus.
I donāt know whether this is also the case with Studio One as DAW.
MIDI Remote āconnectsā a Cubase fader to the motorized fader.
The value 0 is always at the bottom and the value 1 is always at the top.
The value for 0 dB is some value in between.
In order to adjust this value in between, a function would have to be constantly calculating, as values above 0 dB would have to be calibrated differently than values below 0 dB, and all this also bidirectional, different in the one direction than in the other.
However, as cases 1), 2) and 3) are all different, a perfect automatic calibration implementation is not possible.
But donāt worry, because this behavior is only annoying at the beginning, when you absolutely want everything to be perfect. If you work with the FaderPort for some time, you will see that you will read the exact dB values only from Cubase and the āUā of the FaderPort will no longer be of interest to you. The special thing about a one-fader controller is that you only have one fader, so you no longer have to make sure that you are moving the correct fader. Thatās why you no longer have to look at it.
Maybe the āUā means something else, e.g. āUh, touch meāā¦
1 Like
Ha, good explanation! My primary concern here was whether or not the FPV2 I purchased was operating correctly. So now I will ignore its physical position and instead focus on the Cubase mixer.
I also need to say that the various functions of your script are somewhat overwhelming coming from using just the keyboard! Have you thought about doing a YouTube video, maybe in an instructional format? I think you should consider this, Christian. I am quite certain that no users here are using your script with a FP as well as you are. I for one would watch it. For that matter, I would be happy to pay for it. Think about it? Happy New Year, btw, and thank you again for all your work here!!
1 Like
Since I found the script, the manual for the script is open while Iām working. It really is a beautiful piece of work.
2 Likes
Having spent the day with it now, I think I can sort the controls/features. I can report that EVERYTHING works exactly as the layout sheet describes. Which in itself is rather amazing! There is so much here! It seems the best plan is just to use the FP enough to commit the functions to memory. Iām on it.
1 Like
Thanks for the screen shot, but Iām going to stay with +6 db based on what Christian said.