[vorbis-dev] Re: [vorbis] Request for Standardization: classical music TAGS

[Trick]

> I disagree with having a mini-display-format language.  The purpose
> of the tags is to store information.  Its up to the client how it
> wants to display the information.  In winamp/xmms for instance,
> they often try to display everything on one line.  Other players
> have a nicely formatted multi-line display of the relevant
> information.

You misunderstood. What i suggested isn't a mini-display-format 
language. It's a way to tell applications that don't know about extra 
tags how they're used. For example, for classical music, you want 
extra tags like COMPOSER, CONDUCTOR and ENSEMBLE. You could fill in 
those tags, and then create a compability-tag for apps that don't 
support those extra tags, so that it too can show the extra 
information. That way everybody gets all the information, and those 
who want can get the specific information.

However, it is still up to the app how it should display this. The 
DISPLAYFORMAT-tag i suggested is a _suggestion_. What i originally 
thought of was putting this info into the standard tags, like fx. 
"ARTIST=$COMPOSER ($CONDUCTOR)". Also, if the app DOES understand 
these tags, it can be free to do whatever it wants with them.

This is also good for music that don't fit in a specific cathegory. 
There's loads of strange music out there =)

I still think this is a good idea =)

> I was browsing Amazon today, and I found something interesting:  in
> their classical music section, they have found it necessary to add
> exactly the tags I was suggesting before; to wit, COMPOSER,
> CONDUCTOR, PERFORMER, ENSEMBLE.  It must be kismet...
>
> I think the ARTIST tag is useless.  Someone might quibble, "what
> about Bruce Springsteen and the E Street Band?".  I would say,
> since they are treated as a single item, stick "Bruce Springsteen
> and the E Street Band" in the ENSEMBLE tag.  But since Bruce is the
> one being hilighted, you could just put "Bruce Springsteen" in the
> PERFORMER tag.
>
> Now that I think about it, the ARTIST tag works pretty good for pop
> music.  Maybe we could define the ARTIST tag to be: the name of
> whoever is *primarily* associated with the song/track/piece.  Then
> it doesn't matter if a person is the composer, performer, whatever,
> you just stick 'em there.  And classical music encoders could
> ignore the tag.
>
> Jonathan
>
> On Sat, 6 Oct 2001, Trick wrote:
> > Why not do as one here suggested (don't remember who atm, sorry),
> > introduce a _standard_ tag for display format of the tags ? You
> > could even go further, and make some specific format tags for the
> > different standard tags, which, if present, determine how to
> > compose that tag:
> >
> > ALBUM=S&M
> > ARTIST=Metallica
> > ENSEMBLE=San Francisco Symphony Orchestra
> > CONDUCTOR=Michael Kamen
> > TITLE=Wherever I May Roam
> > ARTISTFORMAT=$ARTIST with $ENSEMBLE ($CONDUCTOR)
> > TITLEFORMAT=$TITLE
> >
> > ... and maybe even a default format for displaying:
> >
> > DISPLAYFORMAT=$ARTISTFORMAT - $TITLEFORMAT
> >
> > Btw, it would be nice if variables were possible in all tags..
> > Would beat all other formats even further into the dust =)
>
> --- >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-dev-request at xiph.org' containing only the word
> 'unsubscribe' in the body.  No subject is needed. Unsubscribe
> messages sent to the list will be ignored/filtered.


-- 
Trick
__________________________________________
Linux User #229006 * http://counter.li.org

--- >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-dev-request at xiph.org'
containing only the word 'unsubscribe' in the body.  No subject is needed.
Unsubscribe messages sent to the list will be ignored/filtered.