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
3rd Party Plugins - (fb2k) / Re: [REQUEST USER-COMPONENT] foo_fanart
Last post by TT -
Anyway TT has convinced me that I should probably get off my lazy ass and just do this so once I finish off georgia-http for http-control (which is coming along AMAZINGLY so far) I'll probably try and knock it out and then let TT add something similar to Reborn.

I'm eagerly waiting for your stuff man... can't wait! It's also good to hear that some ass-kicking helps,
actually I did that on purpose to revamp your motivation and I'm not sorry at all :))

- TT

Other Lossy Codecs / Re: Quite OK Audio (QOA)... anyone ?
Last post by Kamedo2 -
Possible improvements include:
  • Adding noise shaping
  • Use vector quantization, like E8 lattice, or PVQ to minimize the average root-mean-square error.
  • Use QMF (Quadrature mirror filter) to split the input into subbands, and encode each subbands separately, like aptx do.
General - (fb2k) / Re: foobar2000 v2.0 bugs
Last post by Porcus -
fb2k 1.x operates with 32-bit float internally, and so it cannot do 32-bit integer in a lossless manner.

Version 2 is still at beta stage, so I'd be patient. It can verify 32-bit integer FLAC files, but I have no idea what it can output.
(For DACing it doesn't matter, there is still nothing that can deliver the 25th bit, had it even been audible. There is a chip that boasts 140 dB dynamic range (in mono only!) - but in real measured environments it doesn't fully hit 20 bits: )
MP3 - Tech / Re: LAME compiled executable slow!
Last post by 145dBSPL -
Using -march=native usually is most advantageous when just running on the compiling machine.

Current CPU's support a lot of "special" instructions/instruction sets older ones do not.
The differences between AMD/Intel architectures not to forget. So, using -march=native is
kind of a gamble if the binary should run across several different platforms.

The lowest common denominator would rather be -march=x86-64(-v2|-v3|-v4), depending on the target system.
Or you might choose the -mtune settings. The GCC manual details the different options.

For personal purposes, i also compiled the Lame binary for several years now. Aim was always to get
the fastest binary possible, that runs on every CPU - let's say - of the past decade. I also use GCC,
as it provides a solid performance and does not favor Intel over AMD as the ICL did (at least until last year).
It is even able to outperform ICL and MSVC builds speedwise, according to my experience and tests.