On Wed, Nov 28, 2012 at 03:03:32PM +0000, christof De Backere wrote: > Max Kellermann <max <at> duempel.org> writes: > > > No, it just remembers that the playlist file exists (ignoring its > > contents), and will tell that to the client via "lsinfo". The client > > can then choose to issue a "load" command for this playlist file. Or > > it can use "listplaylist[info]" to view the contents of the playlist > > file. > > Thanks for the info. I now understand that the mpd will treat it as any other > file in the music directory. It simply keeps it in it's database because the > file exists. The only difference being that it will not have any tags (scope > identifiers) defined, except 'filename', right? > > Client: now I'm trying to understand what a client should do. > So imagine the client retrieves the db at startup with listallinfo then it > will > get that playlist as > 'file: x/y/rasio/radio1_Stream.m3u'
On MPD 0.17.1 I get: "playlist: path/to/playlist.m3u" (And I don't think it has changed in the last few years' releases.) HTH, Jonathan Neuschäfer ------------------------------------------------------------------------------ Keep yourself connected to Go Parallel: INSIGHTS What's next for parallel hardware, programming and related areas? Interviews and blogs by thought leaders keep you ahead of the curve. http://goparallel.sourceforge.net _______________________________________________ Musicpd-dev-team mailing list Musicpd-dev-team@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/musicpd-dev-team
