Diva, the "configure" tool in Live and Ubermap

[moscom_musik]

Hi,

I am trying to configure Diva to play with it using Ableton Push in Live 9.1.1 and the ubermap script. To do so, I create a rack that contains only Diva, and I then use the "configure" tool in Live so that Push can see the parameters I want to edit.I would then edit the cfg file.

Something puzzles me here. Say I use the DCO oscillator. I click on one of the square wave controls in Diva control panel to create a controller in Live's configure panel. The controller Live creates does not show the name of the wave then: it shows a number, and it is thus not so informative. It is the same if I change the filter mode from 12dB to 24 dB for example. Does anyone of you fellow members know if there is a way to get parameter string values directly from DIVA? If that does not work, would there be a way to edit the string sent to Push so that it displays strings instead of numbers using Ubermap?

I have asked this question on U-He's forum at KVR too, and did not get an answer yet: I was curious to see if I would get feedback here too.

thanks!

Moscom

[tom_d]

I have no idea why this is, but I've found it with some other synths too, e.g. LuSH-101. The weird thing is, some other effects/synths pass it through to Push perfectly (e.g. Fabfilter Timeless 2), and even weirder, in Live you can see the correct string in the Configure bit for LuSH, but it doesn't get through to Push!

Anyway, in the next version of Ubermap, I've added a feature where you can specify a custom mapping for values for knobs like this as it annoyed me too It's not quite ready to be unleashed yet but I will post it up when it is.

I did investigate the "DeviceParameter" object that the MIDI Remote scripts see, to see if this proper string gets passed through and stored somewhere, but looks like it gets lost somewhere between Ableton and Python, so you have to set it up yourself

[moscom_musik]

Hi tom_d,

first thanks a lot for the awesome work you have done with Ubermap! I have used it to design a custom mapping for Waldorf Largo (that I should post here by the way) and I rediscovered this synth. That is why I am so interested in mapping DIVA this way.

Adding a way to edit the strings that gets to Push depending on the value of the controller would be a great work-around! Do you have any idea when this will be available? I will take a week off in two weeks, and I would be super happy to play with thi feature at this time

Cheers

Moscom

[tom_d]

I'll hopefully get it out next week... It's basically working but because the config has become more complex, it seems to be making it slower to change devices/banks (as it tries to reload the config every time), so I need to fine tune the performance. Can always send you the unfinished version in advance if I have it working but still needing fine tuning.

I'm really curious to try your Largo mapping - I purchased a second hand Blofeld the other week, but had to return it due to a faulty encoder (quite common apparently). When I was testing it out, it did occur to me that an Ubermap interface for it might almost be better than the actual interface (as it only has 7 knobs and a lot of paging)! I did like what I heard of its sound though, and as I understand it Blofeld is very similar, so if you could post up your config, I'd love to try out the demo!

[moscom_musik]

Here you go! I was interested in controlling the synthesis parameters: the mapping does not control the modulation matrix, the arpeggiator, and the effect section (among other things). Nonetheless, it was revelation to me: such a blast to edit the synth with knobs!

Should I post it somewhere else?

Code: Select all

