The LUFS Integrated figures all still tally very closely. I'm wondering if the way True Peak is measured changed in one of the updates?

On my installation I get the exact same results for both versions of the scanner.

My Foobar2000 derived True Peak figures used to to tally almost exactly with my other professional meters (RX9 Advanced, Youlean Loudness Meter, RME Digicheck etc.), but during one of the updates over the last couple of years (not exactly sure which one), they started to be further off than my other readings, always reading significantly higher. Not sure when it happened, or why, and sorry it's not very helpful for you, I'm just saying it's something I noticed and I would also like to know how to change it back to be more accurate with my other meters. The LUFS Integrated figures all still tally very closely. I'm wondering if the way True Peak is measured changed in one of the updates?

Does anybody know if there is an already compiled component for the R128 Scanner? I can't find it

Brand, what do you mean by that: True Peak results can vary a lot depending on the resampler settings. IDK if the defaults have changed over the years in f2k, because I've only recently started to pay attention.
But I think SoX with the default settings (linear phase, 95% passband, x4) is pretty close to most other True Peak scanners. I found that changing phase and passband settings has the biggest effect.??

Anyway, I ended up using the SoX resampler component for TP scanning, with linear phase and 95% passband. I compared the results with some other TP scanners outside of f2k and they were similar, so I guess they also use linear phase filters when oversampling.

ffmpeg can be used, I wrapped it on SPM to automatically tag files after analyzing, check Playlist Tools on my sig. Other tools/Write tags

There are also code samples to display LRA, LUFS and PLR there too at presets/UI

Due to this thread I recently switched back to the SoX Resampler and now everything is as it was before and the True Peak results tally with my other audio software.

I can easily see LUFS I, True Peak, and PLR per track, but does anyone have a string to display Loudness Range/LRA figures?

Thanks, but I meant without having to use a third party component like Spider Monkey, e.g.

PLR:
$puts(PLR,$if(%replaygain_track_peak_db%, $puts(PLR,$sub($mul($replace(%replaygain_track_peak_db%,.,),10),$sub($mul($replace(%replaygain_track_gain%,.,),-10),18000))) $puts(PLR_TEN,$left($right($get(PLR),3),2)) $puts(PLR_ROUND,$ifgreater($get(PLR_TEN),40,$add($get(PLR),100),$get(PLR)))$iflonger($get(PLR_ROUND),4,<$left($get(PLR_ROUND),2)<.$substr($get(PLR_ROUND),3,3),$left($get(PLR_ROUND),1)<.$substr($get(PLR_ROUND),2,2)),))$get(PLR)

LUFS Integrated:
$if(%replaygain_track_gain%,$puts(l,$sub(-1800,$replace(%replaygain_track_gain%,.,)))$div($get(l),100).$right($get(l),2) dB,)

Quote from: darkflame23 on 2022-04-12 06:41:30

Thanks, but I meant without having to use a third party component like Spider Monkey, e.g.

PLR:
$puts(PLR,$if(%replaygain_track_peak_db%, $puts(PLR,$sub($mul($replace(%replaygain_track_peak_db%,.,),10),$sub($mul($replace(%replaygain_track_gain%,.,),-10),18000))) $puts(PLR_TEN,$left($right($get(PLR),3),2)) $puts(PLR_ROUND,$ifgreater($get(PLR_TEN),40,$add($get(PLR),100),$get(PLR)))$iflonger($get(PLR_ROUND),4,<$left($get(PLR_ROUND),2)<.$substr($get(PLR_ROUND),3,3),$left($get(PLR_ROUND),1)<.$substr($get(PLR_ROUND),2,2)),))$get(PLR)

LUFS Integrated:
$if(%replaygain_track_gain%,$puts(l,$sub(-1800,$replace(%replaygain_track_gain%,.,)))$div($get(l),100).$right($get(l),2) dB,)

I know that code :-) But that gives me results who are to way off the results that I get from the other ones mentioned enough here ;-) because the RG Scanner seems to calculate the RG track gain in EBU R128 mode not correctly or in a different way as the other tools. That said the result of calculations based on the RG results can't be better..

REM Helper to execute ffmpeg.exe (%3) on input (%1) and save output to file (%2)
REM Retrieves LRA data as json
@ECHO OFF
%3 -i %1 -af loudnorm=dual_mono=true:print_format=json -nostats -f null -  2>&1 | > %2 FINDSTR /BIR "{ .*\" }"

Thanks regor! I've just discovered your great tools the other day and I'm trying to getting used to it. Since a day or two I get error warnings when I re-open foobar.

The LUFS I figures from that string correspond extremely closely to RX 9 Advanced, RME Digicheck, Youlean Loudness Meter, REAPER and Acon Acoustica, never off by more than a tenth of a dB, good enough for me!

It was the TP figures that were off for me, but fixed since going back to the SoX Resampler.

Quote from: skippertag on 2022-04-12 10:54:12

Quote from: darkflame23 on 2022-04-12 06:41:30

Thanks, but I meant without having to use a third party component like Spider Monkey, e.g.

PLR:
$puts(PLR,$if(%replaygain_track_peak_db%, $puts(PLR,$sub($mul($replace(%replaygain_track_peak_db%,.,),10),$sub($mul($replace(%replaygain_track_gain%,.,),-10),18000))) $puts(PLR_TEN,$left($right($get(PLR),3),2)) $puts(PLR_ROUND,$ifgreater($get(PLR_TEN),40,$add($get(PLR),100),$get(PLR)))$iflonger($get(PLR_ROUND),4,<$left($get(PLR_ROUND),2)<.$substr($get(PLR_ROUND),3,3),$left($get(PLR_ROUND),1)<.$substr($get(PLR_ROUND),2,2)),))$get(PLR)

LUFS Integrated:
$if(%replaygain_track_gain%,$puts(l,$sub(-1800,$replace(%replaygain_track_gain%,.,)))$div($get(l),100).$right($get(l),2) dB,)

I know that code :-) But that gives me results who are to way off the results that I get from the other ones mentioned enough here ;-) because the RG Scanner seems to calculate the RG track gain in EBU R128 mode not correctly or in a different way as the other tools. That said the result of calculations based on the RG results can't be better..

Theoretically if you can compute PLR and LUFS with ffmpeg (and sure you can) it would be trivial to add those tags to the list of tags to be calculated by my script. That's it... if you find ffmpeg being more accurate (?). I have to note that my RG results are pretty accurate too though (compared to audition, music bee, Izotope,... , so maybe there is an error on your config at some place (?).

This is an example of my batch file, which outputs LRA to a json file

Code: [Select]

REM Helper to execute ffmpeg.exe (%3) on input (%1) and save output to file (%2)
REM Retrieves LRA data as json
@ECHO OFF
%3 -i %1 -af loudnorm=dual_mono=true:print_format=json -nostats -f null -  2>&1 | > %2 FINDSTR /BIR "{ .*\" }"

If you manage to do the same for PLR and LUFS (it would be preferable to have both values calculated at once), I would gladly code the other part (menu entries, tagging, etc.).

Quote

Thanks regor! I've just discovered your great tools the other day and I'm trying to getting used to it. Since a day or two I get error warnings when I re-open foobar.

Error warning? Or slow script popup? The second is not a problem of my scripts but a SMP thing, you can configure SMP to adjust the time before warning at advanced config.

Quote from: skippertag on 2022-04-07 00:49:40

Does anybody know if there is an already compiled component for the R128 Scanner? I can't find it

ffmpeg can be used, I wrapped it on SPM to automatically tag files after analyzing, check Playlist Tools on my sig. Other tools/Write tags

There are also code samples to display LRA, LUFS and PLR there too at presets/UI

Theoretically if you can compute PLR and LUFS with ffmpeg (and sure you can) it would be trivial to add those tags to the list of tags to be calculated by my script. That's it... if you find ffmpeg being more accurate (?). I have to note that my RG results are pretty accurate too though (compared to audition, music bee, Izotope,... , so maybe there is an error on your config at some place (?).