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
Streamline Configuration and Usage of Generator #11
In general, try setting this up on a "fresh" machine, where SQL and SQL Server may not already be set up, and document how to do that. Additionally, document how to change the proper configs to get a user's data to run. The following is a list of suggestions:
Utilize a config file to allow for absolute paths to music
Create a more advanced loading system so you can see progress and estimated wait time of the generator
Add log output for more specific details on what is happening with each file and why/if certain fields are missing (if those fields are some of the more important ones that really should be on every MP3 file)
Of course, have the output of the console direct users to this more verbose logging when necessary
Include the "Limited Metadata" log to encourage users to get .mp3 or .flac versions of their music files (or fill out the metadata themselves) for files that we only half support (.wav right now)
In general, try setting this up on a "fresh" machine, where SQL and SQL Server may not already be set up, and document how to do that. Additionally, document how to change the proper configs to get a user's data to run. The following is a list of suggestions: