osmizza001
Pan button doesn’t light up with latest script on my PC (win 10 latest, Cubase Pro 12.0.70)
Already tried Cubase uninstall-reinstall but no luck
Hi Carlo & other Windows-Users with problems…
? Have you installed the latest UNIVERSAL CONTROL Software from PreSonus, Version 4.1.0.93124
and (with this) set up the Firmware of the FaderPort to v3.74 ?
After that, you have to set up the FaderPort again to the Studio One Mode like this:
To select the Studio One Mode, switch off the FaderPort (= power off), press and hold the Next button while powering on the FaderPort, wait for the FaderPort’s lights to illuminate, release the Next button and then press the Solo button.
Don’t define the FaderPort as a MCU/HUI-Device in Cubase, only copy the File PreSonus_FaderPort.js to the special folder like this:
C:\Users\YOUR USERNAME\Documents\Steinberg\Cubase\MIDI Remote
\Driver Scripts\Local\PreSonus\FaderPort\PreSonus_FaderPort.js
(The path depends on the language of your system.)
Something more, that could help:
Delete all program settings of Cubase per starting Cubase with Ctrl-Alt-Shift to delete all Cubase Preferences.
Delete as far as possible the content of this hidden system folder (not the folder itself):
c:\Users\YOUR USERNAME\AppData\Local\Temp
(The path depends on the language of your system.)
Always turn on the FaderPort only after the PC is completely booted. Start Cubase (Version 12.0.70 must be installed) after that.
Always turn off (= power off) the FaderPort before you shut down your system.
Some FaderPorts that are in circulation are said to have hardware problems. In this case the coding of the colors of some LEDs does not work. If this should be the case, in the latest script (13.09.2023) in line 54 the code of the file PreSonus_FaderPort.js must be changed to:
var disable_color_settings = true
However, it is also possible that this problem was fixed with the firmware update v3.74.
If all this still doesn’t help, another question would be whether it works when there are no other midi devices connected to Cubase besides the FaderPort for to find the reason for the problem.
Best regards
CKB