Midi learing Osc Section of DIVA ??

[xmortenx]

Hi

I have mapped all the functions of Diva to Ni Maschine Studio - and it works beatifully !!

But the OSC section is a mess !! Since Maschine will not allow to duplicate a function on several pages, it´s impossible to map the OSC section since some controls are shared (TUNE etc) while others are very specific to a model..

This means that instead of making a map/controller page unique to each OSC section you have to have a page with the shared controls like Tune, Env etc. and the a lot of other pages with more specific controls to each Oscilator section..

So it ends up a mess.....

Is it possible to assign other CC´s to the shared controls like tune so you can build a map that makes sense to each of the different oscilator section instead of having to tune on page 1, then click 4 pages down to turn on a Saw on the jupiter module, then jump back to page 1 and aply a LFO etc ????

To me it would be better if the OSC sections did not share any controls across different models since most controllers today have few knobs and multiple pages and with Divas mix of shared and non shared oscilator functions you end up with a confusing mess and have to reach for that dreaded mouse....

[Howard]

Shared controls are the same or very closely related functions (though the labels may differ). E.g. "FM1->2/3" in the Triple VCO is shared with "cross" in the Digital model because they do practically the same thing. "Sharing" makes sense (imho), though you might not like the differing labels.

(BTW there's no oscillator parameter called "Env" - not sure what you mean there).

[Sleepwalker]

What you can do is create preset folders in Divas browser within each synth config type. And have spesific controller mapings for those. Its like having a bunch of synths but atleast it works. This is the nature of Diva, its semi modular.

In Ableton Live you could save racks for each of these types. Works for me.

[Phil999]

I agree it can be difficult to map those parameters, but for me it makes perfectly sense. If each oscillator/filter/envelope type had its own parameters for shared functions, the list would become much bigger.

For my Lemur controller, I had to add a couple of send/receive scripts and aliases to make it work. A bit of a workaround, but perfectly functional. With other controllers one has to make compromises.