New Feature: SuspendOnSilence

[ForeverLive]

@Christoph-Hart This is fantastic update! God bless HISE.
Nice that the new feature "gate" is working with RNBO well!

[ustk]

@Christoph-Hart I found 2 bugs regarding this new feature

At first, I am not using Scriptnode
I am only using the processBlock CB to perform my recordings and other stuff that are waiting for a flag to start, but since it is now suspended (S), evidently nothing happens.

So I created an embedded DSP and disabled the SuspendOnSilence flag of the main DSP container -> the S disappeared successfully.
But still, the processBlock CB isn't firing (a simple console print shows nothing)

Going back to the node to double check -> the SuspendOnSilence button disappeared

Restart Hise and project:

• S isn't showing
• SuspendOnSilence button doesn't reappear
• processBlock CB still doesn't fire by itself

Now I need to sleep, the rooster is waking up already... Need a SuspendRoosterOnSilence

[DanH]

@ustk you have a rooster?!

[ustk]

@DanH not compatible with my cats, but my neighbor has many, with hens, geese... Joys of a 30 souls village :)

[ustk]

@Christoph-Hart So apparently processBlock is bypassed when a network is present, which I think is normal behaviour.
But then, without a network, there's no possibility to set the SuspendOnSilence flag which makes processBlock to be always gated when no signal is present.

[Christoph Hart]

I changed it so that it doesn't suspend the script processors by default. I could add a scripting method that controls this behaviour, but using script processors without a DspNetwork is so 2016 that I don't want to spend too much time with this :)

[ustk]

@Christoph-Hart Mmm great! Thanks!
Yeah, that's old school but it's the only way (that I think, since you helped me a while back on that matter) to record a buffer from an input stream.

[Lindon]

@ustk said in New Feature: SuspendOnSilence:

@Christoph-Hart Mmm great! Thanks!
Yeah, that's old school but it's the only way (that I think, since you helped me a while back on that matter) to record a buffer from an input stream.

So your using the process block to record incoming audio? Is that right? If so: "How are you doing that!!"

[ustk]

@Lindon Basically, you create a buffer and just copy the incoming stream into it. Since processBlock is continually firing, just set a flag (here the recordIndex is used as a flag) to tell when you want it to record the buffer.

reg recBuffer = Buffer.create(yourLength);
reg recordIndex = -1;

function processBlock(channels)
{
	if (recordIndex != -1)
	{
		local numSamples = Math.min(recBuffer.length - recordIndex, channels[0].length);
		local temp = Buffer.referTo(recBuffer, recordIndex, numSamples);
		
		if (numSamples == channels[0].length)
		{
			channels[0] >> temp;
		}
		else
		{
			local s = Buffer.referTo(channels[0], 0, numSamples);
			s >> temp;
		}
		
		recordIndex += numSamples;
		
		if (recordIndex >= recBuffer.length)
			recordIndex = -1;
	}
}

A simpler version to understand would simply be to copy the samples one by one in a for loop, but it's a bit greedy on cpu cycles. So this version Christoph gave me is much lighter since the copy process is made per block.

Bear in mind that you can't test this in Hise standalone because the inputs aren't activated.
Though I don't use the Hise plugin version for this, it should work (and the same for the exported project of course, it can't work in standalone unless activating the inputs)

[Christoph Hart]

Bear in mind that you can't test this in Hise standalone because the inputs aren't activated.

I think you can test it by dragging an audio file into the HISE Controller DAW timeline...

[Lindon]

@ustk said in New Feature: SuspendOnSilence:

@Lindon Basically, you create a buffer and just copy the incoming stream into it. Since processBlock is continually firing, just set a flag (here the recordIndex is used as a flag) to tell when you want it to record the buffer.

reg recBuffer = Buffer.create(yourLength);
reg recordIndex = -1;

function processBlock(channels)
{
	if (recordIndex != -1)
	{
		local numSamples = Math.min(recBuffer.length - recordIndex, channels[0].length);
		local temp = Buffer.referTo(recBuffer, recordIndex, numSamples);
		
		if (numSamples == channels[0].length)
		{
			channels[0] >> temp;
		}
		else
		{
			local s = Buffer.referTo(channels[0], 0, numSamples);
			s >> temp;
		}
		
		recordIndex += numSamples;
		
		if (recordIndex >= recBuffer.length)
			recordIndex = -1;
	}
}

A simpler version to understand would simply be to copy the samples one by one in a for loop, but it's a bit greedy on cpu cycles. So this version Christoph gave me is much lighter since the copy process is made per block.

Bear in mind that you can't test this in Hise standalone because the inputs aren't activated.
Though I don't use the Hise plugin version for this, it should work (and the same for the exported project of course, it can't work in standalone unless activating the inputs)

cool.. I must find some time to look at this... Thanks.

[tomekslesicki]

This is perfect! I can't see the option to turn the suspend on silence on my scriptnode chains, though. It works on the snippet that Christoph provided. Is there anything extra I need to do to have this? I'm on the latest Develop build, compiled today.

[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?