Modulation behaviour

[Reincke]

Hello,

I recently noticed a changed behaviour of MuLab due to the modulation amplitude. I some cases the modulation signal inside a Mux will obviously be clipped to 100%, which MuLab didn't in earlier versions.

I think it would be interesting for a user like me to know, where a modulation signal is clipped by MuLab/Mux, I mean which module input/output will automatically clip and which will not.

Any idea?
JR

[MuTools]

Yes, it's the same issue as with the Whistler preset you recently sent me.
Since the new 64 bit versions, there indeed is a little bug in the modulation system which limits the modulation signals between [-100% - +100%]. That will be fixed in the forthcoming MuLab 4.4 / MUX 1.1.

Normally modulations are not bound until they're applied to the parameter.
A bit like with audio: You have all headroom until the very last step when the audio goes out of MuLab / MUX, then it's bound to max valid levels.

[Reincke]

Normally modulations are not bound until they're applied to the parameter.

Thank you for this hint. Just to clarify: That means every cable and the modulation mapper won't clip, but e.g. an AIPS input jack of an oscillator module will do?
And M4.4 won't clip modulation signals anymore?
JR

[pljones]

In programmer-speak: If valid values are for a parameter 0.0f to 1.0f and you modulate in sum total to 200% you will not get 2.0f, you will get 1.0f.

(I've not tried this so I don't actually understand the problem or what the fix will change...)

[MuTools]

That means every cable and the modulation mapper won't clip, but e.g. an AIPS input jack of an oscillator module will do?

Indeed.

And M4.4 won't clip modulation signals anymore?

Indeed.

(only at the very last step i.e. when they modulation is applied to the parameter)

[Reincke]

In programmer-speak: If valid values are for a parameter 0.0f to 1.0f and you modulate in sum total to 200% you will not get 2.0f, you will get 1.0f.

You're right, thank you. I think that's what clipping means. My question was: At which "points" inside a patch MuLab will clip modulation signals automatically and at which it does not, now and in a future version?
JR

EDIT: The last posts were intersecting, so I unterstand clipping will be done everytime a modulation signal is applied to a "consuming" parameter. Thank you all.