PreSonus FaderPort 2 (2018) midi remote script

Cubase
,
290

Very grateful here. Thank you

2 Likes
291

Love it! Thank you

2 Likes
292

A new update is available

for the PreSonus UNIVERSAL CONTROL. The current version for it is
4 . 2 . 0 . 96206

1 Like
293

Hi all,
I have received a request if I am working on another update and if so, what will be the next enhancementsā€¦
Hereā€™s the answer to everyone: Yes, there will be another update.
I am working on extensions of the value under mouse Mode and the EQ Mode.
There you will have the possibility to manage multiple value under mouse values and multiple EQ sets in a simple way. For this I am creating a new functionality so called special memory. Actually, this is already running, but Iā€™m still testing it.

Best regards
CKB (Christian) :innocent:

2 Likes
294

Thank you so much for the heads up, Christian.

As an update, Iā€™ve upgraded to Cubase Pro 13 and the script seems to be working well on it.

3 Likes
295

Thank you, osanan for this information.
I havenā€™t installed Cubase 13 yet.

1 Like
296

Hi all,
Iā€™ll be testing the script with Cubase 13 soon.
The next update of the script with the new announced special memory functionality (= extension of the EQ Mode and the value under mouse Mode) will come afterwards.

Best regards
CKB (Christian) :innocent:

2 Likes
297

Hi all,
this is my result after testing Cubase 13:
Bad news for those who want to upgrade to Cubase 13 now.

If the script is started with Cubase 13, the coloring of the LEDs for the buttons Touch, Write, Read, Link, Pan, Channel and Scroll does not work correctly = for all buttons where it is possible to set the colors via RGB values.

Unfortunately, this cannot be solved now. The reason for the error must have been caused by Steinberg due to a faulty modification of MIDI Remote with Cubase 13. Again with Cubase 12 there are no such problems.

More precisely, the error appears here:
This function no longer works correctly after the update to Cubase 13 and it is very strange why not:

function setRGBLED(device, ledID, r, g, b) {
    midiOutput.sendMidi(device, [ 0x91, ledID, r])
    midiOutput.sendMidi(device, [ 0x92, ledID, g])
    midiOutput.sendMidi(device, [ 0x93, ledID, b])
}

I would therefore recommend not upgrading to Cubase 13 now.

Best regards
CKB (Christian)

298

Thanks Christian. Iā€™m seeing some other problems with C13, too, notably this one: NO rant , just facts Cubase 13 Audio engine Spikes compared to Cubase 12 - #64 by Highly-Controversial

So, Iā€™m holding off on C13 for a few reasons. Obviously, you are quite brilliant at code writing so Iā€™m very sure you will sort this unless of course Steinberg has declared war on PreSonus, maybe a possibility. Thanks, Christian!

299

CKB, just clarifying that the only thing not working is the LEDs? Everything else though is functional (including motorized fader)?

300

Apart from that, I havenā€™t noticed any problems so far. The fader also seems to do what it is supposed to do.

When controlling the LED colors, it looks like Cubase is ā€œbendingā€ the midi data for some reason. For some Modes relevant Buttons have no color now.
For me, however, this is reason enough not to use Cubase 13.
It is also very important that the colors work correctly for the next update.

301

Insert marker using the press button function in the marker window doesnā€™t work for me, but I think I have seen that that is a reported bug in Cubase 13. Insert marker doesnā€™t seem to work from remote controllers for some reason.

302

Hello my friend, just to be clear, what is the issue exactly? Is the sendMidi not working, or is the function setRGBLed not triggered? Here in my implementations, sendMidi works as expected.

303

Hi m.c,
I send certain values from Cubase to the FaderPort to display certain colors there. This works in Cubase 12.
What happens is a very simple sending of banal midi data.

With Cubase 13, other colors (or values that result in no color) arrive at the FaderPort. This means that Cubase 13 changes the values.

The code looks like this:

function setRGBLED(device, ledID, r, g, b) {
midiOutput.sendMidi(device, [ 0x91, ledID, r])
midiOutput.sendMidi(device, [ 0x92, ledID, g])
midiOutput.sendMidi(device, [ 0x93, ledID, b])
}

Example:
If I send the color ā€œroseā€ to the LED of the channel button, for example, the following values are sent:

RGB for ā€œroseā€ = 0xF0, 0x20, 0xF0
Address of the channel button = 0x36

therefore the following happens:

  1. midiOutput.sendMidi(device, [ 0x91, 0x36, 0xF0])
  2. midiOutput.sendMidi(device, [ 0x92, 0x36, 0x20])
  3. midiOutput.sendMidi(device, [ 0x93, 0x36, 0xF0])

This works with Cubase 12.
It no longer works with Cubase 13.

Other commands seem to work, namely:
midiOutput.sendMidi(device, [ 0x90, 0x36, 0xF7]) to turn on the LED above
midiOutput.sendMidi(device, [ 0x90, 0x36, 0x00]) to turn off the LED above

I therefore suspect that Cubase 13 changes the outgoing midi data especially for the cc values 0x91, 0x92 and 0x93 on its own and this probably has something to do with the new features of Cubase 13 or it is a bug from Steinberg. Since I am simply sending data, the error cannot be mine.

304

So, if you log inside the setRGBLED, you do see it triggered? And if yes, can you log the ledID and r,g,b?

Here youā€™re sending at midi channel 0, while in your other function, I do see the sends to channels 1 to 3. I wonder whether Cubase is filtering these noteOn messages to the other channels. Could you log using a midi monitor what (and if) it sends?

305

Which midi monitor do you use?

306

Iā€™m using Bome Midi Translator Pro, but I know there are others as well, so not sure which one to suggest.

307

Since my script programming had always worked, I never had to use a monitor for troubleshooting. So this is the first time Iā€™ve had to. But that doesnā€™t work now just quickly as desired.
I have tried the midi monitors MIDI-OX and Bome MIDI Translator (trial).
With that I am only able to test the midi output from the FaderPort without Cubase running. I am not able to check what Cubase is sending to the FaderPort.

But nowā€¦ I see, there is a special Monitor new in Cubase 13ā€¦

308

Instead of using the original midi ports of the faderPort, use the BMT ports of the Bome Midi Translator Pro instead, enable them inside the app, and see if it receives the messages.

309

With Cubase 13 I see something in the new Monitor there which I can export as a text file. It takes times now to analyse thatā€¦