Hi there,
Under the MIDI tab in Wavetable, one can assign the "Key" parameter to whichever mod destination one wants. However, the Key parameter's range is quite strange. The only way of convering the whole wavetable with the "Key" parameter is to set the Osc Pos parameter to 50% and then modulation amount from Key to Osc Pos to 10.
The Fold parameter is similar. Basically, you cannot set Osc Pos or Fold to 0 and then modulate them with a unipolar source like "Key" - the Key source acts more bipold, while the same mod source on Expression Control, called Keytrack, is unipolar. When I assign Keytrack to Osc Pos or Fold, while both parameters' initial values are at 0, I can cover their full range with the full MIDI note range.
When an internal LFO in the Wavetable is used to modulate Fold, nothing happens when Fold is at 0, regardless of the LFO modulation amount. In this case, the value of the Fold parameter acts like a modulation amount, but then the LFO values affect it unipolarly, not bipolarly. Or in some strange way I can't really figure out.
The Warp parameter does not behave like this.
Overall, I think the modulation matrices of the Wavetable synth need an overhaul and standardization. I think having three different matrices is also a bad design decision.
Thanks
Korhan
Wavetable "Key" modulation source not working properly
Wavetable "Key" modulation source not working properly
Computer: MBP M1Pro 32GB 1TB, MixPre 6 MKII
Hardware: Syntrx II, Matriarch, Hydrasynth, Minifreak, Nord Drum 2, Modular (mainly Make Noise)
Controllers: Push 3, Launchpad Mk3, Launch Control, Sensel Morph, PC4, Nanokontrol
Hardware: Syntrx II, Matriarch, Hydrasynth, Minifreak, Nord Drum 2, Modular (mainly Make Noise)
Controllers: Push 3, Launchpad Mk3, Launch Control, Sensel Morph, PC4, Nanokontrol
Re: Wavetable "Key" modulation source not working properly
Yeah, in some case a modulation source/target is unipolar in other cases it's bipolar. Or maybe it's about additive VS multiplicative.
In any case I agree it's disturbing and that's something that always annoyed me too, but I don't think this could ever get changed without breaking presets so I wouldn't hold my breath...
In any case I agree it's disturbing and that's something that always annoyed me too, but I don't think this could ever get changed without breaking presets so I wouldn't hold my breath...
Ableton Forum Moderator
Re: Wavetable "Key" modulation source not working properly
I wonder what the people who coded it like that were thinking... and yeah, I guess it'll always stay like that. Not the end of the world and definitely a 1st World Problem anyway ))
Computer: MBP M1Pro 32GB 1TB, MixPre 6 MKII
Hardware: Syntrx II, Matriarch, Hydrasynth, Minifreak, Nord Drum 2, Modular (mainly Make Noise)
Controllers: Push 3, Launchpad Mk3, Launch Control, Sensel Morph, PC4, Nanokontrol
Hardware: Syntrx II, Matriarch, Hydrasynth, Minifreak, Nord Drum 2, Modular (mainly Make Noise)
Controllers: Push 3, Launchpad Mk3, Launch Control, Sensel Morph, PC4, Nanokontrol
-
- Posts: 39
- Joined: Sat Aug 04, 2012 6:46 pm
Re: Wavetable "Key" modulation source not working properly
I reported this on centercode a long time ago. Makes modulating those parameters next to useless and is something I constantly butt heads with when using this synth. Couldn't they just make a legacy version of Wavetable that loads with old projects and have all new instances load a fixed version?
I also agree that Ableton's synths need some kind of updated, standardized (and modernized) modulation matrix. The drag and drop method on VSTs like Serum make life a million times easier when clicking around with a mouse.....
I also agree that Ableton's synths need some kind of updated, standardized (and modernized) modulation matrix. The drag and drop method on VSTs like Serum make life a million times easier when clicking around with a mouse.....
Re: Wavetable "Key" modulation source not working properly
Agree, the synth is broken it needs to be fixed.