iPod May Not Have The Horsepower For Ogg [updated]
An anonymous reader writes "Gizmodo has an interview with a Rio engineer who speculates that current iPods may not have enough CPU power and/or memory to decode Ogg. He concludes that the Minis might be able to do it, and the next generation iPods will certainly be able to. Of course, just because Apple can doesn't mean it will." Update: 06/06 04:44 GMT by T : csm writes with this rebuttal: "According to Monty from Xiph.org (author of the Tremor codec and OGG itself), it should very well be possible to run Ogg on older generation iPods."
Not to be a smartass, but Ogg is just the name of the larger project. The actual audio compression format is called "Vorbis."
An engineer for a company in direct competition with Apple rips on Apple's hardware. Oh, he's speculating on it.
"Engineer Hugo Fiennes took a break from his day job as a hardware and firmware designer at Rio Audio (maker of the iPod competitor Karma player, among other things)"
That's news?
What's next, someone at Microsoft doesn't like Aqua? Ford engineer says Corvette "not as good as new Mustang"? Fiat engineers doesn't care for Ford Focus?
...a standard that doesn't have a lot of real-world support? I mean, if you go onto one of the p2p systems, you find that everything is still pretty much mp3. So there is some incentive there for Apple to provide mp3 support. Why would they want to promote an alternative standard that they aren't selling, though?
Seems to me that Apple wouldn't benefit much from ogg or flac support. So why bother - besides, the article makes it clear that the processor in the older ipods probably won't even support the decoding of ogg due to cpu limitations.
Barking up the wrong tree here, sadly. Ogg has to get some critical mass before Apple would even consider it.
HBI's Law: Frequency of calling others Nazis is directly correlated with the likelihood of the accuser being Communist.
This article indicates precisely why OGG Vorbis probably isn't a good idea on your ipod or mp3 player... namely, you get 25% LESS battery life. In a non portable, that's fine, but for a portable player with limited battery life... why in the world would anyone choose to get 75% performance with a negligable increase in sound quality (from headphones)?
Vorbis is a better codec at sticking more audio data in less space due to the years of research between itself and MPEG-1. But decoding that data doesn't come for free, and so Vorbis decoding is more memory and CPU intensive than mp3 is. But thanks to the integer decoder, that difference mainly shows up in high bitrate Vorbis files.
Ita erat quando hic adveni.
AAC and MP3 do not have DRM either.. the DRM layer was added for the iTunes music STORE, which is a recent addition.... people bought ipods LONG before the iTMS existed.....
Why do people insist on thinking that ipods and itunes are all just about the store? The majority of ipod owners DONT use the store.
Seriously, who cares about Vorbis outside the faction of *nix users with +1 Amulets of OSS Awe?
Apple's primary market are the throngs of not-quite-but-almost-technologically-literate end users out there who see gadgets as tools, not lifestyles. Does this afforementioned throng care about Vorbis? No. Should Apple therefore care about Vorbis? No.
Get the fuck over it, already.
John Klos
Running Amigas for more than a decade.
okay, i will refute the guy's arguments. i am an embedded systems developer, and often deal with swapping code in from dram/flash to sram for quick execution just such as this. the guy's arguments are, well...
first, the cache is not broken. this is a common design limitation of embedded processors. running code or accessing data from external ram can be VERY slow (1 cycle delay is pretty good). however, his argument is bullshit. the support code for the codec is usually run from dram (like the "open a file, parse a bitstream part"). the core decoder loop, on the other hand, is loaded into sram for fast execution (code and data). if the ogg vorbis decoder can be squeezed into whatever apple has left of the 96kb depends mostly on the efficiency of apple's memory allocation. but i have no doubt that they could do it (they may need to optimize some tables out by computing them at runtime, and other such tricks).
having said that... adding a complex codec into such a system such as the ipod firmware is a major pain in the ass. they may want to enable vorbis support, but it is a large amount of work, and probably hard for apple engineers to justify. if someone could find a good excuse for apple marketing to justify it, i'm sure engineering could figure it out.