MM4 didn't import MM3 database?

[KEP]

I finally downloaded and installed MM4 (RC5 / b1459). I've sort of sat this beta out, as life was just to hectic otherwise, so I'm not fully up on moving from v3 to v4.

I guess I expected MM4 to just automatically import the old MM3 database. It didn't.

How can I force it to do that now, so I don't have to rescan and re-correct everything? (I think I had close to 100k tracks. <groan>)

Thanks!

[KEP]

Hmmm, okay, it seems if I copy the MM.DB file from where it was (on drive D:) to where MM4 wants it to be (Roaming profile on C:), MM4 then proceeds to import it. Is that the way it's supposed to work? Can I still have it off on drive D:, where it'll get backed up?

Thanks!

[Lowlander]

Yes, you can still customize the location of the database in MediaMonkey 4 the same way: http://www.mediamonkey.com/support/inde ... ticleid=46

[MattTown]

I also have MM3 on a D: drive to ensure that it all gets backed up, and have had previous re-installations trash "date added" and playcounts.

Is this understanding of the MM3 - MM4 upgrade process for a D: drive installation correct?

Close MM3
Download MM4
Install MM4 to the preferred location (eg D:\MM4)
Close MM4
Relocate the MM3 db to an appropriate place in the MM4 installation and upgrade the MM4 mm.ini file as per the KB article
Start MM4

Assuming this is right, do I have to do anything else to get the previous MM3 db contents gets imported without or corruption?

Thanks

[KEP]

Yes, you can still customize the location of the database in MediaMonkey 4 the same way: http://www.mediamonkey.com/support/inde ... ticleid=46

Ah, great! Bad assumption on my part, I guess. When MM4 didn't do that automatically, it threw me. Later on I noticed MM4 didn't seem to take any MM3 settings into account, other than my license status.

Thanks...

[Lowlander]

I think it should, but some changes might have been made for fixing upgrade issue in the latest builds. Did you install MM4 over MM3?

[KEP]

I think it should, but some changes might have been made for fixing upgrade issue in the latest builds. Did you install MM4 over MM3?

Yeah, sure did. It seemed to lose a lot of the settings. Database location, folders to track, Auto Organize patterns, etc. Nothing tragic, but it was really more like a fresh install than what I might've expected.

[KEP]

I think it should, but some changes might have been made for fixing upgrade issue in the latest builds. Did you install MM4 over MM3?

Yeah, sure did. It seemed to lose a lot of the settings. Database location, folders to track, Auto Organize patterns, etc. Nothing tragic, but it was really more like a fresh install than what I might've expected.

Repro'd on another system. Installing MM4 over MM3 results in a totally fresh install. The old INI is wiped, the old DB is ignored. Shouldn't there be an option to use as many of the existing settings as possible?

[Lowlander]

Did you do a portable install?

[KEP]

Did you do a portable install?

No.

EDIT: May not have mentioned before. Running Windows 7 x64 on all affected systems, so far.

[Lowlander]

I presume it should have picked up DB and settings. Seaming same issue here: viewtopic.php?p=318399#p318399

[KEP]

I presume it should have picked up DB and settings. Seaming same issue here: viewtopic.php?p=318399#p318399

Similar issues, though hopefully just the technical ones.

I certainly got the prompt to steal associations. And could rant about that, were I inclined. (I really hate "opportunities" to screw up system settings, that can be chosen with one too-quick click! That should really be a far more conscious decision. It's nearly as bad as Flash trying to sneak McAfee past you! But I digress. )

Doesn't sound like that poster was offered the opportunity to import the old DB either. So, is this something that's just supposed to happen by default, or is it like the associations and something you need to initiate? My instinct, as a developer, would be to create backups of (or at least ask to) both the DB and INI(s), to facilitate easy rollback.

Still trying to fully understand the utility of these newfangled collections, and your post over there was the first time I ran across "Types", so even more to look up now. Will get there, though. Thanks!

[Lowlander]

It should upgrade the DB automatically and should keep a copy of your MM3 DB as well.

[KEP]

It should upgrade the DB automatically and should keep a copy of your MM3 DB as well.

Two upgrade installs, Zero upgraded databases.

[nohitter151]

It should upgrade the DB automatically and should keep a copy of your MM3 DB as well.

Two upgrade installs, Zero upgraded databases.

If you've moved the database from the default location, the automatic upgrade wouldn't take place. Likewise installing MM4 in portable mode would not upgrade the MM3 database. If neither of these scenarios do not apply, I could not say why the upgrade didn't take place, but I can confirm that it's working fine for my PC and that the upgrade process is working for several other users who have reported so via the forum and support.

If you need to manually upgrade the DB, you can do so as described in the KB:
http://www.mediamonkey.com/support/inde ... ticleid=57

1) Go to the command prompt, and switch to C:\Program Files\MediaMonkey

2) Type dbupgrade.exe old_MM_database.DB new_MM_database.DB
where old_MM_database.DB is the location of the old database and new_MM_database.DB is the location where MM should generate the new database.