Some things in this thread:
- my request for giving suggestions to enhance the user interface and make it more usable and smaller, with the same information (mostly unanswered up to now)
- "known-problems" in one of my posts
- "what can it do" in one of my posts
might have answered some of your questions.
First of, the program dialog *is* too large. I have been working on this, and the new version to be released will have all less-used MediaMonkey-taggable fields (now added!) to the "More options" dialog (including the already included Custom1-3) to save space on the front panel. The masks for these fields are editable/enablable (right English ?
) in the options dialog and will (for now) not be viewable in the front panel. A future version might include a "preview popup list" for those fields, but because they are mostly "Write-Once Read-Many" fields, that's not an issue for me personally. But please let me know if this would be an issue for you. Anyway, adding them to the "preview track listing" probably would be a better solution for this.
The hidable tracklist fits in the above strategy, but of course it makes much sense to automaticly open it when tracks are loaded from within MM. I have fixed this now. For people who don't want this behaviour (so don't automaticly open it), please let me know and I will maybe add an option.
As already said in this thread, the tracklist just provides a basic preview of what tracks have been loaded from MediaMonkey. It doesn't (yet) implements the recognition features like MM Amazon tagging has, and so the question marks have no meaning yet. That maybe explains your "results are sorted incorrectly" (well, actually *not* matched) problem.
Now, the tracklist represents the track info in MediaMonkey. I will change it so it gives a preview of the actual track changes, so you can see what will be tagged and what not (at least for the most important tags). That will give less problems with the misunderstanding about what will be tagged and what not, and if anything will change the displayed track order.
If anyone has a clue on how to create a "matching" algorithm to match found tracks with loaded ones, please let me know because for me it would just be trial and error, as this isn't an easy thing to do (certainly because people make so many mistakes in tagging their files/inconsistent tagging standards/incorrect submittings to the source websites).
It would be a big help if someone could explain me how MediaMonkey is doing it for album tagging.
I would use all available fields in an order of importance (e.g. Title, Artist, Song Length, ...) but the algorithm worries me.
In a previous release, I implemented a warning function before the actual tagging is done, but later removed it because it annoyed me and I would probably get complaints about it. But I do state that the tagging function has to be used with care.
As for me: I test the program on test/dummy mp3's, so there nothing will ever be changed to my real tracks.
First, this program was just a simple script parser using the Mp3Tag style, later I made it look very much like the MM Amazon tagging dialog, to keep the comfortable feeling. But if anyone things something should be made clearer.... please let me know.
BTW: I don't have found a listview control that has column checkboxes on it, so that is a major GUI problem for me. Can anyone help me with that? I think I will have to create it myself, but any help would be helpful. (subclassing the standard listview, intercepting move/resize events, place and move checkboxes on top accordingly --> would be the solution. That's also the one MM Amazon tagging uses if I'm correct).
BTW: If anyone encounters problems using the "link" between MediaMonkey and the tagger program, *that's not my fault*, and I can't help that. Restarting MediaMonkey should solve it's issue concerning COM.