I’m
New here , but we converted to Cubase because of your fine work .
We owe you more than we have right now . But making sure to fill your stockings this year !
A favor kind sir if we may , Is there anyway to assign knobs to say retrologue on my atom or my atom sq ? I know this is a stretch but the transition would be lovely if this could be possible … either way thank you Cubase and thank you sir for developing this fine script and your valued time ….
Much appreciated !!’
Hi WEM,
Can i use FP2 with Nuendo 11. It dosent seem to support Midi remote script import.
Many thanks
Kev
@WEM: thanx for the cool script! I have only one question: the scroll function is not suitable for me. I often work with film music and I need to scroll in frames. but the scoll function only jumpes between 2 seconds (or 1 bar ). In Mackie mode you can scroll down in frames. Is there a possibility to change this?
A second point: I miss the RTZ function (pressing both << + >>). 
Only Nuendo 12 or Cubase 12 for this script. The FP2 can be used with Nuendo 11, but you’ll have to use Mackie Control and use banks, which blows.
Hello all,
was offline a while for finishing another project. At the moment I wait for a Cubase update that is announced to bring a few enhancements and changes. Especially regarding the motor fader integration for automation.
Thx for bringing in all your ideas. I’ll definitely have a look at this very good ideas in the next revision.
@Tonkutscher I did’t find unfortunately aother way to implement scrolling. It’s already implemented by using some tricks and hacks because it’s not forseen as functionality. But I will definitely have a look at this topic because I not happy with this, too. I’ll also look at the RTZ function - I’ve missted this completely…
Regarding compatibility: The script should work on Cubase 12 (I’ve tested on 12.0.40 on Win11 x64) and Nuendo 12. I don’t have the possibility to test the Script on a Mac or Nuendo.
One issue I could imagine is the midi port name: this can be adopted by using and editing the JavaScript file or changing the names in the Cubase/Nuendo settings.
I’ll definitely update the script and I’ll will keep you updated here!
Thx to all
Werner
@WEM: I made some test now and found that steinberg changed something in the scrolling behavior. Your script works if I change in the arranger the quantize from grid to free and zoom in. Than I can scroll in frames, but only if the ruler shows bars + beats. If you change there to second it does´nt work. Thats different to CB 11.
Hi! I’ve just bought a used Faderport v2 and used the script- thank for this!
I’m having a couple of issues though: when I use the fader to write automation it intermittently just stops writing…then starts again!
Also, my controller knob is strange when I’m adjusting the panning: it doesn’t respond properly, jumps around and doesn’t seem to adjust in increments of 1 like I presume it should…
can anyone help?! I’m hoping I’ve not bought a dud…they guy seemed fine, and it looks pristine…
Just giving this a wee bump…the automation problem is a pisser… weirdly it works fine on my Apple M1 laptop?
But using the control knob for panning is still all over the place.
My main computer is a 2020 3.8 GHz 8-Core Intel Core i7 and I really would like the automation to work properly on it…
Anyone else had these problems?
@WEM have you any thoughts? Thanks!
Regarding automation: this is actually the best possible implementation with the today’s possibilities. Steinberg announced to introduce a touch fader implementation and updates for the automation interface. Unfortunately the update isn’t released until now.
This is something you must live with for the moment but I‘m pretty sure that it will be solved sooner. A solution/workaround is to switch to MCU protocol to write automation.
Regarding panning: I have from time to time the issue that the knob doesn‘t react directly - but this is the same with MCU. It‘s a HW or firmware related topic. But jumping around, like described by you, I did not have.
Are you on C12.0.40? Do you have the same experience with other knob functions: e.g. volume of the CR, scrolling or value under the mouse cursor?
@all
I‘m at the moment reviewing some issues and suggestion from here. There will be an update of the script in the next days.
Best regards
Werner
@WEM
Hi Werner, many thanks for replying so promptly, I appreciate it!
The Control knob is def better when scrolling through the tracks, not perfect but certainly usable.
Using it to adjust the panning isn’t usable at the moment.
And yes I’m on latest Cubase 12.0.40
I’ll def live with the automation issues on my iMac, and look forward to a better solution.
But it’s odd that it works on my M1 laptop!
Thanks again, BSB.
Hello @Big_Scottish_Bloke,
I have now played a while with the topic. I can clearly reproduce the jumps and behavior also on my computer. In my opinion this is caused by the Cubase internal processing and mapping of the value into the range of 0 to 1 in floating point numbers. It looks to me that in some cases Cubase internally rounds the numbers and therefore we experience are some jumps. I’ll contact Steinberg about this and review this topic again.
Near the investigations on the PAN topic I added also the RTC function to my script. You can find the new version on my homepage: PreSonus Faderport (2018) and Steinberg Cubase 12 (Update) - wem-music.de
best regards
Werner
Hi @WEM ! Many thanks for your help- I’ve downloaded the most recent script and love the return to zero function!
Panning and automation much the same- Presonus tech support have been pretty hopeless, they even said “let us know if theres any change” !
But much appreciate your efforts! 
Wow, incredible. Like many here, the beautiful but frustratingly poorly implemented FP2 was about to become a doorstop. I threw the JS file into the folder as instructed (easy!!), rebooted, unselected the Mackie controls, rebooted again, and boom - magic. Beautiful!
This deserves a Grammy for technical achievement, and maybe a Nobel Prize for bringing peace and happiness to the lands. THANK YOU und DANKE SCHOEN @WEM you are a God!
Another big thank you to @WEM!
Quick question - anyone else bumping into an issue where the motorized fader doesn’t respond unless the device is power-cycled?
Thank you!
Hello,
I did not observe such a behaviour. Can you describe the steps to reproduce it and give me a insight in your system configuration?
best regards
Werner
Thank you. Seems to be a random occurrence but i’ll try to find the rule and recreate it deliberately.
And while I have you, is there a “Unarm All” option? (as in, another press on the same button doesn’t seem to reverse this action).
Thanks again
@wem: I have just tried the latest version and used the Java script in Cubase 12.0.50. There seam to be a bug: sometimes CB don’t start it hangs on SKI Remote. I have to switch off the FaderPort, then the start is kompleted. After finishing the start I can switch FP on. It works, but if I want to change the Song and close it. CB hangs on closing. I have to switch off the FP again to close the song and load another. Also interesting: during start of CB the Pan Button turns to white and CB stops loading.
Sad, it just happend also to the midiremote file.
Hello,
I will check this issue. I observed also an issue on closing Cubase a few days ago - but as was just one time I did not care much about it.
Thx for the hint with the button color - this could be an hot lead:
Initially I had some strange issues when setting the color of the buttons - I was never able to find out why, because if worked for a few buttons but not for others. In Cubase 12.0.40 I did not have experienced this issue anymore and I was thinking about Steinberg may fixed it. May they issue is back with 12.0.50?!?!
Can you give me some details on your system: Windows/Mac?
@Jave_Hughes unfortunately there is no possibility to „Unarm All“ at this moment. I hope Steinberg adds this in some future updates.
Best regards
Werner
Windows 10 Pro 21H2, Core i5 -8500 (6x 3GHz), 16 GB Ram.