New Feature: SuspendOnSilence

[orange]

@clevername27 Ehehe, I haven't used it yet. Does it crash or something?

[clevername27]

@orange No crash, it just felt a little sus to me – there are often issues with those types of algorithms (such as that which you are experiencing). Love that meter.

[orange]

@clevername27 said in New Feature: SuspendOnSilence:

Love that meter.

Thanks. Meter of this: https://noiseash.com/prestige-racks/

[Lindon]

@orange said in New Feature: SuspendOnSilence:

@clevername27 said in New Feature: SuspendOnSilence:

Love that meter.

Thanks. Meter of this: https://noiseash.com/prestige-racks/

mate they continue to look really really nice...

[orange]

@Lindon Thanks mate, your stuff looks nice too

[ustk]

@orange Yeah it looks really nice!
And that must have been thousands of hours to get all these DSP emulations! Congrats

[ustk]

@orange As for the meter, I don't see where it could be related to SuspendOnSilence but I'm limited on the topic... Looks more like a timer stopping. If the level is gated gated at the output, how could the meter say there's a signal if we hear nothing? The peak meter probably gets it's level directly from the output signal path so...

[orange]

@ustk said in New Feature: SuspendOnSilence:

@orange Yeah it looks really nice!
And that must have been thousands of hours to get all these DSP emulations! Congrats

Thank you. Yeah, it takes a long, long time.

[orange]

@ustk said in New Feature: SuspendOnSilence:

@orange As for the meter, I don't see where it could be related to SuspendOnSilence but I'm limited on the topic... Looks more like a timer stopping. If the level is gated gated at the output, how could the meter say there's a signal if we hear nothing? The peak meter probably gets it's level directly from the output signal path so...

It doesn't make this all the time, it happens randomly. Also, it seems like it's not just about the timer.

It happens in the analyzer in the Dragging Filter Panel FT.

[Dan Korneff]

If I'm understating the issue correctly, there is a function that was implemented in January to fix displays when the plugin is bypassed:
setOnBypass

https://forum.hise.audio/topic/8739/scriptnode-external-display-buffer-when-plugin-bypassed?_=1729626310133

[orange]

@Dan-Korneff Yes, definitely the same issue. If .setOnBypass is the solution to this problem, good, I will try it immediately. Thanks.