Matrix Modulation Feedback

[DanH]

@Orvillain said in Matrix Modulation Feedback:

activated "ExternalModulation" for each scriptnode parameter

Ah, this could be the missing piece! Haven't seen that before.... Which of the choices do I want for which scenario?

EDIT - Boom, working! Thanks. Went for combined....

[ustk]

@DanH @Orvillain Same time working here you guys rock

In my case it was the parameter range causing the issue...

[Orvillain]

@DanH Yep, combined is what I use too!

Also worth pointing out, once you do this, it is worth setting the effect instance parameter to maximum value, and controlling the actual value from the matrix.

Also - you don't need to have a matrix modulator attached to everything if you don't want. In fact, some parameters you can't right... coz they don't have module entry points, for example in a case where HC effect doesn't have the parameter external modulation enabled.

In those cases if you set the UI knob processorId and then parameterId, and then give the UI knob's "matrixTargetId" field some kind of entry... then that UI parameter will work with the modulation system. But I think the difference is the rate of the modulation will be locked to blocks, rather than being properly audio rate - which for CPU reasons might be better in some cases than others.

[DanH]

@Orvillain Yes that's more or les it as I understand it, although you can set the block size.

I find that I need to restart Hise in order to cement the connections, same for you?

[Orvillain]

@DanH said in Matrix Modulation Feedback:

@Orvillain Yes that's more or les it as I understand it, although you can set the block size.

I find that I need to restart Hise in order to cement the connections, same for you?

Hmmm, no don't think so. Just recompile.

[DanH]

@Orvillain odd! I'll keep testing. So, I remember now, that this system removes the non-modulated value going to the parameter / knob until a note is played (bad for Filter UI!!). Was there a fix for that? Seem to remember it on the forum a couple of weeks ago

Also, do you put anything in the processorId / parameterId for the ui controls? Or leave them blank? Seems to work either way (but neither control the non-mod value as above).

[ustk]

@DanH for the second question you need to set the matrix modulator Value knob for processorId/parameterId
It becomes your unique entry point for both modulation and manual setting
This is why setting the parameter range is necessary

[Oli Ullmann]

@Orvillain
If you only use the “matrixTargetId,” you will have limitations in modulation. Furthermore, the modulation will only be monophonic. This is particularly important to note with envelopes.

@DanH said in Matrix Modulation Feedback:

So, I remember now, that this system removes the non-modulated value going to the parameter / knob until a note is played

I talked to @Christoph-Hart about it, and this is what he said:
"Yeah, I have to change that—the problem is that any envelope will only render a signal and send a UI update message when voices are rendered, but I need to change that so that the matrix modulator sends out updates even when no voice is present, so that this is updated correctly."

[DanH]

@Oli-Ullmann something else curious - the value amount shown in the Matrix Module bar isn't the amount set on the UI slider or the 'Value' slider in the module itself.

[Oli Ullmann]

@DanH
Hmm, I don't see anything right now. Maybe because I don't have a hardcoded effect that I can load in the snippet. I'll take another look at it over the weekend.

Another thing I noticed:
In your picture, the gain knob is set to -100db. If you're using a matrix modulator, the knob should be set to 0db, i.e., the maximum.