Thomas Fletcher
|
Re: External playlist file formats
|
Thomas Fletcher
04/08/2009 7:53 AM
post26329
|
Re: External playlist file formats
Tim Jenkins wrote:
> > Doing a quick search of the documentation, I can't seem to find a
> > description of the (externally generated) playlist file formats
> > that are supported by Aviage 1.1.
>
> It might be missing. :-)
>
> For Aviage 1.1, .pls, .m3u and .wpl are supported.
Thanks to you and Peter for your replies. I have a couple of
suggestions for
the documentation in this area:
1: File extensions are not formats. For the actual media files, often
these are
created by other programs but since playlists can quite easily be created by
users, it would be nice if there was a reference to the actual format and or
format _name_.
An outsourced table with links would also be fine. Something along the
lines of:
Format, Typcial File Extension, Typical Creator Program, Additional
Information
i.e.
Windows Media Player Playlist, pls, Windows Media Player, <wikipedia?>
2: If there is anything special about the content of the playlist that
is required, that
would be good to highlight. For example if the playlist is created on
Windows and
it uses Windows paths to the files, what are the limitations on matching
to those
files on my media store? Will the playlist ever match content on a
mediastore
that is different from the mediastore containing the playlist?
Rather than figure it out by trial and error, and get bitten by some
future change
in behaviour, it would be nice to explicitely spell out the playlist
resolution process.
3: If the file extension and not the actual file content are the only
things that the
playlist parsers key off of, then please make this explicit. One would
think, based
on the rest of the media framework, that you could just add new
extensions into
the playlist configuration area and if _one_ of the playlist parsers can
figure it out
that it will. Reading between the lines on the replies from Tim and
Peter it seems
that this _may_ not be the case.
I haven't tried it, so if it does indeed run through all of them, then
that would be
good to state as well.
I've switch to testing with m3u (MP3 URL =;-), generated on my target
machine
for now to exercise the playlist functionality. Clients however won't
be building
playlist files in Neutrino =;-)
Thanks again,
Thomas
|
|
|