yes, you do this with the record button, but to get out of this loop, you need another button, the stop button. but you only have ONE footswitch, so the re-record case is not manageable with the footswitch alone. after pressing the footswitch to start the recording, the footswitch turns into a stop button. That’s just logic; of course, you can’t change that with the script.
You’re right,
but after a successfull recording (via re-record) I’d be OK to use the stop button as the job is done and I don’t need my hands on the guitar anymore - I do not need the footswitch for this.
Anyway, I’d be interested in Christian’s thoughts about this topic.
I hope you realize that I’m not here to criticize his work - in fact I think he does an amazing job here - this script together with the Faderport exceeds my expectations from a DAW controller anyway.
I just try to give some thoughts/ideas/input - if usefull or not - well, this is up to Christian.
Cheers,
Frank
I have several acoustic instruments here. I play some of them reasonably well, others not so well. Actually, I’m primarily a pianist.
I tested the footswitch for months before making the final decision on its new technical implementation.
I tried playing keyboard, grand acoustic piano, guitar, drums, and saxophone while using the footswitch.
Of course, I’m familiar with Cubase’s Re-Record Mode, which lets you restart recording from a specific point with just one click.
When I’m sitting at my desk with my guitar and can still just reach the FaderPort with my right hand, the Re-Record Mode can be useful. But from the drum kit, however, I first have to get up and walk over to the desk to operate the FaderPort. And when I play the saxophone, I regularly need a break in between to catch my breath, and I want to have my peace and quiet right away. As a result, I came to the conclusion that the Re-Record Mode with its immediate restart is unsuitable in far too many cases. I don’t care if someone else expects the Re-Record Mode to work with the footswitch. What’s more important is that all use cases can be handled with the footswitch, something other than a button.
So the basic rule was, that it must always be possible to stop the process using the footswitch. This is also important in case you only want to make a small correction and absolutely must not overwrite anything beyond that point. Of course, you could configure safety mechanisms beforehand to prevent this, but in practice, many people don’t do that - at least, I don’t.
I then simulated all (for me) possible use cases and concluded that ‘continue from the current point’, ‘return to last start’ and ‘return to left locator’ were the optimal set of transport functions for the footswitc for both, Play Stlye and Record Style.
I had already thought before, that I could do even more with the footswitch if I took into account how long I held it down.
At first, I tried a lot of different press-down times, but in the end I came to the conclusion that only these are practically feasible: short, 1 second, or 3 seconds. With any other times, I made too many mistakes and had to concentrate too hard.
In practice, the use cases have broken down roughly as follows:
(a) continue recording = 25%
(b) resume recording from ‘last start’ = 50%
(c) resume recording from ‘left locator’ = 25%
After that, the further specification was determined. In that process, I had to realize that too much flexibility in operating the footswitch led to more misoperations. This is how the final concept, as it is now, came about. I will not change it anymore either.
I intentionally did not implement an option that would allow the required 1-second press for case (b) to be removed. I tried that, but it caused some confusion. But you can do that anyway by ‘activating’ the transport setting ‘return to Start Position on Stop’ in Cubase in the menu item Transport > Start Mode. I had indeed always strictly prescribed setting this option to ‘deactivated’, but in this case, as an exception, NOT, if in the above case (b) one footswitch press less is desired. I don’t do that myself. I prefer the ‘long version’. As a result, I master all 100% of the use cases for the footswitch better without any confusion. Sorry, that might sound a little ‘undemocratic’, but since I work (= main job) as a software product designer, I’m used to deciding things the way I think is best.
Best regards,
CKB 
Thanks Christian for sharing your thoughts about the footswitch functionality !
Appreciate it !
Cheers,
Frank
I want to say a big thank you for all the work invested here.
I just got a defective Faderport for 40€ and was able to repair it and now with your script I have a great working unit with Cubase.
All the best
Christian
Hi there,
if I may ask - just out of interest - what was defective and how did you repair it ?
( no need for an excessive answer - just keep it short if you like)
Thanks and else… enjoy your Faderport !
Cheers,
Frank
Hi,
It was the USB jack, that was broken.
I first desoldered the rest of the pins and then soldered a USB cable directly to the pads.
First the faderport was not recognized by my Mac. I measured some really strange voltages also. But on a Windows computer it appeared in the device list.
After that it also worked on my Mac.
Then I recalibrated the fader. That was easy thanks to the great description in the setup files.
I love the workflow now.
I have a Softube Console 1 MK3 Channel and the faderport. I can select the track on the console with my left hand and keep my right hand on the fader.
Cheers
Christian
That sounds good.
Another option I find very interesting is combining the FaderPort with the new
Elgato Stream Deck+ XL
In any case, this combination with the FaderPort is far superior, more versatile, and more powerful than Yamaha’s CC1.
I also think two separate devices are much better, since you can then operate the Stream Deck with your left hand while your right hand is on the keyboard or on the FaderPort.
I haven’t bought the Elgato Stream Deck+ XL yet, because I’m waiting to see what other buyers have to say about it first.
Hi butterfly,
I will keep it short because I don’t want this to go much off-topic.
I got an Elgato Stream Deck+ besides the FaderPort since 2-3 years - no problems with the hardware so far - the encoders have a little mechanical slack (same as the FP2 encoder), but no issues so far in regards to function.
The biggest advantage of the XL version imho is the amount of buttons on one page -
the strip to switch between profiles is great, but still - today I’d buy the XL version just for the amount of instantly available buttons.
In regards to the Streamdeck software - it’s constantly updated/new functions added
Of course you could also create profiles for other applications beside Cubase.
For Cubase you might look up for a company called SideshowFX, if you do want more functionality, especially if you’d like to use MIDI controllers and get the most out of the dials. (You might download the manual for the XL version to have a look). Or you could also check https://trevligaspel.se/streamdeck/midi/index.php instead. (I’m not involved anyhow with these companies - I just bought and use their software).
But be warned - once you start to modify existing profiles to your liking or start to create your own ones - it can get quickly addictive 
That’s all I want to say in this topic - if you have any more questions - sent a personal message.
Kind Regards,
Frank
hi I just installed my FP2.
Is there a way to use the PREV/NEXT buttons like the arrow keys on my keyboard? I did not find a function yet to just jump to the next/previous mixer channel :-/
Hi @HorNet505,
if you have installed the fp-wizard script correctly, the Prev and Next buttons do exactly that = switch to the previous or next mixer channel.
Maybe you overlooked something when installing the script. You could take a look in the setup file from CKB. There are lots of hints about what could be causing it, when the script doesn’t work. Here’s the link to the latest version of fp-wizard…
Hi HorNet505,
you have to enable this setting (I write it in german, so that you could find it easier in your german Cubase version):
Programmeinstellungen > Bearbeitungsoptionen > Projekt und MixConsole > Auswahl in Projekt-Fenster und MixConsole synchronisieren
Notes:
Prev / Next for “prev track” / “next track” does not work in every Mode - you have to look to the functional overview pdf.
By holding the Cycle Button and turning the knob, you can move faster through the tracks.
Hi Christian,
A big thank you from Ukraine for your elegant and amazingly useful script! It makes working so much easier and more convenient.
I noticed an issue after updating from the August 2025 version to the May 2026 release. In Touch automation mode, writing doesn’t stop immediately when I release the fader—there’s about a half-second delay. Because of this, unwanted spikes end up forming in the automation line.
This didn’t happen in last year’s version—I double-checked by reverting back to the older build. Is there a way to configure or fix this?
DAW: Nuendo 15.0.30
P.S. “Send to Fader” mode is incredible! Extremely convenient!
Thanks for pointing that out.
Actually, I had already fixed this behavior, which first appeared in the released ‘30 September 2025’ version, earlier. Of course, the automation should stop immediately when the fader is released.
Now I’ve noticed that, for some reason, the fix just isn’t included in the released ‘31 May 2026’ version. But (contrary to that) everything is fine here. I have no idea how that could have happened.
You’ll therefore receive an update of fp-wizard soon, where the automation recording stops immediately when you release the fader, without any delay.
Best regards
Christian
hey Christian, thanks for the tip.
I checke the REMOTE MIDI API and I think it I am looking for a “MixerBank…Action”.
I will dig into it. I do not sync the mixer with the project since I use multiple view-filters in the mixer and need to navigate oleft/right only on what I see.
What I also noticed is, that in the current script I can browse through the tracks [PREV/NEXT] but the fader does not work on those tracks (in the left area of the project)
Since I only mix in the mixer window I think I will reconfigure it to use the “right” “left” function that is already bound to the arrow-keys of the keyboard.
update:
This works for my Mixer navigation:
// old
pageMain.makeActionBinding(mSection.var_Prev, pageMain.mHostAccess.mTrackSelection.mAction.mPrevTrack).setSubPage(SubPage_Pan) pageMain.makeActionBinding(mSection.var_Next, pageMain.mHostAccess.mTrackSelection.mAction.mNextTrack).setSubPage(SubPage_Pan)
// new
pageMain.makeCommandBinding(mSection.var_Prev, ‘Navigate’, ‘Left’).setSubPage(SubPage_Pan) pageMain.makeCommandBinding(mSection.var_Next, ‘Navigate’, ‘Right’).setSubPage(SubPage_Pan)
I wonder if I can make it dependent on an active mixer window only, thus keeping your navigation in the project windows intact.
Hi HorNet505,
alternatively, without changing anything in the code of the script, you could configure the Prev Button and the Next Button on the Custom A0 Mapping Page of the script with the ‘MIDI Remote Mapping Assistant’ (= ‘MIDI Remote Zuweisungsassistent’).
There, you assign the Buttons to
Keyboard Commands > Navigate > Left / Right
(= Tastaturbefehle > Bewegen > Links / Rechts).
The fp-wizard release notes contain important instructions on how to use and configure Custom Mode of fp-wizard.
However, this alternative has the drawback that it only works as long as you are on the Custom A0 Mapping Page - but maybe this is acceptable for you.
Your alternative only works as long as the Mixer Zone has the focus and may have other negative side effects as well.
Otherwise, there is the alternative of changing the global Undo and Redo functions in the code of the script to Navigate Left / Right. The Undo and Redo functions are linked to the key combinations Cycle+Prev and Cycle+Next.