Jump to content

support for xspf and xml playlists


Recommended Posts

@helloman123 interesting,  it expands the range of "locations" 

<?xml version="1.0" encoding="UTF-8"?>
<playlist version="1" xmlns="http://xspf.org/ns/0/">
  <trackList>
    <track>
      <title>Windows Path</title>
      <location>file:///C:/music/foo.mp3</location>
    </track>
    <track>
      <title>Linux Path</title>
      <location>file:///media/music/foo.mp3</location>
    </track>
    <track>
      <title>Relative Path</title>
      <location>music/foo.mp3</location>
    </track>
    <track>
      <title>External Example</title>
      <location>http://www.example.com/music/bar.ogg</location>
    </track>
  </trackList>
</playlist>

but as Wikipedia shows, 

"XSPF was created by an ad hoc working group that commenced activities in February 2004, achieved rough consensus on version 0 in April 2004, worked on implementations and fine tuning throughout summer and fall 2004, and declared the tuned version to be version 1 in January 2005.

XSPF is not a recommendation of any standards body besides the Xiph.Org Foundation"

so it is quite an old standard and has not grown in popularity. 

Link to comment
Share on other sites

I'm not sure how much help this would be, given Poweramp's database-driven model. PA currently matches songs for M3U Playlists solely by their unique filename and first-level containing folder combination, it doesn't retain any other codes or metadata in its database which would otherwise uniquely identify a track. All other path information gets discarded when the playlist is resolved, so as long as at least the first level of folder names matches, it's actually pretty robust now.

I guess if your embedded tagging is very accurate, it would be possible to use an XML format and cross-match with Title / Album / Artist tags, but a simple flat list of folder/filenames does work pretty well.

The nearest thing I could find to a spec for XSPF is https://www.xspf.org/xspf-v1.html , and that revolves around the same basic path/filename concept, with additional description fields available - but Poweramp ignores all that anyway, and uses metadata from the audio file.

Andre

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...