-
Notifications
You must be signed in to change notification settings - Fork 197
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Playlist question #845
Comments
To be able to play a m3u (or m3u8 or pls) file in the Files app or to import its contents to the Music app, the playlist file must contain relative paths to files within your cloud. The relative paths are resolved relative to the location of the playlist file. Playlist files containing absolute paths do not work, as the actual paths of your files is hidden by the cloud, and we only see the internal paths within the cloud storage. If you think that your playlist files already fulfill these requirements, then I will need some more info, and preferably a sample of the file which doesn't seem to work. |
Hi Paul Thanks for getting back to me. I use a Windows software called "Playlist Creator" to create my playlists. The default is relative paths, so that was given, BUT with a backslash. I never thought this would matter, but obviously it does... ;-) Changing them to forward slashes and recreate the list solved the issue. Done. Thanks again! However, some files got stripped away. I guess thats due to formats, Nextcloud music can't read/transcode (i.e. wma...). |
Yeah, backslash is not a valid directory separator on Linux. Instead, it's used as an escape character. Linux file names are allowed to contain almost any characters, including backslashes (which usually have to be escaped like Importing playlist file to Music brings only such files which have been scanned and are part of the library. This requires two things: 1. The file resides somewhere under the folder which has been configured as the root of the music library. 2. The file is identified as an audio file by Nextcloud. The second condition depends on the file extension to mime type mappings of Nextcloud; the mapped mime type must be of format |
When parsing a playlist file, we now support also the Windows style of using backslashes as directory separators instead of slashes. The solution is kind of heuristic or "best effort": The parsed path is first tried to be used "as is". If there is no such file and the path contains any backslashes, then those backslashes are converted to slashes and the lookup is made again. It is principally possible, that this would sometime find some unintended file, but those cases are "pathological" and should not be a real-life issue. refs #845
After thinking this for some time, I now created a kind of heuristic support for backslashes as directory separators. The application still firsts considers the possibility that any backslash found in a path contained in a playlist file is just part of the file/folder name. But if such file is not found from the file system, then all backslashes are converted to slashes and the app retries finding the file like this. |
The backslash support mentioned above is now released as part of Music v1.2.0. |
Hello
Thank you for developing this fantastic little app. Just a small question regarding playlists:
My library has a playlist folder with some *.m3u's which it can't make use of. Is there a possibility to point to that folder? I also tried to create a playlist in the Music App and import an existing playlist in my library directory, but do get an error message.
Thank you
The text was updated successfully, but these errors were encountered: