Diva - map for Automap 4 and Remote SL MkII controllers

[Z]

I made an automap for the Triple VCO in Diva.

Here's the idea: because of the different layout and configuration of all of the modules in Diva, I decided to make one map per oscillator module (hopefully I'll only need to make one map for all of the DCO's - the Triple VCO is the most complex of them all), and then let all of the filters, envelopes and modulation modules be tweakable within the same automap.

I used Automap 4.2b2 which is a bit buggy here and there, so I need people to 'beta test' it, and of course modify it if they have a better layout than the one I used. As a matter of fact feel free to do it!

You'll quickly get the idea of how I've been thinking: There's one page for each of the oscillators while the filter and envelopes are assigned to the same knobs/sliders/buttons on every osc page, so no matter which oscillator page you're on, you find the filter and envelopes on the excact same controls as the previous one. With the same values which can come in pretty handy at times.

I assigned the top right button (to a CC called Cont - Continue would be my guess...) to display which page you're currently on. So if you wonder, select the top row buttons at all times to see where you are.

There are 6 pages in total, but haven't mapped any FX except for chorus for FX1 and FX2, or the Modifications and Trimmers modules yet. This is a work in progress.

This is my first automap, so any feedback is welcome.

The file can be found here (you may have to right-click and chose save link).

[rexlapin]

Thanks for taking the time to do this!
Cheers,
Scott

[PAK]

I'm almost done building a multi-purpose map myself (looks like it's heading for 8 or 9 pages) which has mapped all controls, including the modifications tab and 5 or 6 automation parameters which aren't present on the GUI - I'm not sure if they even do anything (They seem related to things like multi-core processing etc.)

Some of the stuff is quite easy to map. All filter types can be mapped with just 6 knobs and seven buttons, and all envelope types with 8 knobs and 8 buttons (excluding the 4 Vel/KYBD sliders). This is purely thanks to the smart way Diva has implemented those automations (allowing you to toggle model types) rather than Novation.

It's a shame Urs didn't continue this thinking with the FX in slot one and two, so that EG mappings to Chorus1 rate/wet/depth knobs would also control Phaser1 feedback/stereo/wet or Plate1 decay/wet/size etc when you switched to them. This way it'd have been possible to step through all possible FX controls, for both slot 1 and 2, with approx 16 knobs and 8 buttons (easily within 1 page on a Novation controller). Currently you have to sprawl controls for ten FX types (5 on slot 1, and 5 on slot 2) across three pages to map the FX controls logically (Ouch!) But, thinking about it, it'd also have been more confusing to people looking at those controls in a DAW if it'd been done this way, since they'd need to be aware what the FX type value was set at to know what those automated controls were doing (IE the same automation lane would be controlling different things depending on what the FX type value was set to!)

The blame for the page sprawl problems is largely at Novations door though, since they don't support nested controls. Imagine being able to map a button next to the LFO controls that toggled between LFO1 & 2 - leaving the rest of the page map alone. This would essentially replicate how hardware synths like the Access Virus or even Novations own synths work and allow building more logical map layouts without the same sprawling "page" navigation issues present in the current Novation system. This would be more complicated for them to do, and make maps a bit harder to create for end users, but would make the controller way more effective and more like dedicated hardware controls. Someone needs to start a campaign for nested controls

The troublesome bit in Diva I'm trying to sort out is mapping the VCO's and mixer in a logical manner. The mixer itself only takes 4 knobs and 4 buttons for all types except the Moog, which then adds 3 volume controls as well as noise and feedback. But then you've got another 8 buttons and 2 knobs taken up by Tune and Shape, plus the two MS20 waveshape knobs nothing else uses. I've piled them all on two pages right now whilst I try to figure what might work best I like to avoid the rotary encoders where possible since they work well for some controls but I, personally, hate how they feel for stuff like filter sweeps.

Btw - An automation control for moving between Main/Modifications/Trimmers/Scope and Patches would be nice

[Mogular]

rotary encoders work best for set and forget parameters like modification sources and destinations, as well as the oscillator octave set controls.
I always map filters and envelopes to the fixed knobs and the sliders

[Z]

I'm almost done building a multi-purpose map myself (looks like it's heading for 8 or 9 pages) which has mapped all controls, including the modifications tab and 5 or 6 automation parameters which aren't present on the GUI - I'm not sure if they even do anything (They seem related to things like multi-core processing etc.)

8 or 9 pages, that's with all the FX's or did you have one map with every oscillator module as well?

The blame for the page sprawl problems is largely at Novations door though, since they don't support nested controls. Imagine being able to map a button next to the LFO controls that toggled between LFO1 & 2 - leaving the rest of the page map alone.

Indeed, that would be perfect. Another, basic feature that's missing is simply copy/paste. I could have saved a lot of time if I was able to copy/paste since most of the controls are duplicated many times over. Oh yeah, and duplicate pages would come in pretty handy too!

