Feedback request: XSPFPHP Link and Info elements

[Thomas R Bailey]

Sebastian or Lucas,

I could use a bit of feedback on this link/info topic.

I added a custom URI for the link element to settings.php. If present It
will be replicated for the entire playlist. Is it perhaps better to just
drop the link element within the context of a dynamic id3 based playlist?

I added parsing a custom URI on a per-directory basis for the info
element.  To use info element one adds a URI to the end of the directory
line for a specific directory (xspf.dir) and it shows up in the info
element for all tracks in that directory.

I also found a url_publisher id3 tag defined in the id3v2 frame but it
seems missing from the getid3 class library I'm using to extract them.
If I can get it to work I'll use it as the preferred info link and
default to the per-directory link specified or none if none exists.
Does that sound correct?

Last but not least; Any feedback on player.php?
Is this a stupid, useless, meaningless, feature?
I think it's neat as banana pancakes.

-Tom




_______________________________________________
Playlist mailing list
Playlist@...
http://lists.musicbrainz.org/mailman/listinfo/playlist

[Lucas Gonze]

Hey Tom, sorry to not have responded.  I've been only lurking just
because of job stress distracting me.

My basic feeling is that this is a nicely executed and conceived piece
of work which should exist and be widely available.  The
auto-extraction from tags is ultra-useful.  And having the metadata
means that a content resolver like Playdar can do quite a lot with the
playlist.

But I haven't yet personally installed it and given it a roll.  Hm.
Hang loose while I hook it up on my music blog...  I'll be back with
detailed comments.

On Thu, Mar 26, 2009 at 11:23 AM, Tom <siggma@...> wrote:

> Sebastian or Lucas,
>
> I could use a bit of feedback on this link/info topic.
>
> I added a custom URI for the link element to settings.php. If present It
> will be replicated for the entire playlist. Is it perhaps better to just
> drop the link element within the context of a dynamic id3 based playlist?
>
> I added parsing a custom URI on a per-directory basis for the info
> element.  To use info element one adds a URI to the end of the directory
> line for a specific directory (xspf.dir) and it shows up in the info
> element for all tracks in that directory.
>
> I also found a url_publisher id3 tag defined in the id3v2 frame but it
> seems missing from the getid3 class library I'm using to extract them.
> If I can get it to work I'll use it as the preferred info link and
> default to the per-directory link specified or none if none exists.
> Does that sound correct?
>
> Last but not least; Any feedback on player.php?
> Is this a stupid, useless, meaningless, feature?
> I think it's neat as banana pancakes.
>
> -Tom
>
>
>
>
> _______________________________________________
> Playlist mailing list
> Playlist@...
> http://lists.musicbrainz.org/mailman/listinfo/playlist
>

_______________________________________________
Playlist mailing list
Playlist@...
http://lists.musicbrainz.org/mailman/listinfo/playlist

[Thomas R Bailey]

Lucas Gonze wrote:

> Hey Tom, sorry to not have responded.  I've been only lurking just
> because of job stress distracting me.
>
> My basic feeling is that this is a nicely executed and conceived piece
> of work which should exist and be widely available.  The
> auto-extraction from tags is ultra-useful.  And having the metadata
> means that a content resolver like Playdar can do quite a lot with the
> playlist.
>
> But I haven't yet personally installed it and given it a roll.  Hm.
> Hang loose while I hook it up on my music blog...  I'll be back with
> detailed comments.
>  

Use the svn version, the archive on sf is a bit old.
svn co https://xspfphp.svn.sourceforge.net/svnroot/xspfphp

:)

_______________________________________________
Playlist mailing list
Playlist@...
http://lists.musicbrainz.org/mailman/listinfo/playlist