Hi all, here comes a new update of the script.
after the implementation of the EQ mode, the adjustment possibilities of the click level, set pan to center and set CR master volume to 0 dB, I have now implemented a Custom Mode, in which you can assign up to 18 Cubase Functions individually to the FaderPort.
By pressing the Channel Button 2x on the Main Page you activate the Custom Mode.
While the Custom Mode is active, the Shift LED is flashing and the LED of the Next Button and the LED of the Prev Button light up, so that you can clearly see that you are in the Custom Mode.
You can leave the Custom Mode by pressing the Shift Button; after that you will be in the Pan Mode back on the Main Page.
While the Custom Mode is active, the functionalities of the Transport Section and the Footswitch Section are available and the motorized fader is assigned as to modify the value under mouse.
The following 18 Buttons are availabe for to assign to a Cubase Function:
- Solo
- Mute
- Arm
- Bypass
- Touch
- Write
- Read
- Prev (>> preloaded: Undo)
- Press Knob
- Next (>> preloaded: Redo)
- Link
- Pan
- Channel (>> preloaded: Exit to Main Page)
- Scroll
- Master
- Click (>> preloaded: Quantize Panel)
- Section
- Marker
The rotate functionality of the knob is not available in the Custom Mode, so if you need it, you have to use the activate knob for value under mouse function on the Shift Page.
For to assign Custom Buttons of the FaderPort to Cubase Functions, you must use the MIDI Remote Mapping Assistant of Cubase and there choose PreSonus FP2 CUSTOM as the Mapping Page. The mapping there works by selecting the FaderPort Button and choosing a Cubase Function from the Functions Browser. If you do this, it would be good, if you limit yourself to the functions under Key Command Mapping.
Note: For the assigned Custom Buttons, the LEDs on the FaderPort remain off. And please use only the FaderPort for to switch between the Mapping Pages of the script and do it not in Cubase when your normal workflow is going on. This is important, because the script only works properly if the Mapping Pages are called in a certain order.
This update also fixes a few bugs within the new double-click functions (in Pan Mode and CR Volume Mode).
Also there is something else that Lluís had already pointed out today:
If Volume Max in the Other Project Settings of Cubase is set to +12 dB (not +6 dB) you must change a value of a variable manually in the script.
For that you have to open the file PreSonus_FaderPort.js with an editor (like Editor in Windows) and change the code at line 48 from
var CRLevel_Value_0dB = 0.78908658
to
var CRLevel_Value_0dB = 0.74828
for to adjust the handling of the rotation knob with the Volume Max setting.
Addendum (2nd update) - 28.08.2023
I also fixed some bugs in the lock current value functionality.
Note: The lock function also remembers for which track the value was locked. So if a track-specific value is locked and then the track is changed, it may be that later when calling the function activate knob for value under mouse again you have the impression that there is an error, when the still locked (hidden) value belongs to a different track as shown.
Note: A locked value under mouse will be unlocked, if you choosed a custom function before activcating the knob for value under mouse again.
I added also another function:
toggle lock current value under mouse with button, so you can now decide for yourself whether you want to perform the lock function by pressing the rotate knob or by pressing the Channel button.
Addendum (3rd update) - 30.08.2023
Last but not least, I was able to implement a functionality that I had wished for from the very beginning, namely the possibility to toggle with Shift + Arm whether the recording status for all audio tracks is armed or unarmed. This sounds simple, but Cubase offers only two different command functions for this and no toggle function. In the meantime, however, I have made some more progress with the programming of MIDI Remote, so that it was possible for me to combine these two commands as a toggle function on one button.
Shift + Arm is therefore now assigned as follows:
toggle arm all / unarm all audio tracks
Addendum (4th update) - 31.08.2023
I have now assigned some few functions to the Custom Mode as defaults. To the Prev button I have now assigned the Undo function, to the Next button the Redo function (this is also how the FaderPort is labeled), to the Click button the Quantize Panel and to the Channel button a second way back to the Main Page. So if you don’t want to deal with Cubase’s MIDI Remote Mapping Assistant yet, you already get a few extra functions with this defaults.
I also have (two) new functions to improve the workflow for you: For me and I think for you too, it is often the case when working, that you are switching between zoom and scroll. For this I found it suitable, that if you press 2x the Scroll button, you jump to the Zoom Mode and accordingly if you press 2x the Zoom button, you jump to the Scroll Mode, because Scroll and Zoom are a bit like brother and sister, where pressing the Shift button in between is a bit annoying. I call this function toggle zoom / scroll. I like it, because with this you can move between the Main Page and the Shift Page just with the buttons of the Middle Section. Otherwise the Shift button would be the first to break in 20 years… 
Addendum (5th update) - 04.09.2023
Some other bugs were fixed within the new double-click functions.
I hope you like all this… 
The zip-file contains the new version of the script (4007 lines) and the new version of the functional overview.
Best regards
CKB
[ No file here in this reply, because there is a newer version available in the forum. ]
