Anyway, here are some suggestions for features and improvements, ordered by least to most significant to me as a user:
1. Clearing tags
I have been attempting to use MM to clear and rebuild mp3 tags, but have run into the following issue:
Some of the less common ID3v2 tags don’t appear to be picked up by the client application. In MM’s db, I often discover undesirable values in the “textdata” field of the “addsonginfo” table. Unfortunately, I often cannot see or view these values in any field in the MM app.
If I use the MM Search node and look in “any text field” for one of these rogue values, I am able to retrieve the songs that contain them. Of course, I still cannot see the values in “properties” of these songs
The result is that I need to go to three or four different programs in an attempt to clear out junk tags. Then I need to worry about whether the tag I’ve cleared in a separate app is still being stored in the MM db. An example of this phenomenon happens with the “Encoded By” tag. I find the rogue value in MM db, search for the song in MM client, delete the value in Winamp, then manually update MM db. Other fields require other applications.
The best solution would be a utility to entirely sweep and clean all tags (id3v1 and v2) from selected songs. Short of this, would be a way to expose all tags to the MM client so that they can be manually cleared within the application.
2. It would be invaluable to have the ability to assign multiple genres to a song, plus the ability to assign the degree of influence for each genre. (e.g. song X is 75% Rock, 50% Folk, 100% Instrumental). To make it meaningful, the player or playlist generator would also need to be able to incorporate the information into track selection. They’ve been discussing similar functionality at Musicbrainz for some time.
http://www.musicbrainz.org/pipermail/mu ... 00938.html
If your app and their concepts could get together on this, it just might revolutionize automated track selection!
3. Execution of the “Clear Library” command should finish by compacting the Access database. It does not currently appear to do so.