Re: [codec] Planning of further codec testing

I seem to remember that Jan Skoglund also attempted -- without success
-- to get access to AAC-LD for the previous Google test. Might still be
worth trying, but I wouldn't count on getting access to it.

	Jean-Marc

On 11-08-05 11:40 AM, Anisse Taleb wrote:
> Dear Christian, Gregory
> 
> Just a suggestion....to get an AAC-LD or ELD (enhanced low delay),
> encoder and decoder you probably would like to get in touch with the
> folks in FhG IIS (Markus Schnell or Ralf Geiger). I am not sure they
> would be willing to provide you with a complete suite of encoder and
> decoder, however, they could encode the items for you if you provide
> them with the input wavefiles...It's worth a shot.
> 
> I am personally skeptical to using the workaround suggested by
> Gregory, the encoder and decoder may be subject to some obscure EULA
> and it is not clear what delay this implementation has and the
> reported limited set of bitrates and actual quality. It is however a
> good fallback if FhG is unwilling to help with this.
> 
> Kind regards, /Anisse ________________________________________ From:
> codec-bounces@ietf.org [codec-bounces@ietf.org] on behalf of Gregory
> Maxwell [gmaxwell@juniper.net] Sent: 05 August 2011 16:26 To:
> Christian Hoene; codec@ietf.org Subject: Re: [codec] Planning of
> further codec testing
> 
> Christian Hoene [christianhoene@googlemail.com] wrote:
>> Does anybody know how to get an AAC-LD encoder and decoder?
> 
> I was hoping someone would provide a better answer:
> 
> There is an implementation of an AAC-LD encoder and decoder included
> with Apple computers.  People with quicktime pro installed are able
> to select it and write AAC-LD to mp4 files and decode from them to
> wav.
> 
> As I recall the encoder's selection is some limited in terms of 
> supported sample/bitrates, and doesn't present pretty much any
> options, I seem to recall it using the larger of the supported frame
> sizes, and also having extensive bitres usage (not really hard CBR).
> "Take it or leave it".
> 
> If you use it you will want to be careful to check to see the the
> files it wrote were what you wanted and not some other codec.
> 
> I'm also not sure if it's a particularly good implementation or not,
> but it seemed to work okay.
> 
> 
> _______________________________________________ codec mailing list 
> codec@ietf.org https://www.ietf.org/mailman/listinfo/codec 
> _______________________________________________ codec mailing list 
> codec@ietf.org https://www.ietf.org/mailman/listinfo/codec
> 
>