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
35
foobar2000 mobile / Re: Cannot play m4a files after 1.4 update on Andriod
Last post by Peter -
Playlists disappeared or are their contents unplayable?
Either way, fix is being worked on so you don't have to do re-add folders / your playlists keep working; will be released today.

Still, there are pretty horrible performance issues with folders added in the old version and re-adding them is *strongly* recommended.

Unfortunately there's just no easy way to fix playlists referencing old locations, so I'm re-enabling relevant code to keep playlists made with past versions working.
39
FLAC / Re: Is there an online database to check the checksum of tracks?
Last post by Porcus -
Quote from: miwcbimaqs on
That's the problem. Shouldn't the md5 be the same for everyone since it's "lossless"?... I can't understand it.
Different masterings are different, sometimes audibly so.
If one was mastered for CD and another for file delivery, they need not have same length.
And even if same mastering, only different CD pressings: Depending on which device created the master it was pressed from, they might differ in so-called offset: one pressing may have every track boundary say thirty or a hundred samples to the left or to the right of another one.
Same mastering, same pressing, different ripping tool: Drives also have different read offsets and if that isn't corrected upon ripping, you will get bitstream shifted. That is even if there was no ripping error.