It can be quite a chore to add tracks to your playlist manually by looking up each and every track, especially if they existed on another application that allows the exporting of playlists by generating a .m3u playlist file.
Todo:
[x] Implement endpoint for importing playlists by passing in m3u file content.
[ ] Fix & refactor certain parts of code.
[ ] Add an option for adding a new playlist via import (Client Side)
[ ] Display a "Track Matching Utility page" to match tracks that weren't (Client Side)
Currently it can matches tracks on two paramters:
Duration, File name, Artist name present in the m3u file
Duration, Track title, Artist Name present in the m3u file
I've implemented a get_tracks_containing_filepaths getter function in app/store/tracks.py. There's probably a better way to implement that, but I couldn't think of it while testing all of this out, so that needs to be changed along with a lot of other small things within the PR.
Duration matching can be seen as redundant but is especially important for things like VIP remixes, where they belong to the same artist and have similar titles but are two different tracks.
It can be quite a chore to add tracks to your playlist manually by looking up each and every track, especially if they existed on another application that allows the exporting of playlists by generating a
.m3uplaylist file.Todo:
Currently it can matches tracks on two paramters:
I've implemented a
get_tracks_containing_filepathsgetter function inapp/store/tracks.py. There's probably a better way to implement that, but I couldn't think of it while testing all of this out, so that needs to be changed along with a lot of other small things within the PR.Duration matching can be seen as redundant but is especially important for things like VIP remixes, where they belong to the same artist and have similar titles but are two different tracks.