Skip to main content


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
Support - (fb2k) / Re: RealTime error systematically
Last post by Majestyk -
On my Windows 10 system I get the same error, but only with your theme. I haven't got it with any others.

I'm also running foo_uie_vis_channel_spectrum.dll and I don't have any issues, but over the years I have noticed that this component does get falsely implicated in a crash.
Lossless / Other Codecs / Re: Open Source TAK encoder
Last post by mycroft -
You can send me decoder for 1.X version if you want. Real specifications are much better. So I do not need to reverse Pascal code.
Although it is just codec with FIR coefficients for LPC with custom entropy coder and decorrelation for stereo.
General Audio / Re: 32-bit floating-point (WAV) files "in the wild"
Last post by Porcus -
Googled up a few more files at soundcloud - and this time I checked file properties. Largest/longest first:
110 minutes track. That's > 2 GB.
"Made with REAL synthesizers & drum machines, which for a while seems to have diminished."
102 min in 31 tracks, not counting one 16-bit track.
This user (or bot?) has made a big number of playlists all with the same content (I think), just changing the name and the picture. Anyway, pick one playlist:
74 minutes of 32-bit float in 19 tracks. And about the same in 24-bit.
54 minutes, the second file is float.

A couple of single tracks:

... and the THX "Deep note" can be found if sought - who knows how much processing that has been through until someone uploaded it in float.
General Audio / Re: DAS: Which RAID Configuration to Minimize Bit Rot Error Risk?
Last post by fooball -
A good video I stumbled upon for anyone who comes across this topic.
Either he's missed the point or I have.  RAID was never for that.  RAID is the means to swap out a failed HDD with minimal or no interruption to service, and (as an afterthought) achieve higher read transfer rates by paralleling the read across the redundancy.  Bit rot was never in the mix, if that's even a "thing".

It will take a lot to persuade me bit rot is a "thing" when it comes to spinny disks.  There's a CRC for every sector, and if the CRC fails on read (or write verification) the read (or write) is retried and logged.  Unrecoverable errors fail the whole transfer, and do not just return a sector of data with individual bit errors.  The RAID then reports a failed disk and uses the redundancy to maintain data availability.

Where there could be bit errors is in the communications through the data paths, or bit-flips in SSDs.  I presume there is some kind of means of detection in SSDs (although I don't know for sure – I grew up with HDDs when the controller was a separate card!), but data paths commonly don't even have parity.  It's left to the OS to verify that data was delivered accurately.

Ditto a computer's RAM.  There was parity RAM at one time, but it was relatively expensive and now I don't think there is any validation on the data stored in RAM.  If a bit flips in data which is on its way to the HDD, it will be stored as if it were accurate (along with CRC etc) – the HDD has no way to know the data is in error, and neither does the RAID.  The RAID acts in good faith.

None of this amounts to a can of beans.  If it were a problem of any significance at all, the protections would be built in.  If there is a problem, it is in archival data where a write data error might not get noticed for years or decades (so it is essential to have a verify cycle when writing the archive), and the archive media may suffer from degradation (so it is essential to have multiple archives, and refresh the archives on a routine basis).

It's a lot of work, and a lot of cost.  Accumulate enough data, and you'll spend your whole time maintaining data.  The alternative is to just accept that once in a blue moon you'll lose a file, and unless you're under contract not to lose files it probably doesn't matter that much.
General - (fb2k) / Re: Editing tags in foobar
Last post by Air KEN -

After registering all 2000 albums to MEdia Library,
Media Library and some files were destroyed.

Remove the album in question and rebuild the Media Library.
The person asking the question also deleted the TAG using TagScanner.
It says that TagScanner also organizes TAGs.

Re-rip the problematic album.

I think that's one way.
General - (fb2k) / Re: Play Desktop Audio through Foobar
Last post by sacduser -
To use Recorder component you configure Recording Device in Preferences\Tools\Recorder. On the same page you see the recording command to use in 'add location'. In 'add location' you can enter a number of Foobar commands.