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
Validated News / Re: Server Moved
Last post by spoon -
Just ran various tests, from Germany (1000km from datacenter) the front page loads in 1 second, the hardware it runs on is identical.
FLAC / Re: FLAC v1.4.x Performance Tests
Last post by Porcus -
Can anyone try to replicate the following observation, using their fave build and CPU?

Prediction order (the "-l" switch) makes for big time penalty somewhere above -l12.

Being --lax settings, they may have gone under everyone's radar for good reason. But the impact is unexpectedly big here, see plot below.

Here is what I did, using the "timer64" tool - but PowerShell wizards can probably come up with something built-in (and *n*x users, you likely know what to do):
for /l %l IN (6,1,32) DO timer64 flac --lax -fr0 -ss -l %l filename*.flac >> logfile.txt
for /l %l IN (6,1,32) DO timer64 flac --lax -fpr0 -ss -l %l filename*.flac >> logfile.txt
... re-encoding yes (that's the -f), so in principle that means every successive encode has to read a more complicated FLAC file, but (1) FLAC decodes so quick it shouldn't matter, and (2) anyway a jump would be a surprise. The "-r0" to ensure that the partitioning is done the same for every run.

Timings on a quick run on one album (Swordfishtrombones) - this fanless computer is cooling constrained and timings have shown to be quite unreliable, but I ran  -l15 and -l16 (indicated in the oval) several times on several files and that particular jump is quite consistent. For -p, the impact is more dramatic already at -l 13.
foobar2000 mobile / Library indexing errors with android
Last post by Grobb284 -
Recently having multiple indexing errors when scanning the library, "status: object not found."
Changed to different thumb drives, same result.
Reinstalled Foobar2000 for Android, same result.
Unsure what is the problem and solution?
Validated News / Server Moved
Last post by spoon -
We have moved to a new datacenter today (the 8 hour downtime), all should be working now, except anything which is not port 80 or 443, will fix that shortly. Post here please if anything does not look right.