Skip to main content ↑ ↓

Notice

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.
Recent Posts
4
3rd Party Plugins - (fb2k) / Re: foo_vis_spectrum_analyzer
Last post by TF3RDL -
Quote from: Azuriye on
Quote from: TF3RDL on
which is absent in this CodePen project and even older version of this component

Was there a reason to revert that change? As of now it looks odd to resize the window in such a way where all the bands are laid out without any gaps
Yes, but if @pqyt were to revert this change, its current behavior when comes to resizing and how bars are laid out should be added as an opt-in feature, which can please some users of old foo_musical_spectrum that wants a 64-bit foobar2000 right?
6
3rd Party Plugins - (fb2k) / Re: foo_truepeak True Peak Scanner
Last post by ngs428 -
Quote from: francesco on
Hi
May I ask only 2 questions ?

1) what could i do with all the information provided by the True Peak Scanner component ?
I mean should I use them with some normalization /replay gain or components or foobar features?

2) are there some old version avaible ? I liked the first version

I don't see any old versions available.  Not sure what you like better in those?  In the settings in the latest version you can turn on and off anything you want. 

There is a lot of info.  I have a post a few back which outlines some definitions for the scanned values.  The ones in bold below ar ethe ones I care about most and have added them as a column in my Foobar playlist.  I slightly revised it and pasted it here:

1.   Track and Album Peak- This is the common RG value. Very short-lived peaks in the audio.  Can be used to prevent gain adjustments from inducing clipping in the playback device.  True Peaks: Overshoots that can occur when the D/A converter is recreating the analog waveform, that don't normally show as peaks in the DAW. These become more likely the more something is smashed up near 0 dBFS and basically not going to happen if you aren't getting that close to 0.

2.   Track and Album Gain - This is the common RG value in dB.  ReplayGain-capable audio players use the replay gain metadata to automatically attenuate or amplify the signal on a per-track or per-album basis such that tracks or albums play at a similar loudness level
3.   Track and Album LRA - Loudness Range in Loudness Units (LU).  Measures the variation of loudness across a song or album.  LRA values can show whether a song has a continuously constant loudness (low LRA values) or a high variation between low and high level components (high LRA values).  A complex algorithm measures loudness, analyzes how it's distributed throughout a song, determines a song's dynamics properties, and represents that with a number. The lower the number, the less dynamics. (Note that this is not about dynamic range, but rather, musical dynamics.)
4.   Track and Album Max LUFS-M - Momentary (0.4 seconds) measurement, as opposed to "I" which is the whole song.  The shown values are the highest readings recorded inside the track. Currently values are checked every 100 ms.
5.   Track and Album Max LUFS-S - Short Term (3 seconds) measurement, as opposed to "I" which is the whole song.  The shown values are the highest readings recorded inside the track. Currently values are checked every 100 ms.
6.   Track and Album LUFS-I - Similar to RG.  Measures perceived loudness of the entire song.  The foobar2000's ReplayGain scanner in EBU mode has always calculated LUFS-I value, it is just converted into ReplayGain's format with a simple formula. Nothing has changed in ReplayGain or its behavior. I just added ability to show and tag this field for people who want to see it.
7.   Track and Album PLR – Peak to long-term Loudness Ratio (PLR) is the difference between a signal's maximum true-peak level and its program loudness level. It's a long-term measurement that provides an overall value for a song, album, or section of audio. PLR is also known as the crest factor and is often used to describe a track's dynamics. Larger the number the more dynamic the track is. 
8.   Track and Album DR - The distance in dB between the softest sound and the loudest sound.
9.   Track and Album Clipped Samples - Any sample value that is beyond digital full-scale.  One clipping sample means that only one channel clipped. If same spot clipped on all channels of a 384-channel recording, it would be shown as 384 clipped samples.  If your file has 1 clipping sample it means it has a single peak above digital full-scale and only on one channel.  Just knowing that samples clip doesn't yet tell how bad it is. Exceeding the full scale by 0.1 dB would not matter at all, but exceeding it by 3 dB could be a problem. 
10.   Peak Timestamp - Time in track which contains the highest peak value.
7
3rd Party Plugins - (fb2k) / Re: foo_truepeak True Peak Scanner
Last post by ngs428 -
Quote from: Just_Addict on
Boy, I see I have to do some major housekeeping in my compontents section, True Peak Meter looks great.
Got a question though... running FB2K 1.6.17 with True Peak Scanner 0.6.10
Was hoping I could use it to ditch DR Meter but looks like I'll need to hang on to that one a bit longer...
At first, I thought it had a problem with SACD releases (24bit/88.2kHz) as some columns stay empty.
But I get the same with a lot of my mp3's as well.  In the Status Column it says: "Failed to instantiate ReplayGain scanner". 
Likely as a result, the replay gain, LUFS-I and PLR columns are always empty.

Console says:
Error: failed to instantiate ReplayGain scanner.
Oversampling to 192000 (sometimes 220500) Hz with Resampler (RetroArch)

Default ReplayGain is configured to use RetroArch at 192000



First off, I would install this SoX resampler component. I see you are using RetroArch to oversample.  Sox is preferred.
https://foobar.hyv.fi/?view=foo_dsp_resampler

Then in Foobar go to File > Preferences > Advanced > Enter "True" in the filter and at the top, change the minimum peak sample rate to 352800.  Higher rate the more accurate the results.  Also you want have even multiples of yor sampling rate, so 88.2k*4 = 352800.

I just scanned a SACD release (24bit/88.2kHz) with my Foobar 2.1.5 64 bit and the latest True Peak Scanner 0.6.10.  Worked just fine....

Console stated:
True Peak Scanning track: D:\Music\FLAC HD\Davis, Miles\1959 Kind of Blue (SACD 2.0) (88.2kHz-24bit)\Miles Davis - Kind of Blue (SACD 2.0) (88.2kHz-24bit) - 01 - So What.flac
Oversampling to 352800 Hz with Resampler (SoX)

Maybe, like you said, you need to clean some components up too...  Good Luck!
8
3rd Party Plugins - (fb2k) / Re: foo_truepeak True Peak Scanner
Last post by Just_Addict -
Boy, I see I have to do some major housekeeping in my compontents section, True Peak Meter looks great.
Got a question though... running FB2K 1.6.17 with True Peak Scanner 0.6.10
Was hoping I could use it to ditch DR Meter but looks like I'll need to hang on to that one a bit longer...
At first, I thought it had a problem with SACD releases (24bit/88.2kHz) as some columns stay empty.
But I get the same with a lot of my mp3's as well.  In the Status Column it says: "Failed to instantiate ReplayGain scanner". 
Likely as a result, the replay gain, LUFS-I and PLR columns are always empty.

Console says:
Error: failed to instantiate ReplayGain scanner.
Oversampling to 192000 (sometimes 220500) Hz with Resampler (RetroArch)

Default ReplayGain is configured to use RetroArch at 192000