I have the same experience (I think).

MM4 and MM5 are installed (both non-portable).

Every time I install a new version of MM5, a new MM5.DB is created in the other directory where MM.DB (MM4) resides. The existing MM5.DB is not upgraded.

Paths for MM.DB and MM5.DB both look well defined in both ini-files.


[b]Initial situation MM4:[/b]

[url=https://ibb.co/mrscWNv][img]https://i.ibb.co/mrscWNv/Clipboard-MM4-1.jpg[/img][/url]

[url=https://ibb.co/dpsZrtr][img]https://i.ibb.co/dpsZrtr/Clipboard-MM4-2.jpg[/img][/url]

[url=https://ibb.co/9NpNxmW][img]https://i.ibb.co/9NpNxmW/Clipboard-MM4-3.jpg[/img][/url]


[b]Initial situation MM5:[/b]

[url=https://ibb.co/CP8NJkQ][img]https://i.ibb.co/CP8NJkQ/Clipboard-MM5-1.jpg[/img][/url]

[url=https://ibb.co/f8GkqBD][img]https://i.ibb.co/f8GkqBD/Clipboard-MM5-2.jpg[/img][/url]

[url=https://ibb.co/SmxthYs][img]https://i.ibb.co/SmxthYs/Clipboard-MM5-3.jpg[/img][/url]


[b]Install MM5:[/b]

[i]Wrong impact in directory where MM.DB resides:[/i]

[url=https://ibb.co/yWN7kr8][img]https://i.ibb.co/yWN7kr8/Clipboard-Install-MM5-1.jpg[/img][/url]


[i]No impact (what also wrong is) in directory where MM5.DB resides:[/i]

[url=https://ibb.co/xmbcqGX][img]https://i.ibb.co/xmbcqGX/Clipboard-Install-MM5-2.jpg[/img][/url]


[i]Impact MM5 INI-file[/i]

DBName=D:\OneDrive\Documenten\Mijn Databanken\[b][u]MediaMonkey 5[/u][/b]\MM5.DB

is changed to:

DBName=D:\OneDrive\Documenten\Mijn Databanken\[b][u]MediaMonkey 4[/u][/b]\MM5.DB

[quote=Peke post_id=473755 time=1603058749 user_id=213]
@Barry4679
I raised this with rest of devs for another review/revision.
[/quote]

Any update?

I noticed a new situation today.

[quote=Ludek post_id=473683 time=1602790777 user_id=7319]
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).
[/quote]

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

Hi,
Thx for update.

@Barry4679
I raised this with rest of devs for another review/revision.

I think I know why MM5 puts the MM5 ini file in the MM5 folder and the MM5 database in the MM4 folder.
I have multiple instances of MM4, so all .ini files have a line to specify the DB location, also in case this is the default folder.

When installing MM5, MM5 makes an MM5 folder and puts the MM5 .ini file there (copy of the MM4 .ini file).
The location of the MM5 DB is as specified in the copied MM4 .ini file.

This makes sense but is also confusing at the same time.

So I agree with the previous post: if there is an MM4 installation, the MM5 install process should allow for some options.
In addition to the previous post, MM5 should also ask where to put the MM5 .ini file and the MM5 DB: default location or to be specified.

By the way: I have solved the problems, MM5 works fine and everything is in it's right place.

[quote=willyvds post_id=473710 time=1602870809 user_id=23204]
I think this could be made a bit more user friendly.
[/quote]

I agree 100% with this understatement.

Forgive [url=https://www.dropbox.com/s/em90kymi6ycbfpn/import%20options%20during%20install.png?dl=0]the sketchy drawing[/url], but it needs something like this in the install program.

So we could decide whether to import settings and|or db data, and we had visibility and control over where we were importing from.

Hi,
Delete Mediamonkey.ini and MM5.DB from C:\Users\<user>\AppData\Roaming\MediaMonkey5\ then copy C:\Users\<user>\AppData\Roaming\MediaMonkey\MM.DB -> C:\Users\<user>\AppData\Roaming\MediaMonkey5\MM5.DB and start MediaMonkey while declining import Settings and Library.

It should not create C:\Users\<user>\AppData\Roaming\MediaMonkey\MM5.DB like you observed before. I tried several times and have not being able to replicate your behavior.

It helps if I run MM5 as admin. Then MM5 does find and convert the DB. It is still put in the MM4 directory however.
Then I can manually correct to folder of the DB and update the .ini file.

I think this could be made a bit more user friendly.

On my new PC, I first install MM4 and then MM5.

This is what happens when I install MM5
- MM5 makes a new directory AppData\Roaming\MediaMonkey5 and puts a copy of the MM4 database in it
- MM5 also puts a new, empty MM5.DB in AppData\Roaming\MediaMonkey (the MM4 directory !!)
- MM5 then seems to use the MM5 DB in the MM4 directory, and seems to ignore the copied MM4 DB

So there are a few problems
- it's fine that MM5 copies the MM4 files and puts them in a new MM5 directory
- MM5 should not make changes to the MM4 directory, and certainly not put an MM5.DB there
- and of course, MM5 should do something with the copied MM4 DB and use the correct DB in the correct folder

I have done a couple of reinstalls but this is what happens consistently.
Maybe I can solve it by using /inifile (haven’t tried) but this should’t happen in the first place.

If I then delete the MM5 folder and restart MM5 (as you suggested), MM5 does indeed ask if I want to use the MM4 data. If I say yes, I end up with the same result.

Let me know if you want me to try something.

If you already installed MM5 before MM4 then it won't ask.

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).

Did you install it on top of MediaMonkey 4 and/or as Portable Install?

I would have, if I was asked. But this simply didn't happen. MM5 just starts without asking about the library.

Did you tell MediaMonkey 5 to use the database file on the network: http://oldsvr.mediamonkey.com/support/index.php?/Knowledgebase/Article/View/45/0/changing-the-default-database-location

I have a new PC. First I installed MM4. The MM.DB and the .ini file are on a network drive so I referred MM4 to these files.
This works fine.

Now I also want to install MM5. Unfortunately, MM5 doesn't "see" my MM4 library.
I've tried to install it a few times, but MM5 simply starts from fresh.

Any ideas what goes wrong?

The error log is already there in MM5 (as I wrote above).

Also, MM5 is capable to read the overly long filenames (unlike MM4),
so I suppose that it already works fine for you with build MM 5.0.2158 ?
Or are you still seeing an issues with 2158+ ?

Let me add my vote in favor of logging the failed imports. I've been scanning my CDs into a library using EAC, and sometimes, EAC doesn't give the files filenames that work well under Windows-- sometimes they are just too long, or they put a period in the filename and MM doesn't recognize the file extension.

I worked out a method for finding the problem files-- it involved creating a list of all the files in a DOS window, and comparing that list to a MM database dump. Out of several thousand files, MM couldn't import ten of them because their filenames had problems. Some were too long, others had periods that screwed up the "file extension."

An error log after an import would be a huge help.