On 30/03/14 23:18, Timothy Gu wrote:
> On Mar 30, 2014 11:31 AM, "Luca Barbato" <[email protected]> wrote:
>>
>> On 30/03/14 19:23, Vittorio Giovara wrote:
>>> From: Timothy Gu <[email protected]>
>>>
>>> Signed-off-by: Vittorio Giovara <[email protected]>
>>> ---
>>>  doc/encoders.texi | 45 +++++++++++++++++++++++++++++++++++++++++++++
>>>  1 file changed, 45 insertions(+)
>>>
>>> diff --git a/doc/encoders.texi b/doc/encoders.texi
>>> index eccc9c6..bbd8b87 100644
>>> --- a/doc/encoders.texi
>>> +++ b/doc/encoders.texi
>>> @@ -25,6 +25,50 @@ enabled encoders.
>>>  A description of some of the currently available audio encoders
>>>  follows.
>>>
>>> +@anchor{aacenc}
>>> +@section aac
>>> +
>>> +Advanced Audio Coding (AAC) encoder.
>>> +
>>> +This encoder is an experimental Libav-native AAC encoder. Currently
> only the
>>> +low complexity (AAC-LC) profile is supported. To use this encoder, you
> must set
>>> +@option{strict} option to @samp{experimental} or lower.
>>> +
>>> +As this encoder is experimental, unexpected behavior may exist from
> time to
>>> +time. For a more stable AAC encoder, see @ref{libvo-aacenc}. However,
> be warned
>>> +that it has a worse quality reported by some users.
>>
> 
>> Suggest fdk-aac instead.
> 
> libvo-aacenc is more free than fdk, and many distros don't build Libav with
> fdk because they use GPL.

I prefer positive statements than negative ones that might or might not
unfunded at a later time.

The message that should be delivered IMHO is:

- Do not use the native aac for anything serious (it has some FPE and
other horrid corner cases, no I did not have time to investigate and fix it)
- If you want quality use fdk.
- If you can't use fdk use vo.

>>> +@c Comment this out until somebody writes the respective documentation.
>>> +@c See also @ref{libfaac}, @ref{libaacplus}, and @ref{libfdk-aac-enc}.
>>
>> Check those references (and drop those not matching).
> 
> This is commented out, so how do you "check" the references?

aacplus isn't present and I doubt it is worth providing it.

lu
_______________________________________________
libav-devel mailing list
[email protected]
https://lists.libav.org/mailman/listinfo/libav-devel

Reply via email to