21
Other Lossy Codecs / Re: lossyWAV 1.4.2 Development (was 1.5.0)
Last post by Nick.C -@2012's results look much more like it.
Can confirm that 0.6.8 with only RG+DR+POS enabled performs on the same level as 0.6.7 with RG+DR+POS+LRA.Because scanning with 0.6.8 seemed a lot slower than scanning with 0.6.7 and I was wondering if that was because of the extra LUFS-M/S scanningLUFS-M / LUFS-S scanning seems to be the reason. I use the libebur128 library for LRA scanning and also for LUFS-M/S. Seems that the extra work required to split the incoming data at precise 100 ms chunks to be fed to the library also hurts LRA scanning speed.
[...]
Does this make any sense to you?
13,749,585 '01 Riot (Feat. Damian Jr. Gong Marley).lossy.flac'
11,713,235 '01 Riot (Feat. Damian Jr. Gong Marley).lossy.b512.flac'
15,951,686 '02 Entertainment 2.0 (Feat. Juicy J, 2 Chainz & Nicki Minaj).lossy.flac'
13,103,138 '02 Entertainment 2.0 (Feat. Juicy J, 2 Chainz & Nicki Minaj).lossy.b512.flac'
Someone needs a simples dynamic range meter, with the ability to record a log file. + truepeak does not show rms and peak
Because scanning with 0.6.8 seemed a lot slower than scanning with 0.6.7 and I was wondering if that was because of the extra LUFS-M/S scanningLUFS-M / LUFS-S scanning seems to be the reason. I use the libebur128 library for LRA scanning and also for LUFS-M/S. Seems that the extra work required to split the incoming data at precise 100 ms chunks to be fed to the library also hurts LRA scanning speed.
[...]
Does this make any sense to you?
After googling a lot it seems that for LUFS-I positive values and negative values are both used to talk about the same thing.That would be wrong, they are very much different things.
It seems as if %truepeak_scanner_track_lufs_i% only has negative values.For very loud tracks the LUFS-I will be positive. When ReplayGain gain shows -18.00 dB LUFS-I will be exactly 0 LUFS. For louder tracks the LUFS-I will be positive.
Is it correct to assume Truepeak Scanner never publishes positive values?
I'd like to be able to calculate PLR even as %replaygain_track_peak_db% is not available. So I would need something like %truepeak_scanner_track_peak_db% or a way to calculate this value based on the already available truepeak tags.I'm certain there are some titleformat monstrosities posted on these forums that estimate dB value from floating point numbers from the old days. In theory the component could expose a global titleformat string that calculates and exposes this, but I'm not liking the idea at all. It's better to tag things in RG tags and leave hacks out.
Is there a way to calculate this peak_db value from available truepeak tags?