The troublesome bit in Diva I'm trying to sort out is mapping the VCO's and mixer in a logical manner. The mixer itself only takes 4 knobs and 4 buttons for all types except the Moog, which then adds 3 volume controls as well as noise and feedback. But then you've got another 8 buttons and 2 knobs taken up by Tune and Shape, plus the two MS20 waveshape knobs nothing else uses.

That's why I decided to have the Moog VCO in a map of its own. Since it has a 'fixed' mixer, it'll save me the headaches of how to integrate the other HP filter modules so it makes sense.

Btw - An automation control for moving between Main/Modifications/Trimmers/Scope and Patches would be nice

Hmm, maybe it's possible since you can map switching osc/filter/env/fx modules - I assigned a button for each (excluding the oscillators), so you can i.e. cycle through the different filter modules at the touch of a button. My goal is to reach for the PC mouse as little as possible.

[Echoes in the Attic]

Thanks for this. I haven't had a chance to make one yet. I've been debating whether to map each osc module separately, or just map all parameters possible to a single oscillator page. It would save a lot of space, you'd just have to remember which knobs don't do anything for the modules you're using. I'll see how it fits.

How did you guys find the coarse and fine tune knobs worked out? Since they are actually the same control, does it reset the fine tuning when you modify the coarse tune via automap? I'm not sure yet if you can have the coarse tune mapped to only send relative increments and leave the fine tuning where it is.

[Z]

I'm not sure yet if you can have the coarse tune mapped to only send relative increments and leave the fine tuning where it is.

No you can't, AFAIK. I tried, but it only caused the oscillator to get wildly out of tune whenever I changed an octave.

[Echoes in the Attic]

I'm not sure yet if you can have the coarse tune mapped to only send relative increments and leave the fine tuning where it is.

No you can't, AFAIK. I tried, but it only caused the oscillator to get wildly out of tune whenever I changed an octave.

hmm I thought that might be a problem. This is the one design flaw I see with DIVA. You can't map the tune knobs separately to hardware as they are the same parameter. So if you want to keep your fine tuning but change octave, you're tuning will be reset I suppose?

Have to test more to see if there is a way around that.

[aMUSEd]

I made an automap for the Triple VCO in Diva.

Here's the idea: because of the different layout and configuration of all of the modules in Diva, I decided to make one map per oscillator module (hopefully I'll only need to make one map for all of the DCO's - the Triple VCO is the most complex of them all), and then let all of the filters, envelopes and modulation modules be tweakable within the same automap.

That's exactly what I did for the Kore 2 template as well - seemed the best solution

[Echoes in the Attic]

I made an automap for the Triple VCO in Diva.

Here's the idea: because of the different layout and configuration of all of the modules in Diva, I decided to make one map per oscillator module (hopefully I'll only need to make one map for all of the DCO's - the Triple VCO is the most complex of them all), and then let all of the filters, envelopes and modulation modules be tweakable within the same automap.

That's exactly what I did for the Kore 2 template as well - seemed the best solution

What did you do about the fine/coarse osc tuning? Is it a non-issue or just something to live with?

[Z]

You can't map the tune knobs separately to hardware as they are the same parameter. So if you want to keep your fine tuning but change octave, you're tuning will be reset I suppose?

Well, that's what I found out and I didn't see any way around that. I mapped the Range controls in steps of 10 or 20 or so, (I can't remember the exact value), but it was useless since the detune knob turned from 12 to 4 o'clock by changing only one octave. I changed it back to the normal value from 1 to 100 in steps of 1. It still gets detuned, but way less than before.

[xh3rv]

With Automap 4, I'd probably just use two knobs, one with size 1.00 and another with .01 in the 'size' parameter of the range sub-tab for the tune knobs. Love this bit or 'range' about Automap 4, hate some other parts about it >.<

[Echoes in the Attic]

Yeah I'd do the same. I'd use two knobs for the tune and try setting each to a different increment. By the way, setting the range of a control has always been possible, not just with automap 4.

But my concern was that if you have two knobs controlling tune, one with 0.01 for example and one with 1.0, and you set the fine tune say 0.08 detuned, will that get reset when you adjust the coarse knob? I'll find out when I get home. It might be that there is no problem, I just don't remember if automap increments go from the current position in relative increments. If so, then nothing to worry about.

[xh3rv]

... By the way, setting the range of a control has always been possible, not just with automap 4.

So it was! I double-checked, looks like it was put into v3.2 in 2009 ... I was really excited to see it in v4, must've missed the v3 stuff.

But my concern was that if you have two knobs controlling tune, one with 0.01 for example and one with 1.0, and you set the fine tune say 0.08 detuned, will that get reset when you adjust the coarse knob? ...

I can confirm it behaves nicely, .08 coarsely tuned will jump to 1.08 or -.92. It will clip to whole numbers at the min and max.

[bobbybland]

Awesome thank you my friend!