Playlists #123
Comments
|
I'd be interested in this! |
|
I'm currently looking for a way to manage playlists with beets. I already use smartplaylists plugin, but there's something lacking with it: I can't specify any arbitrary order without relying on an existing field. Of course I could add a custom field named From an (my) user perspective, a simple way to manage playlists would require 5 functionalities:
The edition part consists in multiple functionalities itself:
|
|
Yep, that seems like a great list of requirements. If I could add one more: I've been fantasizing about having album playlists, not just track playlists. Perhaps even heterogeneous playlists that can contain a mixture of individual tracks and whole albums. |
|
I'd like to plug my own format here: The universal playlist format. I'm working on a beets plugin that will use this, but it would be nice if it can get better support in core. |
|
Hello, |
|
@djhibee That's very interesting, I'm interested in playlist functionality and adding UPL support to it. I already have scripts to export to UPL, but importing is not working very well yet. |
|
IMO beets should use standard M3U playlists instead of maintaining it's own in-database format. This would greatly simplify interaction with media players (MPD, etc.). Here's a list of features that would be nice:
|
Adds M3U playlist support as a query to beets and thus partially resolves issue beetbox#123. The implementation is heavily based on beetbox#2380 by Robin McCorkell. It supports referencing playlists by absolute path: $ beet ls playlist:/path/to/someplaylist.m3u It also supports referencing playlists by name. The playlist is then seached in the playlist_dir and the ".m3u" extension is appended to the name: $ beet ls playlist:anotherplaylist The configuration for the plugin looks like this: playlist: relative_to: library playlist_dir: /path/to/playlists The relative_to option specifies how relative paths in playlists are handled. By default, paths are relative to the "library" directory. It also possible to make them relative to the "playlist" or set the option or set it to a fixed path.
Adds M3U playlist support as a query to beets and thus partially resolves issue beetbox#123. The implementation is heavily based on beetbox#2380 by Robin McCorkell. It supports referencing playlists by absolute path: $ beet ls playlist:/path/to/someplaylist.m3u It also supports referencing playlists by name. The playlist is then seached in the playlist_dir and the ".m3u" extension is appended to the name: $ beet ls playlist:anotherplaylist The configuration for the plugin looks like this: playlist: relative_to: library playlist_dir: /path/to/playlists The relative_to option specifies how relative paths in playlists are handled. By default, paths are relative to the "library" directory. It also possible to make them relative to the "playlist" or set the option or set it to a fixed path.
Adds M3U playlist support as a query to beets and thus partially resolves issue beetbox#123. The implementation is heavily based on beetbox#2380 by Robin McCorkell. It supports referencing playlists by absolute path: $ beet ls playlist:/path/to/someplaylist.m3u It also supports referencing playlists by name. The playlist is then seached in the playlist_dir and the ".m3u" extension is appended to the name: $ beet ls playlist:anotherplaylist The configuration for the plugin looks like this: playlist: relative_to: library playlist_dir: /path/to/playlists The relative_to option specifies how relative paths in playlists are handled. By default, paths are relative to the "library" directory. It also possible to make them relative to the "playlist" or set the option or set it to a fixed path.
Adds M3U playlist support as a query to beets and thus partially resolves issue beetbox#123. The implementation is heavily based on beetbox#2380 by Robin McCorkell. It supports referencing playlists by absolute path: $ beet ls playlist:/path/to/someplaylist.m3u It also supports referencing playlists by name. The playlist is then seached in the playlist_dir and the ".m3u" extension is appended to the name: $ beet ls playlist:anotherplaylist The configuration for the plugin looks like this: playlist: relative_to: library playlist_dir: /path/to/playlists The relative_to option specifies how relative paths in playlists are handled. By default, paths are relative to the "library" directory. It also possible to make them relative to the "playlist" or set the option or set it to a fixed path.
Adds M3U playlist support as a query to beets and thus partially resolves issue beetbox#123. The implementation is heavily based on beetbox#2380 by Robin McCorkell. It supports referencing playlists by absolute path: $ beet ls playlist:/path/to/someplaylist.m3u It also supports referencing playlists by name. The playlist is then seached in the playlist_dir and the ".m3u" extension is appended to the name: $ beet ls playlist:anotherplaylist The configuration for the plugin looks like this: playlist: relative_to: library playlist_dir: /path/to/playlists The relative_to option specifies how relative paths in playlists are handled. By default, paths are relative to the "library" directory. It also possible to make them relative to the "playlist" or set the option or set it to a fixed path.
|
@skorokithakis Any progress on the UPF front? |
|
Not much, I'm afraid. I did some work towards it but there's nothing finished, only some stand-alone scripts that can convert to/from PLS... |
This issue was automatically migrated from Google Code.
Original author: adrian.sampson (February 18, 2009 07:00:50)
Original issue: google-code-export/beets#8
The text was updated successfully, but these errors were encountered: