Set 2 VelocityCurves with 1 table
ulrik last edited by ulrik
For my plugin that I'm building, I want the user to be able to set the velocity curve in the user interface. I have one AudioLoopPlayer and one Wavesynth and I want to set the same velocurve for both.
I thought I was able to attach a Velocity modulator to the container but the option is not available so I have 2 velomods which I want to control with only one Table, is that possible? And if so, how do I do it?
I also have a similar issue, I want to control the intensity for 2 lfo's with only one knob, is it possible?
d.healey last edited by
@ulrik Yes this is possible, but you'll need to script it, it can't be done using the parameter assignment in the interface designer.
@d-healey Ok, thank you I will try.
You can‘t connect a table to two modules, even with scripting. Use the Global modulator system for this, this is exactly what it‘s made for.
@christoph-hart Ok I see, thank you I will try it.
Here's a example patch:
@christoph-hart Thank you, I will soon check it out.
@christoph-hart It works great, thank you!
bpford last edited by bpford
@Christoph-Hart Christoph, sort of on a similar topic, would you use the Global modulator system if you wanted to give the user the ability and flexibility of assigning the same modulators to different parameters in different modules as they see fit? Say, for instance, I wanted the user to be able to be setup their own modulation routing so they could decide to modulate the phaser rate by "LFO 1"? And then they could use that same "LFO 1" and assign it to modulate the cutoff on a filter module? But, I don't want to pre-bake the routings, I want them to be able to set it up for themselves.
Yes, I am doing exactly this for the modulation matrix in HEXERACT.
You can dynamically create global modulator receivers via scripting, however this is an advanced procedure and rather complicated to understand (you have to be very careful about the order of your elements to restore this correctly when you switch presets).
bpford last edited by
@christoph-hart OK. I already knew I was in over my head but it's good to know that I'm WAY in over my head.
I started out just wanting to build a simple sampler I could throw my custom samples in that wouldn't require too much scripting and could be DAW agnostic.
But now I'm only going to be satisfied by trying to rebuild an emulation of EXS24 with some added features. Guess I better get a lot better at scripting.