Restore/Synchronize Database 3.1.2 (2013-08-31) [MM3+]

[B.B]

Can't get this thing to work.

I read somewhere that MM does the UNC tango better than the mapped drive slow fox, and since my database have been with me since...well..forever..i decided it is time to start over with a fresh DB.

Previously the path to my music where mapped as Z:\ . I renamed the DB and reinstallede MM to get a fresh database, this time i added the tracks from the UNC path (\\192.168.1.99\music\) . Pointing the script to the old database brings this picture up:



Nothing is imported.

Am i missing something?

EDIT...Well..it turns out that i were missing something..

"The requirement is that Path fields <......> are same in the backup and current database files"

Bummer....i guess ill be staying with the old DB..

[nynaevelan]

If you still have the old db available, move the files to the new path that you want. Or if you don't, move them to the old file path and then you can move them back when you restore your data. Ever since I created a new db, my MM has been much faster, I guess I had a lot of junk in mine that was slowing it down.

[ZvezdanD]

EDIT...Well..it turns out that i were missing something..

"The requirement is that Path fields <......> are same in the backup and current database files"

Well, I could add some more criteria for matching tracks, but I suppose it would slow down the execution. For example, I could add the matching for Artist, Title, Album, FileLength, Bitrate, ... and Filename.ext without full path. What do you think about that? Which metadata should be alternately compared if previous fails? By the way, I suggest generating of checksums (Files to Edit / Duplicate Content).

[nynaevelan]

I would suggest filename.ext after checksum.

[ZvezdanD]

I would suggest filename.ext after checksum.

Yes, but it is not enough, because there could be many tracks with same filename.ext. It should be a combination of several metadata.

[nynaevelan]

What combination would make it unique?? For example, I have exact copies of all my tracks in wma, mp3 and m4a. They all have the same bitrate. I supposed file size would work.

[ZvezdanD]

What combination would make it unique??

I don't know, I expected to hear that from you.

For example, I have exact copies of all my tracks in wma, mp3 and m4a. They all have the same bitrate.

Are you sure about that? Are you using CBR? If you are using VBR it is very unlikely that they have the same bitrate. What is a point of your switch from mp3 collection to the wma or m4a if you keep the same bitrate? Those audio formats have advantage over mp3 because you could get smaller bitrate (and file size) for the same quality.

I supposed file size would work.

Maybe, but you suggested filesize.ext, not file size. By the way, there is also a possibility to have two different tracks with same file size, so it should be also in combination with some another metadata. Maybe filename.ext and file size.

[nynaevelan]

For example, I have exact copies of all my tracks in wma, mp3 and m4a. They all have the same bitrate.

Are you sure about that? Are you using CBR? If you are using VBR it is very unlikely that they have the same bitrate. What is a point of your switch from mp3 collection to the wma or m4a if you keep the same bitrate? Those audio formats have advantage over mp3 because you could get smaller bitrate (and file size) for the same quality.

It is my intention to switch from mp3 to another format, but I haven't gotten around to testing the sound quality of them yet. And I do not know enough about bitrates and CBR/VBR to use something different yet. To tell you the truth, this isn't high on the priority list, so until I get around to it I am making duplicate copies of all tracks until I am ready for it.

I supposed file size would work.

Maybe, but you suggested filesize.ext, not file size. By the way, there is also a possibility to have two different tracks with same file size, so it should be also in combination with some another metadata. Maybe filename.ext and file size.

I was thinking filename and filesize, that should be unique enough.

[ZvezdanD]

It is my intention to switch from mp3 to another format, but I haven't gotten around to testing the sound quality of them yet. And I do not know enough about bitrates and CBR/VBR to use something different yet.

Yes, I did understand that your intention is to switch from mp3 to another format, but I don't understand why you are doing that if it is not because of audio quality or file sizes. I think you should first decide which audio format and bitrate you want to keep considering its quality, then you could go making duplicates.

I was thinking filename and filesize, that should be unique enough.

It just comes to my mind that some users make duplicates for different albums (e.g. official and compilations) by simply copying files, so those two criteria (filename and filesize) could not be enough. Maybe in addition of album name and track number.

[nynaevelan]

Audio quality is not the only factor, the file format also has to be compatible with my portable player, because I am not interested in doing any on-the-fly conversions and my player is based on playlists. So it is still a work in progress....

[ZvezdanD]

There is a new update: v1.3 - 2009-08-26
- Added: extra matching test for FileName/FileLength/Album/Year/TrackNumber fields, i.e. track from current database is same with the track from backup database if all those fields are same, even if their paths and checksums are different.

[B.B]

30.000 tracks, 14.31 sec. later everything is restored...I'm impressed


Rock On....

[ZvezdanD]

There is a new update: v1.4 - 2009-08-28
- Added: option to restore playlists (both auto-playlists and static ones);
- Added: option to merge playlists (if Clear Playlists... option is turned off);
- Added: extra matching test for FileName/SongLength/Artist/Album/Year/TrackNumber fields (useful if audio format of tracks is different between backup and current database).

[Teknojnky]

Excellent, I will have to give this a try this weekend after I rescan a new library db.

[nynaevelan]

There is a new update: v1.4 - 2009-08-28
- Added: option to restore playlists (both auto-playlists and static ones);
- Added: option to merge playlists (if Clear Playlists... option is turned off);
- Added: extra matching test for FileName/SongLength/Artist/Album/Year/TrackNumber fields (useful if audio format of tracks is different between backup and current database).

Wow, I am going to have to play with this with a new database, you just combined three steps into one.