If you use this for the first time on an M2 (or arm architecture to be more precise) you might run into the program failing over and over as it tries to do stuff (it keeps asking "Throw in Trash" or "Ok"), then when you click OK it pops up in the Security "Run Anyway", which I do.
Here's where it gets tricky and I screwed up with a 90,000 file collection of rekordbox music; I didn't "realize" that the errors were dwindling, and I re-ran the process a 2nd time, which takes around an hour so far to get to the report which had this issue.
Mistake: Running this on a full library that takes an hour without pre-fixing the issue.
Subtle Workaround:
Setup your library to be like 3 - 5 files, or 1, and do the export process (or edit your XML you exported and make sure only a few files are in there). Run it, get past all of the "Run Anyway" security issues, and when you finally get a report back, run your FULL XML. Which I'm about to restart :)
If you use this for the first time on an M2 (or arm architecture to be more precise) you might run into the program failing over and over as it tries to do stuff (it keeps asking "Throw in Trash" or "Ok"), then when you click OK it pops up in the Security "Run Anyway", which I do.
Here's where it gets tricky and I screwed up with a 90,000 file collection of rekordbox music; I didn't "realize" that the errors were dwindling, and I re-ran the process a 2nd time, which takes around an hour so far to get to the report which had this issue.
Mistake: Running this on a full library that takes an hour without pre-fixing the issue.
Subtle Workaround:
Setup your library to be like 3 - 5 files, or 1, and do the export process (or edit your XML you exported and make sure only a few files are in there). Run it, get past all of the "Run Anyway" security issues, and when you finally get a report back, run your FULL XML. Which I'm about to restart :)