An idea to help organize your music with extra metadata using a SQL Server Database. This repository searches through a folder and gathers metadata already in mp3 files to add to a database
Removed PK in order to allow NULL in TrackID and TrackOrder
Replaced by 2 unique constraints: (PlaylistID, TrackID), (PlaylistID, TrackOrder)
Added Surrogate identity column that is completely unused outside of a key for EF
[x] TODO: Update Schema Readme
Parsing Changes
Support for m3u8 files
More fallbacks
Better matching
Better merge operations
Export only
Only update playlists if the file was modified after the date we last updated the database side of things
Note that setting the value to the last modified date somehow resulted in repeated ingestions.
We were adding the exact last edited date to the database and some kind of rounding made it always insert as 0.1 seconds before the last modified date, so it looked like we always had something to update
[x] TODO: Update Playlist Transfer Tool Readme
TODO
[x] See if your recently converted Groove playlist can run in groove without all the proper data
[x] Also determine if it can run with less data, and if it can, make that a fallback to just throw the path in the file with absolute path prefix as necessary
[x] Add support for .m3u8 files
[x] They have a new extension
[x] They have a new comment for the name of the file (so ignore any line that starts with #)
[x] Test
[x] Groove to Samsung
[x] Samsung (not found) to Samsung
[x] Groove (not found) to Groove
[x] Export Only Groove (with not founds and founds)
[x] Export Only Samsun (with not founds and founds)
Schema Changes:
NULL
inTrackID
andTrackOrder
PlaylistID
,TrackID
), (PlaylistID
,TrackOrder
)Parsing Changes
TODO
.m3u8
files#
)