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."
Now that it's an RFC...
by
Anonymous Coward
·
· Score: 5, Funny
It's only a matter of time before Verisign decides to patent it.
Now if only it had a decent name
by
Anonymous Coward
·
· Score: 5, Funny
"OGG is better" "what? We're talking about music, not whatever that is..." "OGG is about music. It's a file format, like MP3s, only better." "Okay, dude, I'm sorry, I just keep missing the first thing you're saying" "It's OGG. O - G - G." "Dude, that is the most retarded name I've ever heard of... let's play some halo on my x-boxe!!!"
Re:Now if only it had a decent name
by
Anonym1ty
·
· Score: 5, Funny
Until I read more about it years ago, the name OGG always made me picture some wanna be Mac Addict listening to Mod files or something in a dark room prodding through OS7 while dreaming how elite he had become.
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...
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!
Why do the RFC page headers say "OGG" instead of "Ogg"? The headers in other RFCs aren't arbitrarily
capitalized. It's hard enough convincing people
that Ogg isn't an acronym without the RFC itself
making our work harder.
Can they fix this without issuing a new RFC
number?
Yes, that's what RFC stands for. Slashdot took over the commenting aspect of all RFCs, so please just post any comments you might have about RFC 3533 below.
Sincerely,
Letter
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:Request For Comments
by
Greger47
·
· Score: 5, Interesting
No, thats the way it is by design.
IETF doesn't standardize anything untill it is finished, complete with reference implementations.
"...for all you folks who won't look at something unless it has an RFC attached to it."
I can imagine Logic taking four long seconds to come up with something that sounded smart at the time. Here are some more gems that Logic has come up with:
"John Carmack reached 50,000 ft. with his X-Prize entry today, for those of you who don't take video games seriously unless their designer is a rocket scientist."
"NASA today announced proof of a black hole in a nearby galaxy, for those of you who won't watch Star Trek episodes with unproven singularities."
"Sun finally implemented generics in Java in its latest release, for those of you who only view web pages with applets written in languages with generics."
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
It's only a matter of time before Verisign decides to patent it.
"OGG is better"
"what? We're talking about music, not whatever that is..."
"OGG is about music. It's a file format, like MP3s, only better."
"Okay, dude, I'm sorry, I just keep missing the first thing you're saying"
"It's OGG. O - G - G."
"Dude, that is the most retarded name I've ever heard of... let's play some halo on my x-boxe!!!"
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!
Can they fix this without issuing a new RFC number?
Dear RFC,
Yes, that's what RFC stands for. Slashdot took over the commenting aspect of all RFCs, so please just post any comments you might have about RFC 3533 below.
Sincerely,
Letter
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
No, thats the way it is by design.
IETF doesn't standardize anything untill it is finished, complete with reference implementations.
Heres a good writeup: The Internet Engineering Task Force
"...for all you folks who won't look at something unless it has an RFC attached to it."
I can imagine Logic taking four long seconds to come up with something that sounded smart at the time. Here are some more gems that Logic has come up with:
"John Carmack reached 50,000 ft. with his X-Prize entry today, for those of you who don't take video games seriously unless their designer is a rocket scientist."
"NASA today announced proof of a black hole in a nearby galaxy, for those of you who won't watch Star Trek episodes with unproven singularities."
"Sun finally implemented generics in Java in its latest release, for those of you who only view web pages with applets written in languages with generics."
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.