Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Just for my understanding. I removed the old version. Restarted foobar and installed the updated version. I still see the names I entered for LUFS-S/M which are: truepeak_scanner_max_lufs_s_track truepeak_scanner_max_lufs_m_track.
Can you confirm that your default names upon first time installation are: truepeak_scanner_track_max_lufs_s truepeak_scanner_track_max_lufs_m
Thx for looking into the speed/performance problem as well.
EDIT: Sorry, let me rephrase .. What are all default names for custom fields you provide upon first-time installation?
EDIT2: You just hit one of my major annoyance points in foobar ... the settings screen is not resizable and you have now more options than one small settings screen.
Is the Clip count based on the PCM sample value, or the True Peak reading? I am assuming the former, as I have scanned a number of albums showing TP levels of above digital zero, but the Clip shows zero too.
Clip count is calculated from the upsampled signal currently. Are you certain about clip count showing zero? That should not be possible.
Yes, using this string to display the Clip count in the playlist:
%truepeak_scanner_clipped_samples_track%
And this King Tubby CD is showing dBTP overs of up to +2.45dB on one track, but the Clip count is zero for every track.
Is the Clip count based on the PCM sample value, or the True Peak reading? I am assuming the former, as I have scanned a number of albums showing TP levels of above digital zero, but the Clip shows zero too.
Clip count is calculated from the upsampled signal currently. Are you certain about clip count showing zero? That should not be possible.
There's now an option to also include LUFS-I tags when ReplayGain scanning. Album variants of LUFS-M and LUFS-S tags are now also supported.
I too noticed that momentary and short-term loudness evaluation is very slow. First test version called the calculations after each processed audio chunk. Refreshed build runs the calculations approximately every 100 ms. Sadly the results change a bit depending on when the calculations are done. I will need to tweak this behavior still a bit, I don't like that the numbers change for bit-identical data depending on how many samples a decoder produces per decode pass.
There was also a stupid mistake with SoX upsampling setup that was found thanks to @ngs428's sharp eyes. SoX upsampling mistakenly didn't use the power-of-two resampling ratio that it was meant to. Processing speed is now a bit faster as this issue was fixed.
Last post by darkflame23 -
Is the Clip count based on the PCM sample value, or the True Peak reading? I am assuming the former, as I have scanned a number of albums showing TP levels of above digital zero, but the Clip shows zero too.
Last post by TT -
It is displayed in the Playlist Manager at the top bar of the Playlist, see screenshot. Just mouse hover over the top bar of the playlist and it will show.
On foobar startup when nothing is playing, it will automatically show the total length of all tracks, if you select multiple tracks it will calculate these lengths, and if you select all tracks CTRL + A it will display again the total length.