Spectrum Analyzer gets stuck

[pcs800]

@d-healey Never mind, i found the missing comma :-)

[pcs800]

@d-healey This change in code didn't help. It still sticks.
I did change the gainrange, to no avail.

[d.healey]

@pcs800 I looked further into my project (it's been a while) and seems I am setting up some properties in the script too - not sure if this is documented anywhere.

local dbs = Synth.getDisplayBufferSource("parametriqEq");

setEqProperties(dbs);

inline function setEqProperties(displayBufferSource)
{
	local props = {
		"BufferLength": 4096,
		"WindowType": "Blackman Harris",
		"DecibelRange": [-100.0, 0.0],
		"UsePeakDecay": false,
		"UseDecibelScale": true,
		"YGamma": 1.0,
		"Decay": 0.6,
		"UseLogarithmicFreqAxis": true
	};
			
	local dp = displayBufferSource.getDisplayBuffer(0);
	dp.setRingBufferProperties(props);
}

[DanH]

@pcs800 it could be to do with suspend on silence. When audio's not passing through it will disable the module. But of course the analysis curve has a decay which hasn't fallen to 0.

@Christoph-Hart is there a way to disable this?

[pcs800]

@d-healey I put that code in onit and get an error
Interface:! Line 107, column 7: Cannot define local variables outside of inline functions or callbacks.
Parametric:! Line 107, column 7: Cannot define local variables outside of inline functions or callbacks.

This line

local dbs = Synth.getDisplayBufferSource("Parametriq EQ1");

[d.healey]

@pcs800 Ah that makes sense. Change the local to a const.

[pcs800]

@d-healey

Const dbs = Synth.getDisplayBufferSource("Parametriq EQ1");

Interface:! Line 107, column 7: Found identifier when expecting ';'
Parametric:! Line 107, column 7: Found identifier when expecting ';'

[d.healey]

@pcs800 Lowercase c

[pcs800]

@d-healey Oh boy, it seems that upper/lower case thing trips me up a lot :-/
So yes, now the analyzer is retracting as expected.
My next adventure will be to change its color to cyan.
How do I do that? Is it a laf thing? If so, I will be stuck for a while, I have not watched any tutorials on laf.

[d.healey]

@pcs800 Yeah laf is the way to go. There are a few laf functions for the analyser.

[pcs800]

@d-healey Can you point me to something that would educate the quickest for this particular use?

[d.healey]

@pcs800 Have you used paint routines?

[pcs800]

@d-healey Actually I spoke too soon. The analyzer is still sticking, but not as much. Meaning, it leaves less of a peak showing than before. So I changed "Decay": 0.6, to "Decay": 0.3, and it seems to have fixed it

[pcs800]

@d-healey Paint routines, no I have not

[d.healey]

@pcs800 In that case just search my channel for look and feel/laf/paint routine videos. I haven't done one specifically about the EQ or analyser but once you know how laf works for one component it's pretty much the same for all.

In some of the older videos I'm using global look and feel because that's all we had. But these days you should use local look and feel instead - except for a few special places.

You might also be able to use css for the analyser, but I haven't covered that in any videos.

Btw, paint routines and laf are essentially the same. Paint routines are for panels only, while laf is for all other components.

[pcs800]

@d-healey Ok I will check into it. Thanks

[pcs800]

@d-healey So, instead of
const laf = Engine.createGlobalLookAndFeel();

I should use
const laf = Engine.createLocalLookAndFeel();
Correct?

[d.healey]

@pcs800 Content.createLocalLookAndFeel I think - check the API browser