[Banks]
[[Osc 1]]
1_Osc 1 Active = On/off
2_Osc 1 Octave = Octave
3_Osc 1 Semitone = Semi
4_Osc 1 Detune = Detune
5_Osc 1 Shape = Wavetbl
6_Osc 1 Wave = Ini Wave
7_Osc 1 Wave Source = WMod Src
8_Osc 1 Wave Amount = WMod Amt
[[Osc 2]]
9_Osc 2 Active = On/off
10_Osc 2 Octave = Octave
11_Osc 2 Semitone = Semi
12_Osc 2 Detune = Detune
13_Osc 2 Shape = Wavetbl
14_Osc 2 Wave = Ini Wave
15_Osc 2 Wave Source = WMod Src
16_Osc 2 Wave Amount = WMod Amt
[[Osc 3]]
17_Osc 3 Active = On/off
18_Osc 3 Octave = Octave
19_Osc 3 Semitone = Semi
20_Osc 3 Detune = Detune
21_Osc 3 Shape = Wavetbl
22_Osc 3 Wave = Ini Wave
23_Osc 3 Wave Source = WMod Src
24_Osc 3 Wave Amount = WMod Amt
[[OscMods1 ]]
25_Osc 1 FM Source = Osc1 FM Src
26_Osc 1 FM Amount = Osc1 FM Amt
27_Osc 1 Brilliance = Osc 1 Brll
28_Osc 1 Keytrack = Osc 1 Kytr
29_Osc 2 FM Source = Osc 2 FM Source
30_Osc 2 FM Amount = Osc 2 FM Amount
31_Osc 2 Brilliance = Osc 2 Brll
32_Osc 2 Keytrack = Osc 2 Kytr
[[OscMods2]]
33_Osc 3 FM Source = Osc3 FMSrc
34_Osc 3 FM Amount = Osc3 FMAmt
35_Osc 3 Brilliance = Osc3 Brll
36_Osc 3 Keytrack = Osc3 Kytr
37_Osc 2 Sync To Osc 3 = Sync 2>3
38_Noise Colour = NoiseCol
39_Pitch Mod Source = PMod Src
40_Pitch Mod Amount = PMod Amt
[[OscMixer]]
41_Osc 1 Level = Osc1 Lvl
42_Osc 1 Balance = Osc1 Bal
43_Osc 2 Level = Osc2 Lvl
44_Osc 2 Balance = Osc2 Bal
45_Osc 3 Level = Osc3 Lvl
46_Osc 3 Balance = Osc3 Bal
47_Noise Level = NoiseLvl
48_Ring Modulation = RingMod
[[Filter 1]]
49_F1 Type = Type
50_F1 Cutoff = Cutoff
51_F1 Resonance = Res
52_F1 Drive Curve = Drive Crv
53_F1 Drive = DriveAmt
54_F1 Envelope Amount = Env Amt
55_F1 Envelope Velocity = Env Vel
56_F1 Keytrack = Kytrk
[[Filter 2]]
57_F2 Type = Type
58_F2 Cutoff = Cutoff
59_F2 Resonance = Res
60_F2 Drive Curve = Drive Crv
61_F2 Drive = DriveAmt
62_F2 Envelope Amount = Env Amt
63_F2 Envelope Velocity = Env Vel
64_F2 Keytrack = Kytrk
[[FiltMods]]
65_F1 Cutoff Mod Source = F1CutModSr
66_F1 Cutoff Mod Amount = F1CutModAm
67_F1 FM Source = F1FMSr
68_F1 FM Amount = F1FMAm
69_F2 Cutoff Mod Source = F2CutModSr
70_F2 Cutoff Mod Amount = F2CutModAm
71_F2 FM Source = F2FMSr
72_F2 FM Amount = F2FMAm
[[FilMixer]]
73_Filter Routing = FilRout
74_Bass Boost = BassBoost
75_F1 Level = F1 Lvl
76_F1 Pan = F1 Pan
77_F1 Pan Mod Amount = F1PanMdAm
78_F2 Level = F2 Lvl
79_F2 Pan = F2 Pan
80_F2 Pan Mod Amount = F2PanMdAm
[[Amp Env]]
81_AE Mode = Mode
82_AE Attack = Attack
83_AE Attack Level = Att Lvl
84_AE Decay = Decay
85_AE Decay 2 = Decay 2
86_AE Sustain = Sustain
87_AE Sustain 2 = Sustain 2
88_AE Release = Release
[[Fil Env]]
89_FE Mode = Mode
90_FE Attack = Attack
91_FE Decay = Decay
92_FE Decay 2 = Decay 2
93_FE Sustain = Sustain
94_FE Sustain 2 = Sustain 2
95_FE Release = Release
96_Noise Balance = NoiseBal
[[Env 3]]
97_E3 Mode = Mode
98_E3 Attack = Attack
99_E3 Attack Level = Att Lvl
100_E3 Decay = Decay
101_E3 Decay 2 = Decay 2
102_E3 Sustain = Sustain
103_E3 Sustain 2 = Sustain 2
104_E3 Release = Release
[[Env 4]]
105_E4 Mode = Mode
106_E4 Attack = Attack
107_E4 Attack Level = Att Lvl
108_E4 Decay = Decay
109_E4 Decay 2 = Decay 2
110_E4 Sustain = Sustain
111_E4 Sustain 2 = Sustain 2
112_E4 Release = Release
[[LFO 1&2]]
113_LFO1 Shape = LFO1 Wav
114_LFO1 Speed = LFO1 Freq
115_LFO1 Sync = LFO1 Sync
116_LFO1 Delay = LFO1 Del
117_LFO2 Shape = LFO2 Wav
118_LFO2 Speed = LFO2 Freq
119_LFO2 Sync = LFO2 Sync
120_LFO2 Delay = LFO2 Del
[[LFO 3]]
121_LFO3 Shape = LFO3 Wav
122_LFO3 Speed = LFO3 Freq
123_LFO3 Sync = LFO3 Sync
124_LFO3 Delay = LFO3 Del
125_Ring Mod Balance = RngModBal
126_Amp Mod Source = AmpModSr
127_Amp Mod Amount = AmpModAm
128_Glide Time = GlideTm
[BestOfBank]
[[Bank]]
1_Osc 1 Active = Osc 1 Active
2_Osc 1 Octave = Osc 1 Octave
3_Osc 1 Semitone = Osc 1 Semitone
4_Osc 1 Detune = Osc 1 Detune
5_Osc 1 Shape = Osc 1 Shape
6_Osc 1 Wave = Osc 1 Wave
7_Osc 1 Wave Source = Osc 1 Wave Source
8_Osc 1 Wave Amount = Osc 1 Wave Amount
[Config]
Cache = False
Ignore = False

