Matrix Modulation Feedback

[DanH]

@ustk yes exactly, but we don't want Macro 1 assigned to Macro 1 do we?!

So perhaps there's a way to remove the Modulator from the list if you're trying to connect it to itself.

[ustk]

@DanH No, why would you lol. There are not in the target list if you don't assign a matrixTargetId
The way I understand it is that you don't want them to be "modulatable", you just assign a macro + another modulation to the parameters, and it has the same effect

[DanH]

@ustk Modulating a Macro can be useful though... :)

[ustk]

@DanH I agree with this, but then it is a design choice. I prefer to see macro as a modulator than "something else" aside the modulation part. It seems easier for me to understand and use, but my practice of modulation and macro is very limited...

I'd just say that in a plugin, I prefer to keep related things in one place so it better fits my vision to have marco like modulator

Perhaps it is possible to have two sets of modulators, so one can modulate another? I don't know...

[Christoph Hart]

@ustk you can modulate a modulator by assigning a matrixTargetId to the UI knob of any modulator parameter.

[DanH]

@Christoph-Hart but is there a way to prevent a user modulating a macro with the same macro?

[ustk]

@Christoph-Hart Okay There's also the AUX modulation (which should achieve the same thing, right?) but I couldn't seem to make it work...

[DanH]

@Christoph-Hart did setInitialIntensityValues become a thing?

[Oli Ullmann]

@DanH
You can do this with setMatrixModulationProperties

HISE | Scripting | ScriptModulationMatrix

A class that encapsulates the management of complex modulation systems

(docs.hise.dev)

[DanH]

@Oli-Ullmann said in Matrix Modulation Feedback:

HISE | Scripting | ScriptModulationMatrix

ah that's where it went! Thanks!