On Wed, Jun 25, 2003 at 12:12:41PM +0200, Menno wrote:
> Crap!
> 
> > Actually, I'd hold off on that one for a while still. As I'm 
> > informed, the MPEG-4 audio standard isn't 100% set yet, and 
> 
> The AAC standard has been set since 1997.
> Who informed you?

AAC+SBR has been around since 1997!?  OK, didn't think so :-)

Both AAC and Vorbis continue to evolve.  Both have revved spec in
recent years.  You can claim AAC has been around since 1997, but the
spiffy low bitrate AAC stuff available today would not decode on an
original 1997 AAC decoder any more than a spiffy low-bitrate Vorbis would
decode on a 1997 Ogg decoder.

> Try the HE AAC codec that Ahead will release on July 18th, it kicks Vorbis
> ass at low bitrates.
> 
> http://www.hydrogenaudio.org/index.php?act=ST&f=2&t=10530

Mmm, and the current state of affairs will persist forever, no? :-)

I've reviewed this encoder and at 64kbps, it does indeed sound better
than current Vorbis (Vorbis still wins at higher rates).  No beating
around the bush there.  That said, it wasn't as good as I was
expecting; I thought Vorbis would have to go through the next planned
spec rev to catch up, but after hearing AAC+SBR, I believe it's a
matter of tuning in a minor release.  Next major Vorbis rev (V II)
will just have to be content at making it embarrassing is all ;-)

The tech edge goes back and forth; Vorbis has held it over AAC for the
past few years.  AAC has now leapfrogged.. well, at low bitrate
anyway. AAC is still unspectacular without SBR.  Vorbis will leapfrog at
low bitrate again and I'll try to keep our fanboys from getting too
out of hand when that happens.  But make no mistake; Vorbis is taking
AAC and MPEG head on, and we're in this race for the long haul.

> The MPEG-4 file format supports multiple tracks as well. Next to that AAC
> has proper multichannel support.

Rebutted this dig in a seperate mail.

Monty
_______________________________________________
mp3encoder mailing list
[EMAIL PROTECTED]
http://minnie.tuhs.org/mailman/listinfo/mp3encoder

Reply via email to