This exact behavior just started for me with no changes between last night and tonight.
In my case it wasn’t set for In ALL MIDI inputs, and flipping that on and off again did nothing to resolve the behavior.
I’ve factory reset my FP2018 and updated the firmware back to the latest. This appears to have done nothing, but I confirmed the behavior was solely in the one session exhibiting it. Other sessions do not have the same issue.
After some experimenting, it seems the offending element in that session was an instance of Backbone. For some reason even if I imported the tracks to a new session and included Backbone, this behavior would return. Without importing the Backbone tracks, no issue with the Faderport issuing notes.
Adding Backbone as a new track seems to have kept the behavior from returning. I’m so confused.
It seems the same issue is manifesting differently for us both. At least on the surface level.
I don’t have “Backbone”, so that’s not applicable to me. I also tested by creating a blank project and it was still happening. That was before I turned FP2 off in All MIDI.
I’m stumped. But I guess I’m lucky because I had a simple fix that works.
Nuendo 14 should be out in about two weeks and the stability should be improved. It is therefore quite possible that the MIDI Remote problems that have persisted recently may have been resolved (also for Cubase).
I have a rogue situation I cannot think how to get out of.
Faderport has stuck on “custom mode on one particular song”
If I switch to another song no problem all as expected.
Tried the obvious, reloaded script, rebooted from cold, tried all combinations of buttons, tried changing page in Cubase midi remote, tried changing faderport mode and reverting to native.
Lost as where to go next.
Any help please !!
Yea thanks people. Had come to that conclusion. Strange that a song can contain data upsetting the initial start of the unit as it normally will only open in one state. I would like the initial opened state to be set with volume on the knob not pan.
Just for completeness it all went as expected. Additionally I copied the new fully functioning song and placed it back in the original folder, replacing the rogue song. It still worked as expected, proving it was nothing unusual in the folder or inserts etc, just the corrupt faderport info in the song.
Thanks LluisV sadly for me this does not work. Loads in pan position.
Did the obvious,
checked script was altered
cold booted both pc and faderport but no go.
I use ioStation24c instead of faderport II with Nuendo 13, but the script works just the same with a few small changes. I use the ‘Master_Mode = true’.
The “midi remote” management system has a bit of random behavior.
I’ve changed my way of working to make it work well for me.
I always open Nuendo projects from windows explorer and if I have to change projects I always quit Nuendo and open the new project from explorer again. If I open projects without quitting Nuendo, the controller doesn’t initialize properly. Sometimes it doesn’t change from ‘Pan’ to ‘Master’ on startup and other times the buttons on the center strip stop working.
It’s annoying but when it starts properly, the controller is really useful.
If I create a new project I use the hub, but always from a new start of Nuendo.
did you try starting a new project to see if it works? I found that when changing this start mode in the script, it didn’t work for already created projects. But it works in new projects after the change. Bit weird, but give it a try.
Let’s hope that these MIDI Remote problems will no longer exist when Steinberg releases a new Cubase update, which will hopefully be available as soon as Nuendo 14 is finally released.
@Martin.Jirsak
these MIDI remote problems that exist when transferring projects from Cubase 13 to Cubase 14 and that also occurred with the scripts for the Behringer controllers, can you tell us if Steinberg will have fixed these problems when Steinberg releases the next maintenance update (hopefully this week)?
Thanks for creating this script. It makes my life so much easier! One question. Is a “scrub” function available, where one scrolls (using the knob, I guess) while hearing the audio. My old Steinberg CMC-TP had this, and it was very helpful.
@loonsailor,
I myself didn’t like the scrub function so much when it was linked to the Rotate Knob with MIDI Remote because of the playback speed of the scrubbing. I tried that once.
But you can still use the scrub function if you make a code change in the script in the following lines (for version 29, May 2024) using a simple editor for text files:
line 4805
old code: 'Transport', 'Nudge -1 Frame').setSubPage(subpage_Scroll)
new code: 'Transport', 'Jog Left').setSubPage(subpage_Scroll)
line 4807
old code: 'Transport', 'Nudge +1 Frame').setSubPage(subpage_Scroll)
new code: 'Transport', 'Jog Right').setSubPage(subpage_Scroll)
This code change has the effect that if you have selected the fp-wizard-setting step per frame for the Scroll Mode, scrubbing takes place instead of scrolling per frame.
Sorry I haven’t written anything here since December.
Like many others, I’m eagerly awaiting a new Cubase update, which will hopefully be released with the release of Nuendo. This is also the reason why I have not yet published the already finished update of fp-wizard here. Cubase version 14.0.10 still has some bugs with MIDI Remote and in the past (i.e. 13.0.50) there were also problems.
It is important to me that I can test the finished update of fp-wizard with the next Cubase version (14.0.20 ?), because more than 1650 lines of new code have been added, some of which is very complex, because I have programmed things that are not available in the API, so I had realized the programming with various java-script ‘tricks’.
And I would like to know for sure that these ‘tricks’ also work with Cubase 14.0.20 and - if not - that I can make the necessary adjustments without you having to work with a defective version.
Steinberg will hopefully be ready soon and I think they have also worked very hard and that the wait since November 2024 will have been well worth it in the end.
This means that when Cubase 14.0.20 is out and my update of fp-wizard runs well with it, I will publish it here a few days later.
