[Playlist] Project Opus Extension to XSPF

[Jim Sowers]

Hi David,

Some time ago I made several posts regarding what I thought would be 
good extensions for DJing.  I didn't have the time/expertise to write 
these up, and I'm not sure where they stand, so at the risk of being 
redundant, I think it would be cool/useful to have tags for:
 - indicating a fade-out point; fade-in point; duration of fade; slope 
of fade (linear, logrithmic) 

This might seem like a bit much, but I just spent the evening training a 
friend who is going to DJ a party using iTunes.  They want him not 
because he is a professional DJ, but because he knows the music (salsa 
in this case).  Thus, he doesn't care that iTunes counts the number of 
times he has played a track, but he does care that it has a crossfade 
function.  Everyone wants to be a DJ these days.  And they also want to 
be able to preserve their mixes without using proprietary software, so 
that they can share them.

Thus, I think a good implementation of these basic DJ functions will be 
popular--and likely well-supported.

Jim Sowers (DJ SpinCycle)
Chief Rhythm Officer, www.CalabashMusic.com


David Gratton wrote:
> Hello all,
>
> We've developed a few extensions to XSPF for use in our players that 
> we felt we should share with the community.  If anyone else has/is 
> developing something similar, or has any insight, we'd love to hear 
> about it.
>
> First, the general stuff, we've added extra statistics and meta data 
> to each song.  These include: number of listens, city the artist is 
> from, extra genre information, and a bit of internal data (song ID, 
> user ID of artist .. etc).
>
> Second, we added tagging / tag cloud extension.  Our schema looks like 
> this (notice that a dumb parser can still gather a tag list from this 
> schema, a smarter parser can build a proper cloud).
>
> <extension application="http://www.projectopus.com">
>   <po:tags>
>     <tag tid="INTERNAL_ID_OF_TAG" size="UNSIGNED_INTEGER">TAG
> _NAME</tag>
>     ....
>   </po:tags>
> </extension>
>
> Questions:
> Is this useful to anyone else or the specification?
> Specifically Dan Brickley, are we correct in not adding the "po:" 
> namespace to the internal <tag> elements?  (XSPF player wouldn't read 
> the data otherwise - not that the player is the issue).
> Is anyone working to standardize some of the common XSPF extensions?   
> If so, how about including tag clouds? :-)   If not, would this be a 
> useful area for us to get more involved with XSPF?
>
>
>
> David Gratton
>
> Project Opus
> #404, 329 Railway Street
> Vancouver BC Canada
> V6A 1A4
> (604) 685-2454
> http://www.projectopus.com
>
>
>
>
> _______________________________________________
> Playlist mailing list
> Playlist at lists.musicbrainz.org
> http://lists.musicbrainz.org/mailman/listinfo/playlist