I also would like to have real importing and exporting of M3U files. An M3U file is what most people mean when they refer to a “playlist”.
M3U (or M3U8) is an industry standard with very specific stanza formatting that includes a line that provides the “Artist - TrackName”. For example (from previous post by Konstantin Merikis):
#EXTINF:323,Bad English - 03 - The Restless Ones
…/Melodic Rock/Bad English/1989 - Bad English/03–The Restless Ones–Bad English.mp3
ROON seems to define an external “playlist” as simple a file with a list of music file path descriptions. That is not M3U and they should not require customers to transform an M3U into this ROON defined creature before import. The import should be improved to recognize and parse a real M3U file, in addition to its current design.
And, exporting this ROON type of playlist file (missing the #EXTINF lines) to a spreadsheet is not the same as exporting to create a M3U file. Once again, why should they make their customers manipulate the spreadsheet to generate a real M3U?
Not all customers are hobbyists with extensive programming skills (heaven forbid I would manually manipulate these files).
For ROON staff with programming skills, parsing an M3U file is non-trivial, but also not that difficult. The web has many examples of such code. Or there are likely some ROON customer who could contribute coding snippets.