gorman;410221 Wrote: > I wonder what's the reasoning behind keeping Vorbis native and > transcoding AAC. While I don't use AAC at all and use Vorbis for > portable needs... I don't doubt that the market would far prefer the > opposite solution. Some idle speculation: • Perhaps the AAC/AAC+ decoder would be far larger than the Ogg decoder, so there still wouldn't be space. • Ogg has issues in the amount of memory it uses, especially with lower than 64bit recordings. Perhaps this is the same with AAC/AAC+? and if that's the case, broken native support is going to cause more problems than no native support will. • Perhaps, even with a bug free codec in the firmware, there isn't enough processing power in the SB3/Receiver/Boom to run everything and decode AAC/AAC+ • There is also the time/cost factor in implementing this codec in the firmware. I think the Ogg codec was a fairly simple port as various decoders are readily available as it is. AAC/AAC+ might need extensive reworking from faad2 to make it compatible with the Ubicom processor. I believe it doesn't have a floating point unit, so only integer maths is available. This heavily restricts what a codec can do.
So as you can see, there are plenty of possible reasons why AAC/AAC+ and ALAC aren't included in the current lineup of players. Perhaps adding codecs to some future player will be trivial, and everything will be supported natively, who knows! :) -- funkstar ------------------------------------------------------------------------ funkstar's Profile: http://forums.slimdevices.com/member.php?userid=2335 View this thread: http://forums.slimdevices.com/showthread.php?t=19155 _______________________________________________ discuss mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/discuss
