I use Google Music Manager to mange my music collection for a while. Recently, I decide to reorganize my music library and I found some inconvenience or rather say “can be improved” about the Google Music Manager.
If you are reading this, you probably already know how good is the Google Music . I will just start with my unsatisfied points.
- ID3 Tag only takes ID3v2 with UTF-16.
- Not able to retry the failure upload tracks.
- Update ID3 tags does not trigger the re upload. ( Music Manager use MD5 to identify whether changes on the Music file itself. Music Manager wont change recognize its new update file even we change the ID3 Tags. )
For me, Point 2 and 3 are the issue I like to resolve so I start pork around. The exploration of the application lead me find the log file and the sqlite db under the C:\Users\%USERNAME%\AppData\Local\Google\MusicManager
Since it is a Sqlite db, lets try to see whats in there.
WARMING! Make sure you backup the file before you try it on your system.
- Close Music Manager
- Backup the ServerDatabase.db ( just make a copy to other directory).
- connect to ServerDatabase.db ( I use sqliteman)
xfiles contains all the tracks that has been scan by Music Manager. There is very little document I can find about the table definition. Below are the list of the status that I can find in the internet.
- 0: Not yet upload
- 1: ? ?
- 2:already upload
- 4: Error uploading file
- 5: ??
- 6: Reach 20000 tracks
- 11: File marked as permanent failure on server
Therefore, if we want make the music manager to upload the files, we need to update the row with MusicUploadStatus to 0.Another way is touch the file to force the MD5 change so Music manager would retry. I may try it later to see how it works.