Hi. Seeing as the topic appeared a while ago I was wondering: How do people feel about adopting ID3v2 for Vorbis aswell. This would, of course, mean it's given a stream of its own and even allow interleaving. It could be usefull, seeing as it would cut down on both initial development and software support, since a lot (most?) audio players already support it. It could also allow for code sharing on embedded devices, resulting in a smaller memory footprint. Well, just a thought. Regards Oscar --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a message to 'vorbis-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.
> Seeing as the topic appeared a while ago I was wondering: How do people > feel about adopting ID3v2 for Vorbis as well.I think you'll find that they're really, really, really opposed to the idea. And you thought people got reactionary when it's suggested that Vorbis tags be made machine-parsable.... I don't think of ID3v2 as anything even remotely resembling a proper metadata solution. -- Graham Mitchell - computer science teacher, Leander High School "Reading is to the mind what exercise is to the body." - Sir Richard Steele --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a message to 'vorbis-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.
On Friday 17 October 2003 12:09, you wrote:> Hi. > > Seeing as the topic appeared a while ago I was wondering: How do people > feel about adopting ID3v2 for Vorbis aswell.No. Please don't. Have you looked at it? It's a horribly over engineered binary format, for a start, and there are no complete implementations outside of the reference code - people plod away for a few days, then give up. Better to just let it die. Better, also, to hack vorbiscomment on to the front of mp3s - but I doubt you'll find too many people here interested in doing that :-) John --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a message to 'vorbis-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.
> Seeing as the topic appeared a while ago I was wondering: How do people feel about adopting ID3v2 for Vorbis > aswell.HAHAHAHAHAHAHAHAHAHAHAHAHAHAHA! I'll be impatiently awaiting Monty to torch you now. Better put on the asbestos while you can. jack. --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a message to 'vorbis-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.
Oscar Sundbom wrote:> Seeing as the topic appeared a while ago I was wondering: How do people feel about adopting ID3v2 for VorbisNo way, why would anyone want to have that atrocity? Its a hack to improve ID3v1, which is a hack in itself to provide a very restrictive, complicated, limited in every aspect way for adding "metadata" (don't even think it can be described like that) to MP3s. We absolutely have no use for that. I assume a proper metadata stream for Ogg would be an XML-based solution. Apart from that, see Segher's repeatedly comprehensive and well thought-out mails on the topic "metadata stream, why we need it, why Vorbis tags can't do it". Why anyone would want to add something like "crippled Vorbis tags" AKA ID3v* to Ogg or Vorbis is beyond me. <p>Moritz --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a message to 'vorbis-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.