Re: [Faudiostream-users] lufs loudness analyser

On second thought, I don't see at the moment how anything can go wrong with this: sliding_mean(durSamples) = (+ ~ _) - @(int(durSamples)) : /(durSamples); Since there is no rounding involved, the cancellation has to be exact. We just have to ensure that the implementation does not subtract

Re: [Faudiostream-users] lufs loudness analyser

The obvious conclusion, of course, is to work out the ping-ponged truncated integrators, for measurements this long. We just need two 0.4s mean calculators that alternate. I'm sure I'll work it out sometime soon if nobody beats me to it. I imagine a square wave, select2, the sliding-mean unit,

Re: [Faudiostream-users] lufs loudness analyser

Actually, the pattern we want kicks in at durSamples = 32 (circular-buffer delay line). On Sat, Jul 10, 2021 at 10:53 AM Julius Smith wrote: > > I'm not sure I understand what you mean by allocating a delay line for > the sliding mean, but I'll look into it. > > Here's an example implementation

Re: [Faudiostream-users] lufs loudness analyser

> I'm not sure I understand what you mean by allocating a delay line for the sliding mean, but I'll look into it. Here's an example implementation in Faust. The "small test" allocates a length 8 delay line. The full test takes too long to compile, but you can see the pattern, so it's easy to

Re: [Faudiostream-users] lufs loudness analyser

> El 10 jul 2021, a las 15:31, Klaus Scheuermann escribió: > > Hello Juan Carlos, > >> Klaus, I’m using Atom+FaustLive, Max and SC to do the tests, but I get the >> same crash as you with faustide/editor. >> https://www.dropbox.com/s/blwtwao7j317db0/test.mov?dl=0 >>

Re: [Faudiostream-users] lufs loudness analyser

Hello Juan Carlos, > Klaus, I’m using Atom+FaustLive, Max and SC to do the tests, but I get the > same crash as you with faustide/editor. > https://www.dropbox.com/s/blwtwao7j317db0/test.mov?dl=0 > cool, thanks! > Btw the reading are

Re: [Faudiostream-users] lufs loudness analyser

> Le 10 juil. 2021 à 14:47, Juan Carlos Blancas a écrit : > > Klaus, I’m using Atom+FaustLive, Max and SC to do the tests, but I get the > same crash as you with faustide/editor. > https://www.dropbox.com/s/blwtwao7j317db0/test.mov?dl=0 There is indeed a general issue across all FIR base

Re: [Faudiostream-users] lufs loudness analyser

Klaus, I’m using Atom+FaustLive, Max and SC to do the tests, but I get the same crash as you with faustide/editor. https://www.dropbox.com/s/blwtwao7j317db0/test.mov?dl=0 Btw the reading are aprox but not the same as Youlean nor Insight2 for instance… also thinking about how to do the -70 dB

Re: [Faudiostream-users] lufs loudness analyser

Thanks, Juan :) Your code crashes my faustide on firefox and on chromium (both linux). Here is the error message: ASSERT : please report this message and the failing DSP file to Faust developers (file: wasm_instructions.hh, line: 918, version: 2.32.16, options: -lang wasm-ib -es 1 -single -ftz

Re: [Faudiostream-users] lufs loudness analyser

Dear Julius, thanks for putting it nicely. :) I'm not sure I understand what you mean by allocating a delay line for the sliding mean, but I'll look into it. A quick improvement to the slidingMean function could be to put the integrator after the difference. With a sliding window of .4 sec at 48