I’m especially pleased that you implemented a request of mine (from some time ago) - to be able to change the resolution of the rotate knob in QC Mode.
I especially like that this function is not only availabe via a key combination - I think the temporary function via “press/hold Prev Button” and turn the Rotate Button is really convenient - I press the Prev Button with my left hand ring finger, turn the rotate knob with the remaining fingers/thumb and by releasing my ring finger I can change immediately back to the normal resolution.
Also the new manual fader synchronisation within +QC1..4-Mode is a nice addition to the QC Mode - but here I noticed some typo errors in the documentation:
You mention the button combinations Touch+(Link/Pan/Channel/Scroll) for synchronisation, but then list them as “Bypass+Link” etc. instead.
You might correct this with your next update.
So far - impressive work as usuall - I’m just really wondering what’s actually left to be implemented further - but you seem to be always good for surprises.
Also the new manual fader synchronisation within +QC1..4-Mode is a nice addition to the QC Mode - but here I noticed some typo errors in the documentation:
Thanks Frank for pointing that out. I’ve corrected it in the documentation and updated the files directly in the post above.
Now, I’ve also gone thru the AI Mode with the new additions -
the handling is pretty close to the QC-Mode, but it left me wondering, why you didn’t implemented a manual synchronisation for the fader to the rotate knob just as you did within the QC Mode ?
I can’t imagine you haven’t thought about it - some technical reasons maybe ? If not, this might be worth as a further addition to another update. (Not that I need this badly - just thinking out loud…)
Hi Frank, we’ve here been doing this for three years (since the beginning), using this side effect: press the Pan Button and then press the Channel Button. It means switching from the AI Mode to the Hitpoint Mode and then back to the AI Mode, but it has the desired side effect of synchronizing the fader in a simple, very fast way.
indeed a simple, fast way ! Though I’ve once scrolled through this forum to get me an overall overview - this I haven’t noticed. Maybe you could ad this hint to the release notes for the AI-Mode for new users ?
OK, for now… thanks for always being responsive - it’s really a pleasure to be able to talk to you about all those little details with you on this forum !
Thank You for hard work, Christian! I am very happy with this device support and it works under You`re guidance even better than in Studio One! (Especially with last updates about not mechanism in device). Thank You !
Christian, Could You please tell us, how are You using Faderport for writing automation? Like are You just taking parameter on main window and do “Move what`s udner mouse” or there`s more advanced workflow as for You?
Hi shredatormail, within the Pan Mode, Send Mode, EQ Mode, and PF Mode, you can record automation data directly. For midi instrument plugin parameters and insert effect plugin parameters, you can use the “QC” button of the specific plugin to activate Focused Quick Controls, for which you can then record automation data within the QC Mode. For the other, remaining parameters, you can use the AI Mode to record automation data. There are also “Track Quick Controls”.
Thanks, Christian! But the question about You`re own workflow….Like what`s most handy for You as a worker, so do speak. As You, Christian, using the most
I did the update as I was reading the midi-remote horror stories…. I thought “let me cancel that” as I was half way down the page… but it had already finished.
I’m scared to open my DAW this morning… Will share my experience with the latest ver and this precious script later today..
PS.. Can the latest version of the Faderport remote script be pinned in some way? 973 posts to this thread and counting
Hi Volker, I haven’t had any problems with Cubase 14.0.40 and fp-wizard from September 30, 2025 so far. However, when I update Cubase, I always make sure to thoroughly delete all presets and completely reset and recreate all MIDI remotes so that I can be sure there won’t be any side effects with earlier versions. I am also still working with the latest version of Windows 10. Therefore, I cannot generalize my positive experience.
I remember your instructions for the complete reset can be found in the troubleshooting-manual.
I’m still watching the comments about the update in relation to the windows 11 updates and will be updating when the system is not “in need” for important productions.
!
Though I’ve once scrolled through this forum to get me an overall overview - this I haven’t noticed. Maybe you could ad this hint to the release notes for the AI-Mode for new users ?
