Feature description:
Hi folks. Excuse my lack of knowledge if something like this already exists, but I couldn’t find anything in my research.
This feature would allow you to select an existing playlist and effectively convert it to a sever agnostic Symfonium playlist file (maybe a .symspl). When exporting a smart playlist that uses track names in the rules, the .symspl file makes references to the track titles, not file names/paths (like an .m3u8 might).
If we could take an existing playlist, long press it, and click a button like “Generate Shareable Playlist”, it would be really cool if a smart playlist was automatically generated using track name + artist (to avoid mismatches with matching song titles from different artists). Then, this playlist could be exported as a .symspl and shared without any concern of the server or filesystem. This would also create playlist resiliency if files are moved around on the backend. On the import side, non-matches could be reported in an error output.
Problem solved:
- Sharing playlists currently can be tricky (at least being on Plex). Exporting a .m3u8 via Symfonium includes absolute file paths, and I wouldn’t expect many smart playlists to be filled with specific track names. Creating a smart playlist that way would be quite cumbersome (hundreds/thousands of rules).
- Resilient to file path/server side changes.
Brought benefits:
It feels like the groundwork is already laid here. Smart playlists already allow for specific track name selection. Sharing a smart playlist with track names works perfectly (songs are resolved nicely upon import).
If we were able to convert an existing playlist to a smart/“shareable” playlist (basically recreating the playlist but with the matching logic found in a .symspl), it would make playlist sharing extremely flexible and would save us from manually creating a static playlist in the form of a smart playlist to achieve this goal (manually adding tons of rules).
I think this would be a game changer.
Other application solutions:
Additional description and context:
Screenshots / Mockup: