I have a huge data base ("MediaMonkey.mdb") that I used in my previous version (2.5). I installed now a beta version (v3.01.1116) and I see that the DB format is different. So I don´t know how to migrate previous format to new one. Please, help me! I don´t want to loose my database, I invested years on it!
Thanks in advance!
Migrate database 2.5-->3.0 triggers duplicates [4181]
Moderator: Gurus
Just install new version, it will automatically convert database and retain original DB (just follow install instructions and install to new directory - MediaMonkey3).
That said, i converted my huge database (41,000 songs) and while conversion was OK a rescan of my hard drive ended up with all my song titles being doubled - appears the new version doesn't import given the same keys or field format as the old/converted version. Not really practical for me, I have lots of time invested in rating and organizing my songs, not about to do it a second time
That said, i converted my huge database (41,000 songs) and while conversion was OK a rescan of my hard drive ended up with all my song titles being doubled - appears the new version doesn't import given the same keys or field format as the old/converted version. Not really practical for me, I have lots of time invested in rating and organizing my songs, not about to do it a second time
I have not had any problem with re-scanning files after importing my mm2 library (which is a huge nearly 400 megs).
MM3 should automatically ask to import your existing mm2 library if it can find it, you can also manually convert it using the dbupgrade.exe program in the mm3 program folder (wherever you installed mm3 to).
best to use a cmd prompt window in the mm3 folder and run it via that
MM3 should automatically ask to import your existing mm2 library if it can find it, you can also manually convert it using the dbupgrade.exe program in the mm3 program folder (wherever you installed mm3 to).
Code: Select all
dbupgrade.exe path\filename_of_old_MM2.mdb path\filename_of_new_MM3.dbNew script: 
Last.FM Node Now with DJ Mode!
Last.fm + MediaMonkey = Scrobbler DJ!
Tag with MusicBrainz ~ Get Album Art!
Tweak the Monkey! ~ My Scripts Page
Last.FM Node Now with DJ Mode!Last.fm + MediaMonkey = Scrobbler DJ!
Tag with MusicBrainz ~ Get Album Art!
Tweak the Monkey! ~ My Scripts Page
Duplicates in library
bob61,
If you delete your MM3 db, and install RC5, and then rescan, does it still duplicate your entire DB?
If yes, have you recently made any changes to your hard drive (the only reason I can think that this would happen is if MM 'thinks' that the tracks are on a new hard drive).
-Rusty
If you delete your MM3 db, and install RC5, and then rescan, does it still duplicate your entire DB?
If yes, have you recently made any changes to your hard drive (the only reason I can think that this would happen is if MM 'thinks' that the tracks are on a new hard drive).
-Rusty
Re: Duplicates in library
I've just installed RC5. I did a delete of the MM3.db file, fired up MM3 RC5, had prompt asking if I wanted to convert my files, said OK and then received an error message that there was a problem with the conversion. Had this happen with previous RC's as well. What I find is that even though I get an error message the DBUPGRADE.EXE continues to run in background and MM3.DB is built converted from the MM2.5 db. Now, maybe there's part of the problem - dunno. Certainly seems strange to get an error message that there's a problem yet the conversion continues.rusty wrote:bob61,
If you delete your MM3 db, and install RC5, and then rescan, does it still duplicate your entire DB?
If yes, have you recently made any changes to your hard drive (the only reason I can think that this would happen is if MM 'thinks' that the tracks are on a new hard drive).
-Rusty
What I've done this time is aborted the DBUPGRADE.EXE (using Windows Task Manager). Deleted the MM.DB3 file that was starting to be written and now I've running DBUPGRADE.EXE from command line prompt. Will see what happens.
I can tell you that when running RC3 and RC4 I'd get the duplicates after rescanning hard drive - NOTHING HAD CHANGED ON THE FILES - GUARANTEED. To convince myself I did a rescan in MM2.5 and confirmed there were no new files added - so scan under 2.5 results in no files added, RC3 and RC4 both duplicated the entire file list.
The DBUPGRADE.EXE process has been running now for about 10 minutes, should be finished with the conversion soon and I'll do a rescan with RC5 and let you know what happens.
Rusty - still having the same problem. Interesting observation - I have files that are on two drives. One set of files kept on my "C" drive all rescanned and didn't create any duplicates. Starting # of files = 2789, ending # of files = 2789 - GREAT! This may have been the case previously, I never bothered to worry about rescanning this small set of files - but found it interesting that the local drive scans fine.
The other set kept on my external "H" drive are in three sets of directories. I did a re-scan of one of these directories and not good. Starting # of files = 12136, ending # of files = 24396 - I now have more than twice the files I started with - UGH!
So noting that behavior is different between local vs. external drive, make any difference? Wouldn't think it should, but that's the only difference I see between the two sets of files.
I have reviewed the file listings - all files are exactly same path. I noted that some files have difference in their timestamp, these are files that were not in my MM2.5 DB (strange since I did a rescan of that directory earlier today - that's really strange, eh?). Most of the files appear to have same timestamp.
Here's screenshot, I've highlighted several examples - those with same timestamp in blue, those with different timestamps in yellow.
If you want I can zip up both sets of the databases if that would be of any benefit to you.
The other set kept on my external "H" drive are in three sets of directories. I did a re-scan of one of these directories and not good. Starting # of files = 12136, ending # of files = 24396 - I now have more than twice the files I started with - UGH!
So noting that behavior is different between local vs. external drive, make any difference? Wouldn't think it should, but that's the only difference I see between the two sets of files.
I have reviewed the file listings - all files are exactly same path. I noted that some files have difference in their timestamp, these are files that were not in my MM2.5 DB (strange since I did a rescan of that directory earlier today - that's really strange, eh?). Most of the files appear to have same timestamp.
Here's screenshot, I've highlighted several examples - those with same timestamp in blue, those with different timestamps in yellow.
If you want I can zip up both sets of the databases if that would be of any benefit to you.
try to zip or rar your mm 2 database and send to the support email (or if too large, via a u-send-it link or other file transfer website).
This way they can analyze your working mm2 database and try to figure out why its not importing correctly to mm 3.
This way they can analyze your working mm2 database and try to figure out why its not importing correctly to mm 3.
New script: Last.FM Node Now with DJ Mode!
Last.fm + MediaMonkey = Scrobbler DJ!
Tag with MusicBrainz ~ Get Album Art!
Tweak the Monkey! ~ My Scripts Page
Last.FM Node Now with DJ Mode!Last.fm + MediaMonkey = Scrobbler DJ!
Tag with MusicBrainz ~ Get Album Art!
Tweak the Monkey! ~ My Scripts Page
Would be glad to - but can you point in me direction as to how / where I find this log? If I need to recreate it not a problem as I still have my original DB file to convert from.PetrCBR wrote:Hi bob61.
Send me an debug log of your rescan after upgrade please (petr < att > mediamonkey < dott> com).
Regards,
Petr.
Just sent log file. Did a fresh copy of MM2.5 DB, ran DBUpgrade and then did a rescan of one of my file directories that creates the duplicate entries. Hope it helps.PetrCBR wrote:Hi bob61.
Send me an debug log of your rescan after upgrade please (petr < att > mediamonkey < dott> com).
Regards,
Petr.
debug logs and db copy
Bob61, I don't believe we've received any of the following from you:
-debug log
-MM 2.5 db
-MM 3.0 db (after upgrade and scan)
Please zip them up and send via you send it.
Thx
-Rusty
-debug log
-MM 2.5 db
-MM 3.0 db (after upgrade and scan)
Please zip them up and send via you send it.
Thx
-Rusty