Re: Hardware support
"Charles philip Chan" <[email protected]>
| Newsgroups | gmane.comp.multimedia.ogg.vorbis.general |
|---|---|
| Message-ID | <[email protected]> |
"Ulrich Windl" <[email protected]> writes: > The Samsung YEPP 6, Mega Edition (the one that plays 40 hours (MP3, not Vorbis) > with a single AA battery). Occasionally it goes crazy on long filenames or on long > tags, or on may tags, I never found out what exactly happens. I see. I don't have any experience with that device. > Last time I read the Vorbis specs, it sounded more like: "You can use > these tags while we think of something better (=the XML format)". IMHO > such statements are counter-productive. I don't have the specs here > right now to quote exactly. It is in the link in my last post: ,----[ Quote from Vorbis Comments Spec ] | The Vorbis text comment header is the second (of three) header packets | that begin a Vorbis bitstream. It is meant for short, text comments, not | arbitrary metadata; arbitrary metadata belongs in a separate logical | bitstream (usually an XML stream type) that provides greater structure | and machine parseability. | | The comment field is meant to be used much like someone jotting a quick | note on the bottom of a CDR. It should be a little information to | remember the disc by and explain it to others; a short, to-the-point | text note that need not only be a couple words, but isn't going to be | more than a short paragraph. The essentials, in other words, whatever | they turn out to be, eg: | | "Honest Bob and the Factory-to-Dealer-Incentives, _I'm Still Around_, | opening for Moxy Fruvous, 1997" `---- By arbitrary metadata I believe the author meant things like lyrics because later on in the spec there is a proposed, minimal list of standard field names: ,---- | TITLE | Track/Work name | VERSION | The version field may be used to differentiate multiple versions of | the same track title in a single collection. (e.g. remix info) | ALBUM | The collection name to which this track belongs | TRACKNUMBER | The track number of this piece if part of a specific larger collection or album | ARTIST | The artist generally considered responsible for the work. In popular | music this is usually the performing band or singer. For classical | music it would be the composer. For an audio book it would be the | author of the original text. | PERFORMER | The artist(s) who performed the work. In classical music this would | be the conductor, orchestra, soloists. In an audio book it would be | the actor who did the reading. In popular music this is typically | the same as the ARTIST and is omitted. | COPYRIGHT | Copyright attribution, e.g., '2001 Nobody's Band' or '1999 Jack | Moffitt' | LICENSE | License information, eg, 'All Rights Reserved', 'Any Use Permitted', | a URL to a license such as a Creative Commons license | ("www.creativecommons.org/blahblah/license.html") or the EFF Open | Audio License ('distributed under the terms of the Open Audio | License. see http://www.eff.org/IP/Open_licenses/eff_oal.html for | details'), etc. | ORGANIZATION | Name of the organization producing the track (i.e. the 'record | label') | DESCRIPTION | A short text description of the contents | GENRE | A short text indication of music genre | DATE | Date the track was recorded | LOCATION | Location where track was recorded | CONTACT | Contact information for the creators or distributors of the | track. This could be a URL, an email address, the physical address | of the producing label. | ISRC | ISRC number for the track; see the ISRC intro page for more | information on ISRC numbers. `---- Charles _______________________________________________ Vorbis mailing list [email protected] http://lists.xiph.org/mailman/listinfo/vorbis
signature.asc
(application/pgp-signature, 193 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFIfvNV3epPyyKbwPYRArCvAJoDRJGuU5WfcAnUdQescq1gvWH9BwCgnGai fv6f8fmNLzdHUlCN9uKNcZc= =OPrU -----END PGP SIGNATURE-----