search

fongecore / rubyripper

Automatically exported from code.google.com/p/rubyripper
0 stars 0 forks source link

feature request: XSPF playlist support #178

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
Hi folks.

There have been talks about CUE and M3U list generation over here.

It seems that the XPFS playlist (XML) standard represented by libspiff
is taking over slowly but surely.

Audacious, Amarok and so on will support it.

I am wondering if to put more emphasis on this one. It would be a great
thing if this would be a feature within Rubyripper.

Cheers

Original issue reported on code.google.com by kls.schlz@gmail.com on 29 Feb 2008 at 11:02

GoogleCodeExporter commented 8 years ago 
Sure, what are the advantages over simple m3u files?

Original comment by rubyripp...@gmail.com on 5 Mar 2008 at 5:51

GoogleCodeExporter commented 8 years ago 
You can store artist,track, album and so forth as done within ID3-Tags. This 
way you
can properly use Amarok also with wav, flacs and so forth. 

<?xml version="1.0" encoding="UTF-8"?>
<playlist version="1" xmlns="http://xspf.org/ns/0/">
    <trackList>
        <track>
            <location>http://example.com/song_1.mp3</location>

            <!-- artist or band name -->
            <creator>Led Zeppelin</creator>

            <!-- album title -->
            <album>Houses of the Holy</album>

            <!-- name of the song -->
            <title>No Quarter</title>

            <!-- comment on the song -->
            <annotation>I love this song</annotation>

            <!-- song length, in milliseconds -->
            <duration>271066</duration>

            <!-- album art -->
            <image>http://images.amazon.com/images/P/B000002J0B.01.MZZZZZZZ.jpg</image>

            <!-- if this is a deep link, URL of the original web page -->
            <info>http://example.com</info>

        </track>
    </trackList>
</playlist>

Original comment by kls.schlz@gmail.com on 5 Mar 2008 at 6:39

GoogleCodeExporter commented 8 years ago 
I think you meant XSPF playlist support, this is wat libspifff is pointing too 
anyway.

Original comment by rubyripp...@gmail.com on 22 Jun 2008 at 2:35

GoogleCodeExporter commented 8 years ago 
For later reference, the specification:
http://www.xspf.org/xspf-v1.html

You said it's taking over slowly m3u and cue. Can you explain why it would take 
over cue? 
Can it store pregaps for example? I have missed it in the specification. I do 
have the feeling 
too that the format is more focussed on web-playlists than on local playlists.

Original comment by rubyripp...@gmail.com on 22 Jun 2008 at 2:50

GoogleCodeExporter commented 8 years ago 
Having read part of the specification once again I really don't see the 
advantages of
this playlist in comparison to m3u / cue files. I thought, well perhaps they've
focussed on metadata support, but that's not the case either. Notice that 
cuesheets
already support some metadata information.

As noted earlier XSPF seems more relevant for remote files. Due to the low 
interest
of other people for this one, I mark this one as WontFix.

Original comment by rubyripp...@gmail.com on 22 Aug 2009 at 8:34