My alternative device to the CC121 after the production has ceased

Hi CKB,

I discovered two very interesting new features in your list above: :grinning_face:

  • use knob for Quick Control with low / high resolution

  • use knob for value under mouse with low / high resolution

If you have a moment to reply (I assume you are working on the update)…

Will the “high resolution” be added to your script or the “low resolution”?

Both will be new, for the QC Mode and the AI Mode.:slightly_smiling_face:

You’re probably also curious to know how it will be operated,
so here is a small excerpt from the as-yet-unpublished release notes for the next update, which is not quite finished yet:

Note:
The new update of fp-wizard (Version from September 30, 2025 )
was published here in the Steinberg Forum.
[ topic: PreSonus FaderPort 2 (2018) midi remote script ]

Great. The new version works perfectly! :grinning_face:

CC121: Hey owner, could I get my old job back?

Me: err, sorry mate, maybe you could just sit there looking pretty and hold these headphones for me for a bit?

Note:
A new update of fp-wizard (Version from December 2, 2025 )
was published here in the Steinberg Forum.
[ topic: PreSonus FaderPort 2 (2018) midi remote script ]

Interesting photo, AlanP, because it clearly shows that the compact size of the FaderPort is very useful and that you can even place the device on a keyboard. I think saving space is an important aspect of increasing creativity in production.

Yes, I have used the CC121s PSU (which has a long cable) and a longish USB cable, and I move my Faderport between Desk, keyboard etc. as needed. I agree, Butterfly, that the slim form factor is a winner. I am thinking of selling my CC121 if anyone wants one..

Hi,

Sorry if I sound disconnected to the thread but is it possible to use the script and assign the fader from faderport to cc1 or cc 11? Thanks.

Hi laurent,

yes, that’s possible.
There are four different Fader Modes to choose from in the script.

One Fader Mode is the ‘direct’ Mode.
When this Fader Mode is active, the data is transferred ‘clean’ from the FaderPort to Cubase, where it can be converted using Cubase’s ‘Input Transformer’. The data arrives in Cubase as ‘MIDI Pitch Bend’ - this cannot be changed. But it’s possible to setup Cubase’s ‘Input Transformer’ so that ‘MIDI CCx’ data is generated in realtime from the ‘MIDI Pitch Bend’ data within Cubase.

However, if the Fader Mode within the script is set to ‘direct’, the motorfader cannot be used for the many functions offered by the script. For this reason, the Fader Mode ‘direct’ should only be used in exceptional cases.

In most cases, the desired use cases can be realized using Quick Controls instead of the Fader Mode ‘direct’, which can be controlled very easy and conveniently with the script, i.e. for to control a filter of a VST instrument or something similar.

Best regards
CKB

Great! Thank you for the explanation

Finally here

Okay, but the new cc1 doesn’t look elegant.

At first glance, it’s a mutation of an Elgato Stream Deck + but WITHOUT an extra display, instead with 12 buttons and some basic features from the old cc121.

What I see, however, is that the very important transport buttons REWIND and FORWARD are missing.

Negative opinions about the Yamaha CC1 in another thread…

Based on what I’ve read about the Yamaha CC1 in the thread above, the FaderPort together with fp-wizard might be the best choice after all. It only costs half the price, so you can buy a Stream Deck separately if you need it. Nevertheless, I believe that there is also a target group of users for the CC1.

For me, the FaderPort is still the best choice.

:grinning_face_with_smiling_eyes:

CC1 looks a good bit wider and longer than the FP too, which does matter.

CC1 definitely looks longer - but looks narrower to me.

The technical specifications indicate that the CC1 is quite heavy. This would be impractical if I need to move the CC1 around my home studio. My FaderPort is much more flexible in this regard.

CKB, is your current iteration of the Presonus Faderport 2 script still compatible with the PreSonus ioStation 24c?

I would like to use the Mic preamps in the 24C but need the function of the Faderport 2.

@Featherlightstudio

I have a ioStation 24c working with Nuendo 14 on Windows and Mac.

I’ve done some small tweaks.

Edit the script and change this:

deviceDriver.makeDetectionUnit().detectPortPair(midiInput, midiOutput)
.expectInputNameEquals(‘PreSonus FP2’)
.expectOutputNameEquals(‘PreSonus FP2’)

By this:

deviceDriver.makeDetectionUnit().detectPortPair(midiInput, midiOutput)
.expectInputNameEquals(‘ioStation 24c MIDI In’)
.expectOutputNameEquals(‘ioStation 24c MIDI Out’)

And change the folder name and the script name:

Folder name: ioStation 24c

File name: PreSonus_ioStation 24c.js

Regards,

Lluís

Edit:

I change FaderPort by ioStation 24c in this line:

var deviceDriver = midiremote_api.makeDeviceDriver(‘PreSonus’, ‘FaderPort’,
‘2025/12/02 oe@totalcall.de, wem-music.de’)

Hi @AlanP

I see that you and other people sometimes change the location of the FaderPort while producing. In the next major update of fp-wizard, there will be a new feature that provides support for such situations. I call it smart footswitch control. There has never been anything quite like this in the world of controllers. :smiley:
Here’s an excerpt from the (not yet published) next release notes…

At the moment, I am still working on the documentation for the next update and this is going to take me a little longer than I thought…

Best regards,
Christian :innocent: