Final Cleanup: Average Decibels, Linked Tracks Schema, Rating - Githubissues

JeffreyGaydos / music-database-generator

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

2 stars 1 forks source link

Final Cleanup: Average Decibels, Linked Tracks Schema, Rating #15

Closed JeffreyGaydos closed 1 year ago

JeffreyGaydos commented 1 year ago

There are a couple of fields and tables that I have marked as subject to change. Before we close out this project, let's make sure those fields are deleted or implemented.

Average Decibels

~Not sure how useful this will be~
~Min/Max Decibels might also be useful~
Reading out decibel values is 1 - no longer metadata, but content, and 2 - extremely time consuming. Opting to replace this with the following:
Comfortable listening volume column that is custom modified by the user (as needed) might be the best option

~Linked Tracks~

The bit flag on Main is maybe a bit unnecessary, but depending on how large the LinkedTracks table gets, it could save us on performance
Rename the table to be PlayBeforeTrackID and PlayAfterTrackID
Yes you can make a playlist out of this
- Come to think of it, we should just implement this as a playlist
- Also, you didn't put ordering in the playlists at all lol

Playlist

Needs playlist track rank
Can be utilized for "linked tracks"
- LinkedTrackPlaylistID is present if the tracks are linked. It is a reference to the PlaylistTracksTable, which can then tell us which order the tracks should be played in.
- This will be especially efficient for tracks that are linked to a lot of other tracks since we can literally treat it like a playlist

Rating

Get it off the file for the tracks
- Hmm actually ratings are a Windows-specific datapoint that is not attached to the files themselves
This will be a dummy variable then...