Well explained, CKB. Impressive how you focus on developing the script primarily close to real practice. You did a great job again with the new Audio Mode. Also your selection of the 12 functions within, the order of the buttons and how you chose the LED colors. When I look at these LED colors, I intuitively find the right function immediately.
Thank you very much! 
1 Like
Thank you CBK!
2 Likes
Hi LluĂs,
in addition to the changes in the script when using an ioStation 24c instead of a FaderPort,
have you tried whether it helps if you also rename the filename of the script and the folder?
instead of
.../PreSonus/FaderPort/PreSonus_FaderPort.js
this (with blank)
.../PreSonus/ioStation 24c/PreSonus_ioStation 24c.js
or this (without blank)
.../PreSonus/ioStation24c/PreSonus_ioStation24c.js
Best regards
Christian
1 Like
@CKB
I have tried the options you suggested and added the underline option
âŚ/PreSonus/ioStation_24c/PreSonus_ioStation_24c.js
I have also changed this line of code:
var deviceDriver = midiremote_api.makeDeviceDriver(âPreSonusâ, âioStation 24câ, âoe@totalcall.de & WEM-Music.deâ)
With blank, without blank and with underline
I have not noticed any change, in all cases if I open the project without exiting Nuendo the script does not initialize correctly because the âpanâ button remains activated when the âmasterâ should be activated. But I can activate it manually and all the functionalities work fine.
I have the option enabled:
const start_with_Master_Mode = true
I tried opening and closing 30 projects (without leaving Nuendo) and the script worked fine although without fully initializing, the âmasterâ button is never activated automatically.
I couldnât do this with version 13.0.40.
Since version 13.0.40 I have the habit of always leaving Nuendo to change projects. But it seems that with 13.0.55 and 14.0.30 I can open projects without leaving Nuendo, I hadnât tried it.
With version 13.0.40 and earlier, if I opened and closed projects without leaving Nuendo, the script stopped working completely. Only the transport buttons worked.
I had to leave Nuendo and reopen the project for it to work again.
Can you test that with the faderport, and with the option Master_Mode = true, the Master button is always activated when you open a project without closing Nuendo?
Thanks for your invaluable help.
LluĂs
1 Like
Hi LluĂs,
thank you for trying so much.
Yes, I was now been able to reproduce that the Master Mode was not automatically activated when going to another project (if the option for this was set in the script). This may depend on the Cubase/Nuendo version. It used to work with an older version of Cubase/Nuendo, if I remember correctly.
It looks like Cubase/Nuendo reloads the script when changing projects, but does not initialize everything. Reloading means that the driver is shut down once and then started up again. The initializations should actually take place during this startup, but unfortunately Cubase/Nuendo does not do this, or sometimes not or apparently not completely. I have now implemented that various initializations take place during shutdown, but I am not sure whether this is sufficient and whether it has any undesirable side effects. So here is this (preliminary) version for testing:
[ the file originally posted here has been deleted, as it can now be found under this link: ]
PreSonus FaderPort 2 (2018) midi remote script - Cubase - Steinberg Forums
Best regards
Christian
3 Likes
Hi Christian,
Well done!!!
Now I was able to open 5 projects at once and switch from one to another without any problems with the ioStation.
It always start with âmasterâ button set and all the features I usually use still work.
Many thanks for your work,
LluĂs
2 Likes
new update available - June 6, 2025
Dear friends,
because of the hints from LluĂs I have added some initializations to the shutdown of the script. It seems that there are now no problems when switching to another project during a Cubase/Nuendo session.
The test version of this has now become the current official version of fp-wizard.
So I have replaced all files in the post with the last complete version. Therefore, all files in that post now have the date June 6, 2025.
PreSonus FaderPort 2 (2018) midi remote script - Cubase - Steinberg Forums
Best regards
CKB (Christian) 
5 Likes
PreSonus must either be really impressed by you, or hate you since youâve made this thing 100x more powerful in a competing platform.
2 Likes
I hope nobody hates me. I love my FaderPort and I hope he loves me too and that he always does what I want because of that. 
2 Likes
Presonus must be happy with @CKBâs work. Some people have bought Faderport thanks to this script.
Presonus must give money to @CKB.
3 Likes
most definitely (-:
2 Likes
So many nice commentsâŚ
Many thanks!
2 Likes
Iâve done a new hard test.
I opened Nuendo and a project with faderport unplugged.
I powered the faderport, after a few secods, Nuendo recognized it and everything was working fine.
I have turned the device off and on, with Nuendo running, and have not found a way to make it fail.
I think now the script and the midi remote works perfect.
Well done @CKB and Steinberg
LluĂs
3 Likes
Hi Christian,
I currently came to think, if it is possible anyhow to assign a key command in the Custom Mode,
which does not relate to a Cubase function, but instead would trigger an application besides Cubase ?
Guess itâs a dumb question and for sure not possible ⌠!?
(If so - I hope you donât mindâŚ)
Best regards,
Frank
1 Like
Hi Frank,
It should actually be possible, but in my opinion only with additional software that is designed precisely for this case. There is such a thing (but I donât know anything about this software):
However, I have not yet had any experience of whether such software can be configured so that it works
- in parallel with MIDI Remote and
- only in those certain situations where you want to have the special key combinations on the FaderPort assigned for your desired application call.
Of course, it would take some time to try out what works. Maybe you could give it a tryâŚ
Best regards
CKB
1 Like
Thanks Christian for the answer,
I really donât want just another software runing besides, so Iâll be using my StreamDeck for this right now.
But I might check the program you mentioned anyhow as Iâm always curiousâŚ
Thanks and Kind Regards,
Frank
1 Like
Hello @CKB
I often like to use your special memory function in EQ Mode, with which you can save or reload all EQ settings at once with the write / read buttons or with the write / read combinations together with link, pan, channel, scroll. Recently I used this in a vocal track with automation and switched the voice to âtelephoneâ and back again. Very cool!
Now I would like the script not to delete these special memory data when changing the project. Is that possible? In my case I would like to create a small test project in parallel to a big project, where I try things out and in it I need EQ settings from the big project. It would be very cool to do that with your special memory function.
So I mean I would like this special memory to be retained for as long as Cubase is running.
br - butterfly 
1 Like
Hi butterfly,
your suggestion makes a lot of sense.
Yes, I can implement that.
Maybe Iâll be able to do it at the weekend and then publish an update of the script here.
Best regards
CKB
2 Likes
Thank you very much, CKB.
Itâs great that youâre in the process of improving even small things in a short space of time. 
1 Like
Sometimes it makes sense to do this immediately.
For example, I have noticed that in some cases there is a small amount of unnecessary MIDI traffic and LED flickering when switching projects. I am currently improving the script so that a project change runs more smoothly - i.e. without this unnecessary MIDI traffic.
This will also be added to the upcoming update this weekend. 
2 Likes