Skip to content
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

Open
paradajz opened this issue Jan 24, 2024 · 4 comments
Open

Setting a playlist path with http:// scheme doesn't work #1975

paradajz opened this issue Jan 24, 2024 · 4 comments
Labels

Comments

@paradajz
Copy link

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:

python3 -m http.server

mpd instance on a server is used only so that client mpd instance can fetch database from it. Relevant config on a client (laptop):

music_directory "http://my_server"

database {
    plugin "proxy"
    host "my_server"
    port "6600"
}

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:

playlist_directory "http://my_server/Playlists"

mpd complains that the path for playlists must be absolute. Is this intended? Am I doing something wrong?

@MaxKellermann
Copy link
Member

Not intended, just not implemented.

@paradajz
Copy link
Author

paradajz commented Jan 25, 2024

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 music_directory? Do you have any tips on where to look and what should be changed?

@MaxKellermann
Copy link
Member

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?

@paradajz
Copy link
Author

paradajz commented Jan 25, 2024

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.

I figured there would be some read/write complications... Okay. Thanks.

Did you know that the music_directory can contain playlist files, too?

I know. And I can actually see them in the library browser, but for some reason I cannot access them (MPD: No such playlist).

Screenshot from 2024-01-25 10-46-33

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants