The dbox from the initial scan double counts the tracks being "added" ... ie. where tracks that pre-existed in MM, and the scan has now added the GPM link ... it double counts these
https://www.dropbox.com/s/dnt4ees1iajan ... g.png?dl=0
Having a scan log is good, but it could be more helpful. Currently is as as follows:
- It firstly lists all the GPM tracks which were matched OK. They seem to be listed in random sequence. They are shown as operation = "updated".
- The report then lists the GPM tracks which were not matched, again in random sequence. These are shown as Operation = "skipped"
- There is a line for every track in our GPM library ... It can be a long report. GPM libraries may contain up to a max of 50,000 tracks of our own tracks.
- Every row includes the tracks hidden GPM link; 30 or 40 characters of random text
- We get one chance to review or save the report ... ie. by pressing the View Log button on the Scan Results dbox ... The report is lost if you close the Scan Results dbox before you realise that you need to review the report.
It would be more useful if the "skipped" tracks were sequenced by something useful, like <album><Track> or <album artist><album><track>
Same thing with any other errors ... eg "403 Forbidden" or conversion errors etc.
The matched tracks could then be listed in the same useful sequence. ... Operation = "GPM link saved" .... or "GPM track added to MM" ... or "GPM track downloaded" ... nb. I have only tested the former "operation"
TheGPM track links are useful to you in the case of problem report? ... if no, they could be discarded, as it is no use to a MM customer. It just makes the log less easy to use.
I still believe that MM would be enhanced if it had an option to auto-save the most recent n scan logs ... so that I could go to a menu option like File|ScanLog|View one of the last n Scan Logs
It is disappointing that a Scan Log is not produced if I select a bunch of tracks, and then right click "download". ... This is similar to a sync. It results in a batch of tracks being inserted into the MM db. ... It is different I suppose in that I specifically selected the tracks to be acted upon, but the batch operation may encounter errors, and only be able to complete part of the batch. So there still may be a cleanup job for me to do, and a log would be useful.
I realise that there is no clear end to a download batch .. ie. I may, or may not, add further albums to the download batch, and so you don't know when I am completed ... you could start a download batch whenever I do my 1st download in a specific invocation of MM, and keep adding to it until MM closes, or gets restarted following an abnormal shutdown ... ?
If that were done you could also include any track "removes" into that log also, which would be good.
Some people put a lot of work into their MM db. ... Batch update operations are disconcerting without an activity log IMO.