Hi ALl , Omnisphere 3 can now be controlled with a Moog One , for some reason Cubase is NOT passing the front panel data to Omnisphere 3 , Pitch and mod Will and keyboard obviously work fine just the front panel is not sending data to Plugin .
Standalone version of Omnisphere 3 works immediately without changing any settings.
I’m just wondering if there’s some kind of filter I need to turn off , I am sending “NRPN” from the front panel of the Moog one , which is how the Omnisphere 3 manual suggests
ThanksMartin. I did try that after doing an AI search suggests that I’ve got to set this up manually with Midi remote as cubase doesn’t work direct with “NRPN” I’ve email spectrasonics support , as they suggest it should work I wouldn’t quite know how to set up a mini remote cause I’m not sure of how they have mapped their plug-in
If I get an answer, I’ll update it here in case someone else is looking
If you want to control a plug-in parameter directly (i.e. via its internal Learn function or direct MIDI mapping), you don’t use MIDI Remote. You would use the MIDI Remote only if you control the plug-in by using Cubase’s Quick Controls.
MIDI Remote supports RPN/NRPN messages. In the MIDI Controller Surface, click on Resolution and select the 14 Bit NRPN option.
The problem is that the standalone version of Omnisphere 3 is pre-maxed so I shouldn’t have to create my own remote really unless Cubase can’t pass the data
I have the same problem with my DSI Mopho which sends NRPN, too! Works fine with Omnisphere 3 standalone or the plugin in any other DAW but not in Cubase. Moog Muse or Novation Launch Control (both send simple CC) work with the plugin, but not the Mopho. So it seems it is a problem with forwarding NRPN from the keyboard to the plugin within Cubase. Did you find a solution?
I just found an older thread named “omnisphere-hw-integration-not-working-in-cubase-13-pro” (sorry, can’t post a link). Seems like Cubase 13 had the same problem with NRPN but it was solved with an update.
FYI, my OBX8 NRPN-mode hw integration with Omnisphere 3 works perfectly in Nuendo 14, but not in CB15 Pro using various test configs (including default preferences reset). Omnisphere seems to respond to the first parameter change and instantly adjust the relative value of the mapped control, but then all other input data is ignored.
I’m planning to do another complete reset of C15 over the weekend and will report back if I gather any additional information.
OK, doing more testing with the exact same setup in N14, the failure for Cubase 15 to properly parse NRPN data seems to be consistent. Midi Monitor shows the exact same data with the exact same configuration between the two - the only difference is that in CB15 Pro, the “first touch” of a parameter from the hardware (my OBX8 filter cutoff was used in testing) results in a very brief (~200ms) message flashing on Omnisphere 3 indicating it saw the initial attempt to set the parameter, but then it ignores everything, even though Midi Monitor shows the same data stream that N14 does.
Hazarding a guess, the most prevalent change I see in CB15 is:
Control Change Support Extensions
Cubase now supports the easier to use registered (RPN) & assignable (NRPN) controllers from the MIDI 2.0 protocol.
Given previously reported fixes for this in 13.0.40, my guess is some manner of bug regression and/or mangling of NRPN from MIDI 2.0 integration.
@grayedout Andy, do you mind just tagging your OP as issue and cubase-15 so we don’t have to create a new thread? I think the history of this thread would be valuable if this is in fact some kind of bug and not something we’re supposed to work-around differently in CB15.
