Peke wrote: ↑Sun Oct 18, 2020 5:05 pm
I raised this with rest of devs for another review/revision.
I noticed a new situation today.
Ludek wrote: ↑Thu Oct 15, 2020 2:39 pm
MM5 will ask you again to import MM4 data once you delete your C:\Users\<user>\AppData\Roaming\MediaMonkey5\ folder (or if you installed MM5 as portable then the Portable folder inside the MM install folder).
The above advice is nice and simple, but it doesn't seem to cover all cases in the way that the user may assume.
I did as above ... I accepted MM5 offer to import data and settings from MM5 ===> I noticed that the new MM5 database contained tracks not found in my MM4 database.
I think this is triggered in a situation where the MM4 db is in a custom location, and that custom location already contains a previous MM5 database.
I looked at the debug log ... MM5 found my MM4 in the custom location OK ... it wants to build the MM5 db in that custom location also, but since there already was a MM5.db, it added to it, rather than creating a fresh db.
I think that the situation would be improved if there was a dbox in this case, asking whether I want to add to the existing db, or build a new one.
The current situation is confusing. I spent some time trying locate some other MM4 db that it may be importing from, which was my initial assumption.
[Update] fixed typo ... I typed MM4.db, but meant MM5.db