Hey. Great work with this by the way, you guys have done a wonderful job by the looks of it. I haven’t got a FPv2, I just filed a return for my P1-Nano which I am very unhappy about, full refund inbound. So I’m looking at other options to fill my needs. This looks very promising.
I have one question: did Steinberg eventually add support for fader touch via Midi remote in the end? Or is that still not possible?
Cheers
Hi Indigo_Sam,
yes, Fader Touch is working from Cubase 13 onwards.
The fp-wizard script here automatically recognizes whether Cubase 13 is installed and if this is the case, the script activates the Fader Touch functionality.
Oh wow. That is perfect news!
I’m actually using Nuendo 13. Is this an issue for your script?
No, that’s not an issue.
The MIDI Remote API is identical in Cubase and Nuendo.
A few users here use the script with Nuendo.
Thank you, I’ve taken the plunge and ordered mine, should be here by the end of the week
It would be good if you read this file carefully at the beginning of your installation:
fp-wizard_setup.pdf
(So do not read the manufacturer’s instructions first.)
When you start working with the script, print out this file (one page):
fp-wizard_overview.pdf
Then I would intuitively try to understand how to use the FaderPort in general with the script.
Then you should definitely read through the various release notes, because they also contain detailed descriptions of how to use the script.
(At a later date I will summarize all of the release notes into a sorted, structured manual.)
Best Regards
CKB 
This was a useful hint. Thanks, CKB.
I have ordered my FP2; should arrive tomorrow. i will be sure to go through your documentation before I do anything. 
Thanks for being very helpful to us all. You rock!
Also please look at the Midighter Twister. It can do some amazing things. Knobs are endless encoders w dual features and LED feedback.
Hi CKB,
One question: does the script also support Faderport 8 (the one with 8 Sliders) on Cubase 13? Or should I expect problems with it? I just purchased a second hand Faderport 8 and I was thinking to use your script for it.
Thanks and regards
Rob
Sorry, Rob,
the script here only works with the FaderPort with one fader.
It would also not be possible to adapt the script to the FaderPort 8, because a single fader device must be implemented differently than a multi fader device.
Regards * CKB
Ok, thank you for this information. Nevetheless I find your work and support on this topic great!!!
Greetings Rob
Hi CKB
Yesterday I got everything set up following your instructions. Seems to be working great, no software hurdles or issues to speak of on initial experience. One thing I did notice is that the physical fader does not follow the channel when the automation lane for that channel is selected by itself; guessing this is a limitation with MIDI remote, as the Control Change communicated is tied to the selected channel fader, and the automation track/lane does not have a fader associated with it…
Okay anyway, so I think I might have a hardware issue that I would like to ask for your advice on. To preface, I bought the FaderPort V2 brand new. The motorised fader seems to not behave how I would expect, comparing to other equipment i’ve experienced in the past. It’s not smooth and It seems “jittery” for lack of a better word. You can see/hear what I mean in the video below.
I’ve tested the unit in Nuendo, both in StudioOne mode with script, MCU without script, also I downloaded Studio One 6 demo and tested it there in the respective mode, all 3 produce the same results.
You mentioned before that you have two of these units. Can you tell me if this is normal? or should I organise a replacement?
Thanks,
Sam
Hi Sam,
the motorized fader of my newer FaderPort is mainly quieter when it comes to quick position changes.
The motorized fader of the newer FaderPort also “shakes” a little, and it makes also a difference in which direction it moves.
In practice, I have here and there a boost, a fade-in or a fade-out, but while this, the slight “shaking” doesn’t bother me.
A wild “back and forth” like in your example doesn’t really exist in my projects.
I guess 95% of the time I use the motorized fader, I use it for input and with this there is no jittering during recording (= writing automation data), so everything is ok for me.
If the motorfader moved more smoothly on your previous device, sorry, I understand that you notice this now in comparison.
Maybe someone else here has an opinion on this?
Regards * CKB
By the way… Which production week [C01 YY WW] is noted under your FaderPort?
I had also looked at the Midi fighter Twister (available for over 10 years).
But the newly revised Intech Studio EN16 has the same functions, is much cheaper, more compact and there are various other modules from Intech Studio that can be combined with it. I also find the Intech Studio buttons a bit more “professional”.
In this case (= if you want that the physical fader does follow the channel) you have to toggle the Read button to “off”, because the automation data on the cursor has priority over a manual fader setting as long as “Read automation” is active, even if the project is stopped.
Thanks for replying. I was hoping you’d say that it is not normal for it to be shaky 
I work in film post production so sometimes there’s a lot of fader moves / automation depending on the content. So it’s something I might have to just get used to. I’ll think about it over the next several days of use. I probably won’t be able to live with it honestly. I did email Presonus directly, let’s see what they have to say when they eventually reply.
Anyways. The production date says C01 23 46, so it’s the newer manufacture batch.
Cheers
Sam
Hi Sam,
however, you should also read the reviews of the alternatives.
For the Icon P1-M, for example, I found this bad current review: 
I was negatively surprised by the build quality (noisy, stiff faders, jog wheel not running smoothly and controller tilting) and that the faders keep readjusting or moving slightly even when no signal is being sent to the controller, even when the daw is closed.
What would particularly bother me about the Icon P1-M and many other devices is that the transport section is not at the bottom of the device. Buttons on the device that you never use are also annoying. With the FaderPort, on the other hand, all buttons are used equally. The FaderPort also has a rest for the hand, with which you can comfortably operate the whole device and that is a feature that I immediately notice when I try out other devices that don’t have this. I have also seen devices where it bothered me that some LEDs were too bright or where I was initially impressed by a display, but was then bothered by the order in which the parameters are listed there, etc…
So I know how difficult it is to find the right decision for yourself, because you never know at the beginning which weaknesses of a device you can accept later on.
By the way, if your film post-production often runs as you describe, i.e. that you have to control the fader volumes of many tracks simultaneously in real time, you should rather buy a multi-channel device. But this costs a bit more than a FaderPort…
Best regards
CKB
Addition: If you are working with the fp-wizard script on a track where the main volume automation is finished, it is no longer necessary for the motorfader to always move automatically in sync with the softwarefader. For such cases, the script offers the option of temporarily switching off the motor. I often do this too, not because of the slight shaking of the fader in some cases, but just so that there is complete silence.
Hey. Following the reply to my PreSonus support ticket, I did a factory reset of the device. The shaking fader has improved a little bit; not perfect, but I think I can live with this now. I don’t want to get rid of it, mainly because i’ve realised the benefit of the FP with your script far outweighs the fader by itself. It’s just a matter of learning the myriad of functions now, getting a “muscle memory” so to speak.
I did have an issue today (after messing with the firmware) where the ‘middle’ section keys weren’t functioning. This was fixed by a simple disable and re-enable of the script as per your suggestion in the document. Working like a dream now!
It’s miraculous how many things can be fixed by a simple off and on cycle.
Regarding the iCON hardware: I mentioned before that I just got rid of my P1 Nano after 3 weeks. It’s an amazing device (in theory), with a lot of great features. The thing that is most bothersome is the software glitches that come in tandem with the hardware malfunctions. It’s just too much to ignore. The breaking point was realising I had a glitch where the controller would be stuck on a particular channel and I couldn’t write automation on any other, even after changing banks it would still go back to that channel when I touched the fader. I’ll never go back to iCON. If I need to change I will go for the Avid Dock or S1 with Eucon. As you say, It is difficult to find what’s right for you, but for now this FP2 solution is perfect.
Regarding my work: I actually don’t need to have control of multiple things at once. It’s not essential, automating one thing at a time is great for me. But I do need a single fader because it’s really fatiguing to click and hold the mouse button for a while on a long automation pass.
the script offers the option of temporarily switching off the motor.
I hadn’t discovered that yet. It’s just what I need. Thank you!
P.S. How can one donate to this cause? I’d like to offer some small remuneration for your hard work and effort with this. Do you have a portal for donations?
Cheers
Sam
That sounds interesting.
Does the factory reset that PreSonus mentioned to you mean starting the FaderPort while holding the Next button?