Open CodingSamS opened 4 months ago
I've never seen the non-extended format being used. That said, this is easy to implement but parsing extended format is more secure since it is structured. Is there any specification about the non-extended one?
According to Wikipedia there is no specification - it's a de facto standard.
https://en.m.wikipedia.org/wiki/M3U
But it is simple - only absolute paths, relative paths and URLs.
I found a pretty good summary of the format here:
It would also be useful to m3u files formatted as below, a slight generalization to the suggestion above
#EXTM3U
#EXT-X-RATING:(number)
(track location)
...
I noticed this is the format Poweramp uses. I imagine other music apps might also add nonstandard fields to the m3u file, but they likely begin the extra fields with a #
. It seems like these could be taken account of altogether by ignoring the first #EXTM3U
line, considering #
above a link to denote a comment, and extracting data only from the commented lines Symphony is aware of.
Description
Importing a normal .m3u playlist results in an empty playlist. However, importing an extended .m3u playlist does work.
Non-working .m3u playlist:
Working .m3u playlist:
Steps to Reproduce
Expected Behavior
The playlist should contain the tracks mentioned in the .m3u file.
Device
Checklist