New Feature: SuspendOnSilence

[d.healey]

@tomekslesicki It's in the same place as the allow compilation option. Make sure you have no nodes selected.

[tomekslesicki]

@d-healey It should be there when I right-click on a chain, right? !https://imgur.com/a/Gdkyge3

[Christoph Hart]

@tomekslesicki I think if you open networks that have been saved before the addition of this feature, you need to save the network and reload it again - the property editor is being built from the XML data and it needs a resave to add the properties.

[tomekslesicki]

@Christoph-Hart thanks! I added it manually to the xml and it's working like a charm now :-)

[ustk]

@Christoph-Hart Digging up that SuspendOnSilence not appearing in ScriptFX property
It seems the properties that are not in their default state, or just set (it's not clear to me) are purely removed from the value tree.

[orange]

@ustk Does SuspendOnSilence will be the cure for the peak meter lock when the signal is off?

[clevername27]

@orange Dope meter. I use a timer that periodically checks for that.

[orange]

@clevername27 Thanks. It uses timer too. The problem here is that when there is no signal from the display buffer, the display buffer gets stuck at the last value. Do you have a method for that?

[clevername27]

@orange That's a good point. I don't have suspend on silence activated for most of the plugin. (I don't trust it, lol.)

[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

Scriptnode - External Display Buffer when plugin bypassed

I'm using a core.peak node with External Display Buffer to draw some meters. When the exported plugin is bypassed, the Display Buffer seems to just loop unt...

Forum (forum.hise.audio)

[orange]

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