Matrix Modulator - Advantages?
-
@Christoph-Hart
First of all, thank you very much for the great modulation system!It is possible to add a slider and its parameters to the modulation system via the “matrixTargetId” in the Properties field.
However, I can also load a Matrix Modulator module into the corresponding slot.
Does one method have advantages over the other?
Specific example:
-
If I want to modulate the saturation of a SineWaveGenerator, I can do so by assigning a “matrixTargetId” to the corresponding slider on the UI.
-
However, I can also load a Matrix Modulator into the GainModulation chain.
Can you tell me what the advantages or disadvantages or differences are?
Many thanks,
Oli -
-
matrixTargetId is useful if you want to link a single UI control to multiple matrix modulators.
-
@Orvillain
I think my question is more about whether I need to use a MatrixModulator to implement a modulation system in my plug-in, or whether the “matrixTargetId” is sufficient. After all, it works without MatrixModulator. -
@Oli-Ullmann Hard to say without knowing more about what you want your final results need to be. I needed to use the matrixTargetId because I knew for some of my controls I only wanted 1 UI element on screen, but I wanted to control multiple target parameters from the modulation system.
IE: Let's imagine you've got 3 samplers, and each one of those has a SimpleGain in its effects section. Then you add your matrix modulator to each of the 'gain modulation' targets, and you give them all the same id inside the 'edit ranges' section.
Then you add a knob, and give it the same matrixTargetId as what you gave to each one of the modulators... and then the knob will control the value parameter for each of the modulators all at once.
-
If you modulate a knob with the matrixTargetId instead of a matrix modulator, you lose the following benefits:
- polyphonic modulation
- sample accurate modulation, as the value is sent once per buffer size.
Eg if you want a polyphonic modulatable waveshaper it‘s better to make a scriptnode effect with an additional modulation slot that you pick up with a extra_mod node in the DSP network.
-
Thanks, guys, that's very interesting and helpfu! :-)
-
O Oli Ullmann has marked this topic as solved
-
@Christoph-Hart said in Matrix Modulator - Advantages?:
If you modulate a knob with the matrixTargetId instead of a matrix modulator, you lose the following benefits:
- polyphonic modulation
- sample accurate modulation, as the value is sent once per buffer size.
Eg if you want a polyphonic modulatable waveshaper it‘s better to make a scriptnode effect with an additional modulation slot that you pick up with a extra_mod node in the DSP network.
I thought the whole point of the matrixTargetId was to be able to address multiple matrix modulators, retaining polyphony throughout the pipeline?
IE:
1 knob on screen. 3 matrix modulators in the module tree. Everything sharing the matrix ID.
Why would that cost you polyphonic modulation??
-
@Orvillain ah that's a misunderstanding. If you use the matrixTargetId to connect to one or more MatrixModulators, then it's fine and you get a polyphonic sample accurate signal. I was referring to using the matrixTargetId to create a modulation target for any parameter which doesn't have a modulation chain that you can populate with a matrix modulator (like the saturation amount of the sine wave in the example).
