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) / Truepeak Scanner
Last post by Defender -
@Case

Thanks for this tool.

Can you make a small adjustment in the "Scan true-peaks and positions (as albums)" so that it writes the total amount of clipped samples found in tracks in a field like TRUEPEAK_SCANNER_CLIPPED_SAMPLES_ALBUM?

I'd like to be able to show this value in the group header per album.
5
Support - (fb2k) / Preview Builds 2.2 not scanning
Last post by Crocodile11 -
Windows 11 (23H2)
Foobar2000 2.2 (20240327)

I dont know when this issue started, as I just have been upgrading over what I had installed. But today I fresh installed preview 2.2. I cannot get it to scan my external USB drive. It says monitoring all the time. Tried numerous times. I installed a fresh install of 2.1.3 to see if it was on my end, but that scanned straight away. Using x86
8
3rd Party Plugins - (fb2k) / Re: foo_vis_spectrum_analyzer
Last post by pqyt -
I noticed the "regression" on how low frequencies look (what I meant is the sinc-interpolation on bass frequencies (assuming log frequency scale) is now improper unlike this, which is proper and matches zero-padded FFTs) becomes obvious with spectrogram display as "artifacts" on lower frequencies that doesn't appear in fb2k's built-in spectrogram even with the same window function (Gaussian window with parameter of 2.4)
Spectogram uses exactly the same code as the bars and curve visualization. Between the preview and now nothing has changed. Just polishing and optimization. Please provide more details about what you think is wrong.
9
Listening Tests / Re: Great killer sample, easy to ABX on most codecs
Last post by Kraeved -
@Kraeved with all due respect I have been on this forum for 2 decades, I know and used lame3995o.

Dear @shadowking, it seems my words were open to misconstruction. Speaking of less informed users, I didn't mean you personally, but those who read such in-depth forum threads without having our knowledge of codecs, after which they randomly apply the flags they encounter and then ask why they don't get the desired results. Since -q1 is different from -Q1, I felt it necessary to emphasize that. Also, it would be useful to know what upset you with the result of 3995o.
10
MP3 - General / Re: Resurrecting/Preserving the Helix MP3 encoder
Last post by maikmerten -
The Helix MP3 Encoder is using floating point arithmetic (and LAME does, too). It's perfectly expected that there are slight variations in output depending on compiler version, compiler flags and platform. Rearranging floating point operations (that should be mathematically equal) can result in small (and usually inconsequential) differences in floating point values.

I don't expect hmp3 to generate identical files for Visual Studio, GCC 10.x or GCC 13.x, let alone if different instruction sets are involved.

i586 uses the x87 instruction set for floating point.
i686 uses the SSE instructions for floating point.
The Visual Studio compiles with ASM use a mixture of x87 instructions and SSE.
The Win64 x86_64-builds can use SSE(2)
I think Case's builds were AVX-enabled.