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.
Last post by Peter -
Since the problem is in lookup tables, not in code, any software still suffering from this can be trivially binary-patched: Open the program - or avcodec binary that it uses - in a hex editor, find: 12 16 1A 20 26 2E 34 40 There should be just one occurrence of it. Replace with: 12 16 1A 20 26 2E 36 3E (just two last bytes of the chain changed)
Last post by .halverhahn -
OMG... hopefully Cisco, Juniper, Extreme, HP, Huawei, IBM, Broadcom, PaloAlto, Brocade... etc. realize how bad their products are and get some professional advice from UpTone.
Last post by Peter -
MPEG-2 layer 3 glitch has been fixed for upcoming 1.x refresh, thanks for bringing this up.
In foobar2000 prior to 2.0, only formats decoded thru FFmpeg are: MP3, Vorbis, AAC, ALAC Bugs in FFmpeg not affecting these are not relevant. libavformat is entirely disabled, libavcodec packet decoding is used only. (Vorbis decoding was moved back to libvorbis in 2.x series)
Last post by Peter -
I know many of you have been wondering why Mac foobar2000 is essentially 0.5 versions ahead of Windows.
The long explanation is that initial port was based on an early foobar2000 v2.0 prototype from 10 years ago, hence named 2.0, even though it was eseentially foobar2000 mobile codebase. This was foobar2000 for Mac up to version 2.3.
Windows foobar2000 v2.0 was entirely rebooted later starting from 1.x source. Given choice between releasing another foobar2000 v2.0 for Mac or using different versioning on Mac/Windows, I opted for the latter and released proper foobar2000 v2.0 for Mac as v2.5.