-
-
Notifications
You must be signed in to change notification settings - Fork 120
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 import/export #447
Comments
from #36:
stuff from #36 that might deserve it's own issue?:
|
I'm actually unsure whether I'll immediately implement this as stateless import/export, or whether I will track the file URIs and update it that way. The latter is harder to manage and probably requires #322, so I think stateless import/export will come first. |
Would it be possible to import playlists from Listenbrainz? The format is documented here, I think it would integrate nicely with the already existing MBID’s |
I can, but it would not have any internet fetching. You would need to download the .jspf file and then open it in Auxio @nzure. |
Would it be possible to be able to select the directory where the playlists are stored ? |
Playlists are stored in a database normally, but you will be able to export to any directory allowed by the file picker @Mikaciu. |
Great idea |
Update: Writing a M3U parser is stupid simple, so the backend of this can be easily done. I'm just stuck on the frontend, since I actually want to use menu/"speed dial" functionality so that the "create playlist" button as an option for importing. See the example(s) below: tt8.mp4This requires some custom view magic that will take a little bit, so I'm aiming for 3.3.0 for this. |
|
thank you, that's the most important thing to me! And I hope there won't be a problem with exporting a playlist with more than 1500 tracks on android! That would be great! |
There shouldn't be an issue @Wjxfi, but it might take a little while to import due to it's size. |
it's a good thing it is! I will gladly switch from retro music player to yours, as you will not have this error! Very much looking forward to the update! :) |
Hey! @OxygenCobalt Please :) waited so long |
Please be patient @Wjxfi. I am extremely busy with school and will not be able to do significant work on Auxio for a month or two. |
Screen_recording_20231220_132215.webmImporting from this M3U file:
Only relative paths are supported currently. I don't know how to go about absolute paths since android obfuscates the real path of something behind volume abstractions. |
NVM, absolute paths will be supported too, but under the assumption that they are relative to the volume of the M3U file. Another additional assumption is the usage of unix-style "../dir/./file" type paths. If any of you use windows-style "C:\" paths, please let me know. |
foobar2000 exports such paths for its playlist M3U/M3U8 exports. I recall even old Blackberry's stock music player handling them fine[1], so they're presumably common enough. [1] How it handled the paths was assuming the drive letter was the root of the exposed file system (so eg: |
Alright, this sounds like what I can use for Auxio. I'm basically forced to assume the playlist volume is the same as the file volume. |
Will imported playlists automatically update when the m3u file is changed? If not automatically, an option to rescan and reimport all playlists would be good too. |
Sorry for the delay @evanc577. That's not planned for the MVP since it effectively requires #322 for the best results. Currently there's going to be an "Import" menu option that allows you to reimport a m3u file back into the playlist. This feature is also basically done. There's some rough edges I need to resolve first regarding when names conflict, but otherwise it should arrive in the next release. |
Some of the other functionality mentioned here will be spun off into issues once I fully decide on doing them. |
Split from #36.
The text was updated successfully, but these errors were encountered: