11
3rd Party Plugins - (fb2k) / Re: Dynamic Range plugin
Last post by Henry66 -After running DR Meter on an album, I see this:
Would it be possible to get all this data written to tags or to a log file (or both)?
Ah. So you have just improved a criterion of the following kind:Yes, that is correct.
"This predictor vector cannot possibly create any too big residual from a history of N-bit samples, so we can save time by bypassing the size checks that we are mathematically sure it would anyway pass"?
As far as I'm concerned, those builds should be plenty fine and can be called "stable".
There are further patches on the dev branch (Case's reworked progress printing, improved help messages, some safeguards against negative array indices in the encoder math), but nothing that invalidates the current builds.
edit: For those wondering why the dev branch isn't yet merged to the main/stable branch: I'm still trying to figure out why *downsampling* doesn't appear to work (in either main or dev). For instance, when requesting downsampling a 44.1 kHz input file to 32 kHz (hmp3 -A32000 test.wav test.mp3), the encoder goes haywire and crashes/segfaults. That's because when computing some array indices in l3math.c, the indices can get negative (the dev-branch guards against those negative array indices). However, that's most likely because the encoder is fed invalid audio data (with the negative-indices guards in place, I get silent mp3 files) and I haven't properly investigated out what's going on there.
Would also be nice to have an easy way to show LUFS Integrated and Max LUFS M and Max LUFS S for each track.Here's an unpublished True Peak Scanner version with max momentary loudness (LUFS-M) and max short-term loudness (LUFS-S) scanning support: https://foobar.hyv.fi/foo_truepeak_0.6.8.fb2k-component.
At the moment the component defaults to storing LUFS-M in a tag field "truepeak_scanner_max_lufs_m" and LUFS-S respectively in "truepeak_scanner_max_lufs_s". If there are tag fields already in use by some software I'd happily change to use the same fields.
LUFS-I is computable from the ReplayGain value, but if there's strong will for yet another option, it could be stored in a separate tag field.