I'm running Diva as VST2 through Reason. I can't get MIDI learn to work with my Oxygen Pro Mini controller. The keys, mod wheel and pitch all work, and the MIDI activity indicator lights up when I use them.
I can force a connection between Diva parameter and Oxygen control using Reason's remote override mapping, but that's not exactly ideal because it affects that control on other instruments.
I can't get MIDI learn to work on Tyrel or Vital either, so I don't think it's a problem with Diva.
I have even tried to set the MIDI channel in the midiasign file (ie. channel 1, control 3 for the VCF cutoff) then assign the same settings to bank 1 knob 1 in the Oxygen preset editor, and nothing. It just won't work!
Has anyone else had an issue like this?
Diva doesn't recognise controls from Oxygen Pro Mini in MIDI learn
-
tasmaniandevil tasmaniandevil https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=62450
- KVRAF
- 2171 posts since 22 Mar, 2005 from a planet called u-he
That's a forced limitation of Reason, probably to promote the usage of their own MIDI learn system.
Reason won't let MIDI controller data (apart from pitch bend and mod wheel) directly through to the plugin.
You have to use their MIDI remote system to control plugin parameters.
Reason won't let MIDI controller data (apart from pitch bend and mod wheel) directly through to the plugin.
You have to use their MIDI remote system to control plugin parameters.
That QA guy from planet u-he.
-
- KVRer
- Topic Starter
- 3 posts since 9 Oct, 2022
Problem is that I can't get it to work in ableton either
-
tasmaniandevil tasmaniandevil https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=62450
- KVRAF
- 2171 posts since 22 Mar, 2005 from a planet called u-he
If it doesn't work in any DAW, you might have to consult the Oxygen user guide on how to correctly set it up.
From a quick glance at its user guide, I can see that it has two modes, a DAW mode and a preset mode.
In DAW mode, all controls are already mapped to functions of the DAW, I could imagine that it's not possible to assign the controls to anything else in this mode.
It seems you have to set it to Preset mode in order to freely assign controls to plugin parameters.
Also make sure it's actually selected in the list of MIDI devices of the Live track the plugin is loaded on.
From a quick glance at its user guide, I can see that it has two modes, a DAW mode and a preset mode.
In DAW mode, all controls are already mapped to functions of the DAW, I could imagine that it's not possible to assign the controls to anything else in this mode.
It seems you have to set it to Preset mode in order to freely assign controls to plugin parameters.
Also make sure it's actually selected in the list of MIDI devices of the Live track the plugin is loaded on.
That QA guy from planet u-he.
-
- KVRer
- Topic Starter
- 3 posts since 9 Oct, 2022
Thanks for the advice. I have changed it to preset mode and even used the preset editor software to assign parameters manually. But I'd like midi learn to work, obviously that's much more convenient. I've written to M audio, but their customer service is slow (to not say rubbish!)
-
- KVRist
- 36 posts since 11 Apr, 2020
Hi, I'm having this same problem with Podolski, in Reaper (just by way of further corroboration that it's probably an issue between u-he - and who knows possibly other developers - and Oxygen Pro Mini ...or the whole of that M-Audio series..?).
I can map only some parameters, those which Reaper recognises, to cc knobs; but something like the transpose parameter on the arpeggiator seems to be beyond Reaper's native cc mapping reach.
I can map only some parameters, those which Reaper recognises, to cc knobs; but something like the transpose parameter on the arpeggiator seems to be beyond Reaper's native cc mapping reach.
Last edited by liperli on Thu Nov 03, 2022 3:51 am, edited 1 time in total.
-
tasmaniandevil tasmaniandevil https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=62450
- KVRAF
- 2171 posts since 22 Mar, 2005 from a planet called u-he
I don't know how Reaper's CC mapping feature works, but I suspect it can only map parameters which are also exposed as automation parameters to the host.liperli wrote: Tue Nov 01, 2022 9:17 pm I can map only some parameters, those which Reaper recognises, to cc knobs; but something like the transpose parameter on the arpeggiator seems to be beyond Reaper's native cc mapping reach.
The main transpose parameter is not available for host automation, thus Reaper might not be able to assign it to a CC.
Have you tried using Podolski's own MIDI learn feature?
You can MIDI learn the transpose parameter to a CC this way.
That QA guy from planet u-he.
-
- KVRist
- 36 posts since 11 Apr, 2020
Thanks for the reply...unfortunately it is precisely that I can't map all of the (apparently) mappable parameters that are highlighted when clicking on Podolski's native midi learn option. (I've also tried doing it with the manual option Podolski provides, next door to it on the same menu bar, where you specifically choose which cc number you want assigned to which parameter).
I think I can pretty much confirm though that you are right in suggesting that Reaper's native plugin cc mapping range corresponds to that of available automatable parameters (I had a quick look at this, and certainly the parameter or two I had tried mapping with Podolski's native function were not available as being automatable)
Having re-read my previous post and thought about it a bit more, it may be a Reaper/u-he issue (as far as midi cc mapping is concerned, anyway), rather than an Oxygen Pro Mini/u-he one. Or maybe a combination of all three. Quite frustrating though, that what Podolski is showing as mappable (pretty much everything in the plugin) can't be done with Reaper/Oxygen Pro Mini.
One thing I did notice when trying the manual cc mapping option in Podolski, is that the click/drop-down menu for setting the parameter there has a 'last clicked control' option, which is how Reaper's native midi learn function works. Seems a bit of a remote possibility, but wondering if there might be some conflict there.
I think I can pretty much confirm though that you are right in suggesting that Reaper's native plugin cc mapping range corresponds to that of available automatable parameters (I had a quick look at this, and certainly the parameter or two I had tried mapping with Podolski's native function were not available as being automatable)
Having re-read my previous post and thought about it a bit more, it may be a Reaper/u-he issue (as far as midi cc mapping is concerned, anyway), rather than an Oxygen Pro Mini/u-he one. Or maybe a combination of all three. Quite frustrating though, that what Podolski is showing as mappable (pretty much everything in the plugin) can't be done with Reaper/Oxygen Pro Mini.
One thing I did notice when trying the manual cc mapping option in Podolski, is that the click/drop-down menu for setting the parameter there has a 'last clicked control' option, which is how Reaper's native midi learn function works. Seems a bit of a remote possibility, but wondering if there might be some conflict there.