[moscom_musik]

And of course, I am eager to test the latest version of Ubermap. That coupled with PXT and the community mapping transform Push in the controller I have been looking for for ages!

[tom_d]

Looks great! I'll try it out when I have time.

Yeah, the 128 param limit strikes again We should all take the time to contact Ableton and ask for it to be increased. That said, stuff like modulation is probably easier on screen anyway.

In terms of places to post the mapping - i guess I should set up a thread just for that purpose. When I get round to making the editor, I plan to make it able to upload and download configs from some shared repository but don't hold your breath

[moscom_musik]

It sort of becomes a job, if you go down the editor road I must say that this would be excellent.

I was actually thinking about posting a few requests in the feature wishlist forum. The 128-parameter limit was one of these requests.

Thanks again!

Cheers

Moscom

[tom_d]

It sort of becomes a job, if you go down the editor road I must say that this would be excellent.

I was actually thinking about posting a few requests in the feature wishlist forum. The 128-parameter limit was one of these requests.

Thanks again!

Cheers

Moscom

Heh, well the motivation behind the editor is partially that there are a few new Web technologies that I'd like to try out, so I'm going to use the editor as an excuse to try those out and then put it up on GitHub as an example of my skillz (having good code on GitHub is becoming quite important for software devs these days, kind of an online calling card/proof of your abilities). It's just finding the time that is hard... especially now I can see summer approaching and the beer gardens calling But I will keep you all posted on progress. Glad you are enjoying the script

[moscom_musik]

The call of Beer, mightiest of the mighty

I have been thinking more about DIVA's mapping, and one of your remarks came back to my mind. At some point, you told me that the work-around involved that the cfg file had to be reloaded every time the plug-in is accessed, and that made the editing process slower because of the increase of the time to reload the more complex cfg files ( am I right here?).

Doe that mean that we could imagine finding a sweet spot where the cfg file could be reloaded dynamically if you switch modules in a vst for example? I have DIVA in mind of course. Right now I am planning to make cfg files for fixed DIVA configurations (all Moog, all Alpha Juno, all Juno, All MS20, mix of these...) so that I can circumvent the 128 parameter limit. Now, It would be wonderful if I could add the mode menus for the oscillators, filters, enveloppes, etc to the configure panel and that a change in any of these menus would load the appropriate config file corresponding to the new DIVA config. Do you think that this would be feasible?

If you need someone to betatest the current version of ubermap, I would be happy to do so.

Hope that I am clear enough.

Cheers

Moscom