Can someone tell me why this doesn't work?

[RJHollins]

For some reason, this circuit caught my interest ... but I've not figured out what its' suppose to do

Will we ever learn more ? and the final circuit ?

[Perfect Human Interface]

and the final circuit ?

You asked for it...

Hold Decay.PNG (85.94 KiB) Viewed 11778 times

All this just to learn how inaccurate the peak detection is when it's coming off a mono to float.

[RJHollins]

hmmm ...

well ... I was close on the 'peak' idea

Not good to hear about the inaccuracy, though

Thanks for posting the schematic pix. Would take some time to 'trace' it all though.

For whatever reasons, metering always seem a difficult project. I've must of demo dozens ... and purchased more than I really should have

Right now I've settle with the Klanghelm VU meters. They are about as close to hardware as I've been able to match.
Well worth the $10 purchase. It is a combination VU with PEAK readout.

Doesn't help us much in FS-land ... but it would be nice to match up to it from FS.

Nonetheless ... you did bring a bit of excitement and group participation ... those are fun to watch [and learn from]

Thanks!

[Perfect Human Interface]

That whole thing is just a mess to take a "max" peak value and hold it for a bit before gradually releasing it. It's probably garbage code so no sense trying to analyze it... though it works. The inaccuracy comes from a mono to float after the actual peak detection (not shown here) pulling it back into green.The mono to float only ticks off at 100 times a second, so it's naturally going to miss a lot of values when audio rate is going at 44,100 times a second. With normal visual meters this doesn't matter since your monitor is limited to 60 Hz anyways, but for what I'm trying to do here I'd need to go back into blue to do this accurately at sample rate. I just wish DSP code supported extra things like "ifs" so my simple mind could stick to simple things rather than having to look up how to do bitmasking and such.

[RJHollins]

I completely follow you.

I guess the proverbial question ... is RUBY capable of processing at samplerate ?

Just trying to learn more

[nix]

You could go at 1000hz instead of tick100 with Ruby custom ticker if u wish.

[oddson]

That whole thing is just a mess to take a "max" peak value and hold it for a bit before gradually releasing it...

Code: Select all

streamin x; // signal
streamin t; // reset time in samples
streamout y; // max signal
float i,xMax;
xMax = xMax - (i>t & xMax); // reset peak after t cycles
i = i - (i>t & i) + 1; // increment counter with reset to 1 at t+1
xMax = max(x,xMax) ; // retains former peak unless new peak or at reset
y = xMax;

[Perfect Human Interface]

Haha, thanks oddson. I could have sat down and figured it out myself but here you are making me look bad. The whole masking thing is just slightly abstract so I forget how to do it.

[oddson]

It came up before on SM Site but I couldn't find it as the Site was down. Replicating it took far longer than it should have as I'd forgotten how to use the code module.

[RJHollins]

hmmm ... this might mean that we are not seeing enough of you here at the FS forum !!!

Seriously ... glad to see you here. Hope you find time to visit and post.

You always provide great insight with many helpful code examples and concepts [SM forum]. Wish I would have been there during the hay days. I missed a lot of learning opportunities

Always looked forward ! Hope all is well for you !

Thanks oddson