Libavcodec AAC

From Hydrogenaudio Knowledgebase
Revision as of 19:02, 2 July 2016 by Bp (Talk | contribs)

Jump to: navigation, search
Current AAC encoders
(most to least recommended)
1 Apple AAC M/W
2 FhG AAC (Winamp) W
3 Fraunhofer FDK AAC S/L/M/W
4 Nero AAC L/W
5 FFmpeg 3.0+ AAC encoder S/L/M/W
6 FAAC S/L/M/W
7 Libav (pre-3.0 FFmpeg) AAC encoder S/L/M/W
S Source code available; L Linux; M macOS; W Windows
List of AAC encoders

The multi-codec library, libavcodec, includes an AAC encoder and decoder. The library was created as part of FFmpeg, and forked with Libav. Both projects maintain a separate version of libavcodec.

The original native AAC encoder was written by Konstantin Shishkov, and released under version 2.1 of the LGPL. It was considered experimental and poor quality compared to non-free/commercial encoders, but at least free. For GSoC 2015, Claudio Freire and Rostislav Pehlivanova did a significant amount of work on the AAC encoder that would be included in FFmpeg 3.0 (February 2016), and FFmpeg has declared this encoder stable (at least for CBR) and ready for common use. Libav has not merged this new work, and continues to use the original experimental encoder.

Alternatives

The FFmpeg/Libav frameworks can also use other encoding libraries, if they are available.

  • Fraunhofer FDK AAC, via libfdk-aac. Both frameworks recommend using this encoder if it is available, but it is non-free.
  • FAAC, via libfaac.
  • libvo-aacennc, the very poor VisualOn AAC encoder. (support removed in FFmpeg 3.0)
  • libaacplus, the very old Coding Technologies HE-AAC[v2] encoder. (support removed in FFmpeg 3.0)

Issues

Gapless decoding support

See Gapless playback for more on the general topic.

AAC encoding groups samples into frames of 512/1024/2048 samples. There may be padding of extra samples at the start, due to encoder delay, or at the end if there less than the exact number or samples needed to fill a frame. These extra samples will be decoded as additional silence if they are not trimmed. AAC provides no way to signal how many samples need to be trimmed, so this information is stored in the container, likely in the mp4 iTunSMPB atom.

  • FFmpeg's decoder will trim from the beginning, but not the end
  • Libav's decoder will not trim at all

External links