-
Notifications
You must be signed in to change notification settings - Fork 350
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Setting a playlist path with http:// scheme doesn't work #1975
Comments
Not intended, just not implemented. |
Okay, thanks for the reply. Might want to tackle this myself... I suppose the code handling this isn't much different from path parsing of |
It's more difficult. The music_directory is read-only by MPD's definition. The playlist_directory however is writable with MPD commands - clients can edit playlists. How is MPD supposed to edit http:// files? Sure you can do WebDAV PUT, but that's a complex thing to implement. It needs a whole new I/O abstraction in MPD. Did you know that the music_directory can contain playlist files, too? |
I figured there would be some read/write complications... Okay. Thanks.
I know. And I can actually see them in the library browser, but for some reason I cannot access them (MPD: No such playlist). |
I'm hosting my music on a server and I'm streaming from it using my laptop. The server runs python web server in my music directory:
mpd instance on a server is used only so that client mpd instance can fetch database from it. Relevant config on a client (laptop):
This works fine. I can see my music and play anything I want on a laptop. However, on a server I have lots of playlists which aren't loaded because I can't do this:
mpd complains that the path for playlists must be absolute. Is this intended? Am I doing something wrong?
The text was updated successfully, but these errors were encountered: