modulation overflow? what?

[FabBad]

Hi!, i'm building a generative synth with some nested mux in there and another some parameters automated with Sample and Hold.
In any random time MUX shows a popup window.
The question is, am i doing something wrong or is some kind of limitation by the number of parameters automated?
Thanks

[MuTools]

This can happen if you're doing extreme intense modulations, like (almost) audio rate modulations but still using non-audio rate green cables. Eventhough the internal limit that triggers this warning could be raised (i'll evaluate that), it would still use quite some cpu to do (almost) audio rate modulations using non audio rate signals. Pls try switching to real audio rate modulation in the patch you're building. This can be done using the a Modulation To Audio -> Audio To Modulation converter combi. I realize there should be a way to do this using a single module. This will be added in a future update.

[FabBad]

Many thanks, Jo, It works aparently fine now. And yes, somethimes isn't necessary the audio rate.

[MuTools]

Don't you have a couple of converters too many there?
I think the 2nd and the 3rd can be dropped.
So Noise -> Audio To Mod -> S&H -> ...

[FabBad]

So Noise -> Audio To Mod -> S&H -> ...

yeah, but as you sugest, this was the original form that supossedly gave it the mod overflow.
Is there another way?

[MuTools]

I don't understand. After the first Audio To Mod the mod signal is audio rate anyway. So i don't understand where that overflow is coming from unless you're sending an extreme amount of note events to the S&H, like thousands of events per second.

[FabBad]

So the method "Audio to mod -> Mod to Audio -> Audio to Mod" doesn't deactivate the audio rate modulation...
i'm wrong, is for another reason...
but theres no more popups up to now.
I will keep using and investigate it.
Thanks for your time Jo.

[MuTools]

You can check yourself whether a modulation signal is audio rate or not: In the Modulation Monitor there is a small indicator at the right side of the signal level display. When that indicator is off the mod signal is not audio rate, when it's on the mod signal is audio rate.

The overflow alert you got can only occur when using non audio rate at extreme high frequency.
In the next update i've removed the internal limit that can trigger that overflow warning alert (at the cost of a bit more ram usage) because it's too confusing/technical.
But even while you will not get that overflow warning anymore (when using the next update), i expect that when you use extreme high frequency non audio rate modulations this will still result in a rather high cpu usage for that MUX patch.

Please also elaborate what you actually want to achieve with this MUX patch.

[FabBad]

You can check yourself whether a modulation signal is audio rate or not: In the Modulation Monitor there is a small indicator at the right side of the signal level display. When that indicator is off the mod signal is not audio rate, when it's on the mod signal is audio rate.

That is what made me noted.

The overflow alert you got can only occur when using non audio rate at extreme high frequency.
In the next update i've removed the internal limit that can trigger that overflow warning alert (at the cost of a bit more ram usage) because it's too confusing/technical.
But even while you will not get that overflow warning anymore (when using the next update), i expect that when you use extreme high frequency non audio rate modulations this will still result in a rather high cpu usage for that MUX patch.

Why not an option in context menu, something like "enable audio rate" in modulation type modules?

Please also elaborate what you actually want to achieve with this MUX patch.

I'm building a custom waveshape made oscilator inside a Poly Synth, and i wanted to tweak some parameters and at the same time play some random notes in a scale. So, there's result of 18 S&H patches with their corresponding clock generator (step sequencer) triggering that patches. Nothing serious, just for fun.

I leave the patch here for further investigations

[MuTools]

I'm building a custom waveshape made oscilator inside a Poly Synth, and i wanted to tweak some parameters and at the same time play some random notes in a scale. So, there's result of 18 S&H patches with their corresponding clock generator (step sequencer) triggering that patches. Nothing serious, just for fun.

I leave the patch here for further investigations

I inserted your MUX patch ( nice ) but i don't get that overflow warning. What do i have to do to get that overflow warning?

[MuTools]

PS: Due to the fact that M8.6.16 avoids this overflow warning i think this case can be closed.

Just this tip: If you do high frequency modulations, it might be more efficient to use audio rate modulation. With M8.6.16 each green modulation cable can be set to ensure an audio rate signal.
Double-click a cable to edit its properties.

[FabBad]

What do i have to do to get that overflow warning?

I don't know exactly, maybe, as you said, by extreme frecuencies modulations, and the additional of several instances of the same patch...

PS: Due to the fact that M8.6.16 avoids this overflow warning i think this case can be closed.

Just this tip: If you do high frequency modulations, it might be more efficient to use audio rate modulation. With M8.6.16 each green modulation cable can be set to ensure an audio rate signal.
Double-click a cable to edit its properties.

Excelent! that is amazing and yes, this is gone.
Thanks for your atention Jo.