Playlists

BeetstreamNext manages its own playlists and also mirrors those from Beets:

1. BeetstreamNext’s own playlists: Created via the standard Subsonic playlist endpoints, and stored in BeetstreamNext’s database. Any .m3u files already present in playlist_dir (per-user subfolders are considered private playlists, top-level files are considered public) are imported on startup.

   Every change is also written to an .m3u file in playlist_dir so other players can use them. Leave playlist_dir setting empty to not write any.

2. Beets’ playlist plugin directory: Regular .m3u-style playlist files managed by Beets. They are considered public and kept in sync with their files. Edits made in BeetstreamNext are written back to the file.

3. Beets’ smartplaylist plugin directory: Query-generated playlists. These are read-only in BeetstreamNext, because they’re automatically regenerated by Beets.

Permissions

• Any user with playlistRole can create/edit/delete their own BeetstreamNext-native playlists.

• Private playlists can only be seen and edited by their owner (and admins). Public playlists can be edited by everyone.

• Admins and users listed under external_playlists_editors can also edit/delete playlists from the Beets playlist plugin directory. Playlists generated by smartplaylist plugin are read-only.

See playlist_dir and external_playlists_editors in the configuration reference.

Moving playlists to a streaming service

If you want to export your playlists to Spotify, Deezer, Tidal and others, you can:

1. Export as CSV from the Web UI, and upload it to Tune My Music

2. Connect BeetstreamNext directly to Soundiiz using the OpenSubsonic connection

Both can then export to most existing streaming services.