Posted by
michael
on from the tastes-great-less-filling dept.
Logic writes "The Oggbitstream format (used by OggVorbis) has been enshrined in RFC 3533, "The Ogg Encapsulation Format Version 0", for all you folks who won't look at something unless it has an RFC attached to it."
Remember what an RFC is
by
bigberk
·
· Score: 5, Informative
An RFC is a "Request For Comment", a technical specification document put forward by anybody. As wikipedia puts it, "Few RFCs are standards but all Internet standards are recorded in RFCs."
So what am I getting at is, realize that this hasn't been adopted as some Internet standard overnight. But it's very positive for the project to have such a well defined standards document in a familiar format!
Re:Hopefully
by
bobm17ch
·
· Score: 5, Informative
I`m afraid this won`t affect player support much.
The device (pc/mp3player/whatever) still has to support the vorbis audio codec within the ogg wrapper.
Think of ogg as a bag of revels. The bag is standardised and easy to manipulate, but you just don`t know what you`re gonna get inside. Or even if you are gonna be able to handle it:) [1]
[1] I can`t decode the orange revels. My codec empties the contents of the buffer through the I/O.:p
--
\\ Mitch
Re:Now if only it had a decent name
by
be-fan
·
· Score: 5, Informative
Well, technically, the codec is Vorbis, which is a pretty cool name, if you ask me.
-- A deep unwavering belief is a sure sign you're missing something...
Actually, Tremor, the integer codec, took care of that over a ago according to the changelog. And it's released under a bsd-like license.
Unfortunately Tremor isn't a one-size-fits-all. It's got nasty things like dynamic memory allocation all over the shop and still a rather large memory overhead. Actually, to be 100% compliant with the Vorbis 1.0 spec it's rather difficult to turn out a fast and small implementation (I've been trying).
At the moment I'm working on getting my own implementation working with an extremely small RAM overhead. It's by no means trivial getting it working on the DSPs you find in most MP3 players, and almost none of the source code to Tremor could be successfully ported to them either. I don't expect any of the source code I'm writing for my own implementation to be used as anything but a reference for writing a version to run on DSPs.
Of course, it would have been much more difficult even starting to write my own implementation were it not for freely available specs.
Slashdot Mirror
An RFC is a "Request For Comment", a technical specification document put forward by anybody. As wikipedia puts it, "Few RFCs are standards but all Internet standards are recorded in RFCs."
So what am I getting at is, realize that this hasn't been adopted as some Internet standard overnight. But it's very positive for the project to have such a well defined standards document in a familiar format!
I`m afraid this won`t affect player support much. The device (pc/mp3player/whatever) still has to support the vorbis audio codec within the ogg wrapper. Think of ogg as a bag of revels. The bag is standardised and easy to manipulate, but you just don`t know what you`re gonna get inside. Or even if you are gonna be able to handle it :) [1]
[1] I can`t decode the orange revels. My codec empties the contents of the buffer through the I/O. :p
\\ Mitch
Well, technically, the codec is Vorbis, which is a pretty cool name, if you ask me.
A deep unwavering belief is a sure sign you're missing something...
Unfortunately Tremor isn't a one-size-fits-all. It's got nasty things like dynamic memory allocation all over the shop and still a rather large memory overhead. Actually, to be 100% compliant with the Vorbis 1.0 spec it's rather difficult to turn out a fast and small implementation (I've been trying).
At the moment I'm working on getting my own implementation working with an extremely small RAM overhead. It's by no means trivial getting it working on the DSPs you find in most MP3 players, and almost none of the source code to Tremor could be successfully ported to them either. I don't expect any of the source code I'm writing for my own implementation to be used as anything but a reference for writing a version to run on DSPs.
Of course, it would have been much more difficult even starting to write my own implementation were it not for freely available specs.