Playlists
BeetstreamNext reads and writes playlists from several sources:
- BeetstreamNext’s own playlists: Created via the standard Subsonic playlist endpoints, stored per-user under
playlist_dir. Leaveplaylist_dirempty to disable BeetstreamNext-managed playlists entirely. - Beets’
playlistplugin directory: Regular.m3u-style playlist files managed by Beets. - Beets’
smartplaylistplugin directory: Query-generated playlists. These are read-only in BeetstreamNext, because they’re automatically regenerated by Beets.
Permissions
- Any user with
playlistRolecan create/edit/delete their own BeetstreamNext-native playlists. - Any user listed under
external_playlists_editorscan additionally edit/delete playlists from the Beetsplaylistplugin directory. Nobody can editsmartplaylist-generated playlists, only read.
Note: BeetstreamNext-native playlists are written to the disk as
.m3ufiles like Beets’ playlists.
See playlist_dir and external_playlists_editors in the configuration reference.