QUOTE(Busemann @ Jan 9 2005, 08:48 AM)
So what evidence do you base it on that you need 224kbps to achieve api/ape type quality, except your own brand of common knowledge
did you even read my post? It says it right there...also, it would be interesting to know what bitrate you suggest...if there are less samples failing at AAC 192kbps than on --preset insane, AAC 192kbps would be the answer...however, if a bit more samples fail on AAC 192, the answer would be AAC 224kbps...as I said, AAC 224kbps is better than --preset insane, but there's no AAC 210kbps or something...
An interesting quote from Garf, who is one of Ahead's AAC developers:
QUOTE(Garf @ Nov 13 2004, 02:26 PM)
Such a test is extremely difficult. One can generally find clips that are not transparent at 160kbps without too much problems, so 170-200kbps is a good guess. This is assuming a good encoder (Nero or iTunes).
Edit: You might not believe it, but I'm also looking forward to the release of a iTunes vbr AAC implementation and it's result compared to--preset standard