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
1
3rd Party Plugins - (fb2k) / Re: foo_truepeak True Peak Scanner
Last post by Defender -
Quote from: ngs428 on
Quote from: Defender on
You enabled SoX for foobar standard RG scanner.
You don't have to enable SoX resampler for Truepeak. When SoX is installed Truepeak will automatically use SoX upon scan.

If you use the settings as in the attached file, you don't have to use standard foobar replaygain scan anymore. Upon scanning truepeak will write TP values also in the standard RG fields and will also calculate LRA, DR and clipping positions.
So in one scan you can have it all.
If you don't want the result window popup, you can also disable it.

BTW. All this info is in this thread if you scroll a bit back.

Thanks for the guidance Defender. What is the benefit to writing to custom tags for peak and gain along with using the ReplayGain tag fields?  Both will have the same values, albeit a different tag name.  I was jus tusing the ReplayGain fields as shown in the attached. 

If you don't write the custom fields you don't know how the replaygain values were obtained (with the standard replayscanner for instance and if so whether upsampling was enabled). With upsampling results are more precise.
So in my skin I optionally can show RG values (and LRA, LUFS, PLR and Clipping) I display replaygain values with an indicator if they were obtained with the truepeakscanner (the values of the RG fields are the same as the custom fields in that case).

I show this info in 3 different optional locations: group header (album values), rowlevel (track values) and popup (both album & track values).
When I detect RG info is a result of a Truepeak scan I display TT instead of RG.

It all helps in giving me an idea about the quality of the recording and comparing recordings of the same track on different releases before listening to it.
2
3rd Party Plugins - (fb2k) / Re: Georgia-ReBORN - A Clean foobar2000 Theme
Last post by TT -
@Majestyk,

I do not get any script crash but I do get a foobar crash, don't know if it's the same you're reporting.
I can reproduce the foobar crash with fb.Exit();

Code: [Select]
		const checkResponse = setInterval(() => {
			try { xmlhttp.Status && xmlhttp.ResponseText } catch (e) { return; }
			clearTimeout(timer);
			clearInterval(checkResponse);
			bioOnStateChange.call(xmlhttp, resolve, reject, func);
			fb.Exit(); // Add this line here
		}, 30);

Can you confirm this?
3
3rd Party Plugins - (fb2k) / Re: foo_truepeak True Peak Scanner
Last post by ngs428 -
Quote from: Defender on
You enabled SoX for foobar standard RG scanner.
You don't have to enable SoX resampler for Truepeak. When SoX is installed Truepeak will automatically use SoX upon scan.

If you use the settings as in the attached file, you don't have to use standard foobar replaygain scan anymore. Upon scanning truepeak will write TP values also in the standard RG fields and will also calculate LRA, DR and clipping positions.
So in one scan you can have it all.
If you don't want the result window popup, you can also disable it.

BTW. All this info is in this thread if you scroll a bit back.

Thanks for the guidance Defender. What is the benefit to writing to custom tags for peak and gain along with using the ReplayGain tag fields?  Both will have the same values, albeit a different tag name.  I was jus tusing the ReplayGain fields as shown in the attached. 
4
3rd Party Plugins - (fb2k) / Re: foo_truepeak True Peak Scanner
Last post by Defender -
Quote from: ngs428 on
SoX did speed up scanning quite a bit.  Most values were the same, peak timestamp if different, along with track and album peak.  Is this to be expeced?  1st time using SoX for this so wanted to confirm.  Please see attached. 

I installed  https://foobar.hyv.fi/?view=foo_dsp_resampler
Then went to Preferences>Advanced>Filter, type in Tools, under Automatic resampling preference type in: “Resampler (SoX)”

Colsole info:
True Peak Scanning track: D:\Music\FLAC\P-R\_ and the Mysterians\1966 96 Tears\_ and the Mysterians - 96 Tears - 12 - 96 tears.flac
Oversampling to 352800 Hz with Resampler (SoX)
True Peaks calculated in: 0:01.346, speed: 133.61x

Anything I messed up here?  Don't think so, but checking... 

You enabled SoX for foobar standard RG scanner.
You don't have to enable SoX resampler for Truepeak. When SoX is installed Truepeak will automatically use SoX upon scan.

If you use the settings as in the attached file, you don't have to use standard foobar replaygain scan anymore. Upon scanning truepeak will write TP values also in the standard RG fields and will also calculate LRA, DR and clipping positions.
So in one scan you can have it all.
If you don't want the result window popup, you can also disable it.

BTW. All this info is in this thread if you scroll a bit back.
5
FLAC / Re: FLAC v1.4.x Performance Tests
Last post by Porcus -
Ah. So you have just improved a criterion of the following kind:
"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"?
7
3rd Party Plugins - (fb2k) / Re: foo_truepeak True Peak Scanner
Last post by ngs428 -
SoX did speed up scanning quite a bit.  Most values were the same, peak timestamp if different, along with track and album peak.  Is this to be expeced?  1st time using SoX for this so wanted to confirm.  Please see attached. 

I installed  https://foobar.hyv.fi/?view=foo_dsp_resampler
Then went to Preferences>Advanced>Filter, type in Tools, under Automatic resampling preference type in: “Resampler (SoX)”

Colsole info:
True Peak Scanning track: D:\Music\FLAC\P-R\_ and the Mysterians\1966 96 Tears\_ and the Mysterians - 96 Tears - 12 - 96 tears.flac
Oversampling to 352800 Hz with Resampler (SoX)
True Peaks calculated in: 0:01.346, speed: 133.61x

Anything I messed up here?  Don't think so, but checking... 
9
FLAC / Re: FLAC v1.4.x Performance Tests
Last post by ktf -
Quote from: Porcus on
I didn't quite get the change, but is it so that the code checks that the residual fits a signed short, and when it does ... much faster?

When adding the 32bit PCM part of the encoder, I've amended the FLAC spec to include that all residuals must fit a 32 bit signed int. This is to keep decoding simple. The encoder must make sure this is done.

It is possible to calculate that for certain predictors, checking each residual sample separately is not necessary. When this is not possible, each residual sample must be checked, which is slower of course. This calculation was improved, so the slow process of checking all residual samples is needed less often.

I didn't know at the time 24-bit encoding would be affected, but it turns out that for signals with very little noise in the upper frequencies (= smooth signal) the predictor can be of a very high quality, which can lead to the residual spiking for parts of the signal where the predictor doesn't fit. This doesn't normally happen, but it needs to be checked anyway.