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
53
Support - (fb2k) / Library rescanning like 5x slower
Last post by Squeller -
Hi,

have there been remarkable changes in the latest betas when it comes to media library full rescan? My ~4 TB collection which is on a 6 TB hard disk (not ssd) usually took ~5 minutes for full rescan. Now I observe it's 30+ minutes recently. Anyone else? Might as well be my rig, disk is full except for maybe 50 GB.

Thx
54
Other Lossy Codecs / Re: lossyWAV 1.4.2 Development (was 1.5.0)
Last post by C.R.Helmrich -
Thanks a lot! By the way, I didn't know that I need to add -b 512 to the FLAC command line. This already makes a huge difference on the LossyWAVed Merzbow sample - it almost halves saves one third of the bitrate.

Update: I could confirm your finding that the feedback parameter causes quite some bitrate increase with the low-rate presets, and I've found two further samples causing quite some bitrate bloat with the feedback: velvet and especially applaud from IgorC's set, see this upload post. Maybe you can adapt the feedback parameter on-the-fly based on how noisy and/or spectrally smooth the frame signal is (noisy/smooth -> no feedback)?

Chris
55
General - (fb2k) / Playstation PSF Component - Mute/Isolate Audio Tracks?
Last post by falconmoogle -
Hi all,
Does anyone know if there's a component for Foobar2000 that allows us to mute individual tracks within a PSF file?

My Game Boy/SNES/NES components all have that, but I can't go to GEP Control and mute tracks or change tempo when listening to PSF Playstation audio files.

Any help would be appreciated.

Thanks in advance
56
Other Lossy Codecs / Re: lossyWAV 1.4.2 Development (was 1.5.0)
Last post by Nick.C -
The original has a mightily impressive bitrate of 1,396kbps - which suggests that it is practically incompressible in terms of lossless reduction.

I processed the WAV with lossyWAV 143h at five quality settings: U, D, Q, A, and X and five scale settings; 1, 0.5, 0.25, 0.125, and 0.0625

Table of bitrates attached.
X

Noting the increasing bitrates as quality decreases I suspect that the new "auto-feedback" for quality settings below X (extraportable, -q -5) is being a bit too protective. With feedback set to zero the results are as follows:
X

There are some quite significant drops in resultant FLAC bitrate for the --scale 0.5 output compared to full scale - which leads me to think that clipping is stopping bitdepth reduction to an extent (which seems hardly surprising given that the clip more resembles static than music).

I'll have another pass at the auto-feedback settings for quality settings below -5 - thanks for bringing this sample to my attention as it has uncovered a need for a bit of tuning (at least).
57
General - (fb2k) / Re: Converter - RG - Gain is transferred but peak is not
Last post by Defender -
Quote from: Case on
Gain copying is allowed and in theory the gain should remain the same for transparent encode, it is supposed to sound identical after all. Of course in practice the values can differ a little since no loudness or hearing estimation model is perfect.

But peak isn't copied for lossy targets because it could be criminally incorrect. The only use for peak is to potentially use it in clipping prevention, and if it can be several decibels off it serves absolutely no purpose.

My recommendation would be to change the RG copying to RG scanning in the options. You lose nothing and gain right values. The copying is a valid option for lossless encoding but never for lossy.
I understand that it would be better to enable the post conversion automatic RG scan in the converter setup.

The issue is however that all tags of the source are transferred (as they should). This includes the TPS tags. My skin will flag the converted files therefore as erroneous.
Which means I have to run a non-automatic TPS scan anyway. And if I have to run a non-automatic TPS scan, it makes no sense to enable the automatic RG scan upon converting.

Is there a way to enable an automatic TPS scan (instead of an automatic RG scan) upon converting?
Is there a way to transfer all tags except TPS tags upon converting? In that case I can at least easily see something extra (a non-automatic TPS scan) needs to be done.

It is not that I'm lazy but I like my tools to be efficient and idiot (me) proof.
58
General - (fb2k) / Re: Converter - RG - Gain is transferred but peak is not
Last post by Case -
Gain copying is allowed and in theory the gain should remain the same for transparent encode, it is supposed to sound identical after all. Of course in practice the values can differ a little since no loudness or hearing estimation model is perfect.

But peak isn't copied for lossy targets because it could be criminally incorrect. The only use for peak is to potentially use it in clipping prevention, and if it can be several decibels off it serves absolutely no purpose.

My recommendation would be to change the RG copying to RG scanning in the options. You lose nothing and gain right values. The copying is a valid option for lossless encoding but never for lossy.
59
General - (fb2k) / Converter - RG - Gain is transferred but peak is not
Last post by Defender -
fooBar 2.24.5 32bit

I have set up to transfer metadata (tags), replaygain info and attached pictures.

Everything converts fine from flac to mp3, and replaygain gain info is copied, but for one reason or another the replaygain peak info is not copied.

In the screenshot is the converter setup, properties of the source (including peak) and properties of the converted mp3 without peak info.

After running a TruePeak scan on the destination files I noticed a slightly different peak is found and that could explain why peak info was not copied in the first place, but this new scan also results in slightly different gain values and those were originally transferred.

So why does 'transfer replaygain values' only transfer gain values and not peak values?
How can I get the converter to transfer the peak info of the source to the destination files as well?

NB. Reason I am asking is because I don't want to rerun RG or TPS scan every time after converting an album and I am more than happy to accept the slightly off values for gain and peak in the mp3 destination files.

EDIT: Until now I have been using dbPoweramp to convert FLAC to MP3, and dBPoweramp is set to copy all tags and does copy RG Gain and Peak values.
60
General - (fb2k) / Re: Converter - Output folder automatic creation?
Last post by Defender -
Quote from: Case on
The output directory selection is static, it doesn't do titleformatting. You put E:\Converted in it.
You specify further directory structure and naming pattern in the lower name format field.
Yeah, found that out myself as well.

E:\Converted\$directory(%path%) as output folder in converter setup literally creates the output folder:
'E:\Converted\$directory(%path%)'

Weird that this field is static.

I will put the code for the folder in the file name pattern instead.

EDIT: All good. Thx.