- playing history (the Played table and Playcount + LastTimePlayed fields in the Songs table),
- playlists (auto-playlists and/or static ones in Playlists and PlaylistSongs tables),
- filters [MM3 db] / collections [MM4 db] and views (Filters, Views and NodeViews tables), and/or
- specified fields from the Songs table (e.g. Artist, Title or DateAdded field, however for some fields some another tables would be updated as well, e.g. Genres and GenresSongs if you specify Genre for restore).
This add-on could restore/synchronize data for all tracks in the current database or just filtered or selected ones. It could import/export data even from/to the backup file which is not a copy of the current database, i.e. the current database could be created from the ground after the last backup, as soon as they contain matched tracks.
If you have an adequate backup file, this add-on could be used as Undo tool as well. Let say that you have edited some tag/field in bunch of tracks and after that you have changed your mind. Nothing to worry: just select files that are affected, specify which tags you want to restore and the add-on will import that data from the specified backup file into the current database. Also, this add-on could transfer data from corrupted databases into the new, fresh ones in most cases.
If you want to discus about this add-on, you could visit its related MediaMonkey forum thread.
You could also take a look on my other add-ons for MediaMonkey.
- v3.1.8 - 2019-11-22
- Fixed: error on export/import playlists to/from MM4.1+ databases when the option Clear Playlists & PlaylistSongs tables first is turned off.
- v3.1.7 - 2017-07-16
- Fixed: restore of playing history when Clear Played table is enabled.
- v3.1.6 - 2016-12-22
- Improved: speed of some SQL operations;
- Fixed: many things.
- v3.1.3 - 2015-06-22
- Fixed: some things.
- v3.1.2 - 2013-08-31
- Fixed: error when restoring both Static and AutoPlaylists with Clear Playlists option turned on, if backup DB is from MM 4.0 and current DB is from MM 4.1 or vice versa;
- Fixed: finding of matched tracks in some cases.
- v3.1.1 - 2012-05-31
- Fixed: error on restoring auto-playlists with the condition: Tempo/Mood/Occasion/Quality "is" ... (broken since v3.0);
- Fixed: error with Update tags in files too.
- v3.1 - 2012-04-04
- Added: option Clear Filters table first (also Views & NodeViews for MM4 db);
- Added: option to import/export Bookmark, Start Time, Stop Time, Skipped # and Type fields [MM4];
- Fixed: error with Update tags in files as well.
- v3.0.2 - 2012-01-25
- Fixed: error on import/export of filters when Filter table is empty.
- v3.0.1 - 2012-01-12
- Fixed: import/export of filters.
- v3.0 - 2012-01-09
- Added: possibility to export data to the external (backup) database file;
- Added: possibility to make a backup of the current database;
- Added: option which allows export/import of filters [MM3 db] / collections [MM4 db] and views;
- Added: option Update tags in files as well which could be used only on import;
- Added: new matching test for path without drive letter, first folder & extension (e.g. if the path is c:\Music\Rock\Pink Floyd\Time.mp3, then only Rock\Pink Floyd\Time would be compared) AND SongLength;
- Changed: calculation of PlayCounter if Clear Played table option is turned off, it is now maximum of 2 values(PlayCounter before import + number of non-existent plays of matched tracks from backup, backup PlayCounter);
- Improved: speed in some cases.
- v2.1.3 - 2011-12-09
- Fixed: restoring playlists with some corrupted databases and some MM4 "normal" (?) ones.
- v2.1.2 - 2011-11-15
- Fixed: auto-playlists with the condition: Album "equal/doesn't equal" ..., when backup is not a copy of the current database.
- v2.1.1 - 2011-08-04
- Fixed: restore of metadata stored in the Songs table only (multi-item fields linked to several tables was not affected).
- v2.1 - 2011-07-19
- Added: possibility to restore playlists even when Restore data only for filtered/selected tracks options are turned on (playlists would be restored for all tracks anyway);
- Fixed: error when restoring playlists with Clear Playlists table... option turned on when importing data from MM3 backup into MM4 db or vice versa;
- Fixed: dates when importing playhistory from MM4 backup file into MM3 database.
- v2.0 - 2011-07-17
- Added: possibility to restore specified fields from the Songs table (Artist, Album, Title, ...);
- Added: option to restore only selected tracks;
- Added: option to restore only tracks from the specified filter [MM3] / collection [MM4];
- Added: option to restore auto-playlists or static playlists independently;
- Added: possibility to import data from MM3 backup file into MM4 database and vice versa;
- Added: more detailed information about the execution time and progress;
- Improved: speed (in some cases drastically);
- Fixed: error when restoring playhistory with Clear Played table... option turned on [MM4];
- Fixed: program hangup with some filters;
- Fixed: program hangup with some auto-playlists having very long tags;
- Fixed: auto-playlists with the condition: Playlist "is/is not" ..., when backup is not a copy of the current database;
- Fixed: static playlists with incorrectly added/missing tracks when backup is corrupted.
- v1.4.2 - 2010-09-03
- Fixed: problem with some auto-playlists when backup is not copy of the current database.
- v1.4.1 - 2009-11-16
- Fixed: error when database contains multiple playlists with same name on the same folder level.
- 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).
- v1.3 - 2009-08-26
- Added: extra matching test for FileName.ext/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.
- v1.2 - 2009-08-23
- Added: option to restore Date Added field;
- Added: option to restore only filtered tracks;
- Added: option to merge/clear playstats before restoring data;
- Added: display of the number of tracks in the current database matched to backup.
- v1.1.2 - 2009-08-21
- Fixed: work with multiple tracks with same checksum.
- v1.1.1 - 2009-08-21
- Fixed: work with databases without track checksums.
- v1.1 - 2009-08-21
- Added: matching test for track checksums, i.e. track from current database is same with the track from backup database if checksums are same even if their paths are different;
- Improved: speed drastically (~60 times faster);
- Fixed: matching test for paths now use serial number of disc as well to avoid situations with tracks with same filename, but different drive (c:\track.mp3 and d:\track.mp3 was incorrectly manipulated as one track).
- v1.0 - 2009-08-19
- First public version.
here you could find its location depending of the version of MediaMonkey and Windows.
The next important thing with this add-on is that it could restore data only from/to the backup (external) database file, but it cannot restore the current (active) database with itself. Which means that you need to have the backup file before you get some problem with the current database and nothing can be done if you don't have it.
This version of the add-on could import/export data only if there are tracks in the backup file that are matched with the tracks in the current database, i.e. if they have the same:
1. full path (folders\filename.extension) OR
2. checksum (made after click on Files To Edit / Duplicate Content) OR
3. filename with extension AND FileLength AND Album AND Year AND TrackNumber OR
4. path without drive letter, first folder & extension AND SongLength OR
5. filename without extension AND SongLength AND AlbumArtist AND Album AND Year AND TrackNumber.
The ExtraMatchTests key in the MediaMonkey.ini file determines which criteria will be used to match files between the backup and current databases (you can find more info about that key in the Additional INI keys section). These criteria are cumulative, e.g. if you choose the 4-th one, all previous testing will be executed before that one.
The 2-5. criteria cover situations with modified file locations after backup. The 4-5. criteria further cover situations with different media formats in the backup and current databases, e.g. if the backup database contains .flac tracks and the current one contains .mp3 tracks instead, but with the same filename, song length and other mentioned tags. The 2-5. criteria have the true condition only if there are exactly two matched tracks - if there are three or more tracks matched with those criteria, they would return the false condition and such tracks should have the same full paths to be considered as matched.
The data for tracks that are not matched between current and backup database files will not be restored. This version of the add-on allows matching only one-to-one file, so if you have duplicates in the database (records with the same paths), only the first one will be restored (well, you should avoid having duplicates in the database anyway).
The Restore/Synchronize Database dialog box can be opened using its corresponding item in the Tools / Scripts menu. The backup (external) database file should be specified first in the Backup database file text box. The data will be transferred (restored) from that file to the current database if you choose Import or they will be transferred from the current database to the specified backup file if you choose Export. The backup database file should be different than the current database file, i.e. you cannot specify the current database file in this text box.
Immediately after you specify the backup file, the add-on will start comparing the backup with the current database and that process could be very slow, especially with the higher values of the ExtraMatchTests key . So, if you have a large database with too many records, it is recommended that you have specified the lower ExtraMatchTests value before you start the program. The remaining options in the dialog box determine which data will be restored and for which files.
You could choose which files should be restored using two Restore playhistory/metadata only for options. These options are mutually exclusive, i.e. you could use one of them, but not both. With the option Restore playhistory/metadata only for files in collection [MM4] (Restore playhistory/metadata only for filtered tracks [MM3]) you could choose to restore data only for matched files in the specified collection.
If you turn on the option Restore playhistory/metadata only for x selected file(s) [MM4] (track(s) in MM3), data will be restored only for matched files that belong to the group of files that are selected in the main filelist.
The Restore playhistory option should be turned on if you want to restore the playing data in the Played table and the PlayCounter/LastPlayedDate fields in the Songs table for matched files. If you run this add-on twice with the same backup file, and if you choose this option again, it will not add the play history twice - the add-on will compare those data from the backup and current database files and if they are same it will skip them, i.e. it will add (merge) only the new playing data.
However, if you turn on the option Clear Played table & Playcount/LastTimePlayed fields first, the add-on will remove all playing data from the Played table for matched files from the target database before restoring them from the source database. Also, the PlayCounter/LastPlayedDate fields in the target Songs table will be based only on the data from the source database in that case. So, be careful when using this option.
You could restore both Static playlists and/or AutoPlaylists using the corresponding Restore options. However, some type of playlists will be restored even if you do not select them if they are parents of the playlists of the chosen type. For example, if you have some auto-playlist that has the child static playlists, that auto-playlist will be restored if you select Static playlists even if the AutoPlaylists is turned off.
The option Clear Playlists & PlaylistSongs tables first is enabled only if you have turned on both Static playlists and AutoPlaylists check boxes. If you have that option turned on, the add-on will clear the Playlists and PlaylistSongs tables in the target database completely before restoring playlists from the source database. Please be very careful when using that option! If you turn it off, the add-on will merge the playlists from the source database with the existing ones in the target database, i.e. it will restore only playlists that don't exist in the target database. The content of playlists in the target database which have the same names as the playlists from the source database (within the same parent playlists, i.e. in the same hierarchy) will remain unmodified.
Collections/Views (Filters in MM3)
The option Restore collections/views should be turned on if you want to restore collections and views in MM4, or filters in MM3. If you turn on the option Clear Filter table first as well, the collections/views will be completely cleared in the target database before restoring the collections/views from the source database. Please be very careful when using that option! If you turn it off, the add-on will merge the collections/views from the source database with the existing ones in the target database, i.e. it will restore only collections/views that don't exist in the target database.
You could restore the selected metadata for matched files if you turn on the option Restore metadata in Songs & other tables, in which case the add-on will update Songs table and other tables that are connected to it by related fields, e.g. Artists or Genres.
The option Update tags in files too (only on Import) allows updating of tags in media files for the corresponding metadata in database on Import. If you forget to turn on that option, but you want to have updated tags in files as well, after restoring of metadata in the database, you could choose the Synchronize Tags option of the program.
The remaining check boxes on the bottom of the dialog box allow you to choose which particular metadata you want to restore, e.g. Date Added, Artist...
Info line and commands
The information line on the bottom of the dialog box displays the total number of files in the backup (external) and current databases, as well as the number of matched files (the numbers inside parentheses are the number of matched files for each matching criterion).
You could click the Backup button if you want to make a copy of your current database file using the destination path specified in the Backup database file text box.
After you have adequately set all previously mentioned options, you could click the Export button if you want to transfer data from the current database to the specified backup file, or you could click the Import button if you want to transfer data from the specified backup file to the current database. Then just wait for the add-on to finish, it could be rather slow and maybe will need several minutes with larger databases.
The MediaMonkey.ini file is stored in the c:\Documents and Settings\User_Name\Application Data\MediaMonkey\ folder for MM4 and Win7. You could find the location of the .ini file depending of the version of MediaMonkey and Windows here. If you want to modify the mentioned keys in it using e.g. Notepad, you should do that with closed MediaMonkey application.
If you have upgraded computer or changed hard disk and if you copied all media files to it keeping the same folder structure, then you could first try to transfer MM database to it and update it using the Update Location of Files in Database add-on instead since it is a way faster and simpler to use.
If you choose any of the Clear ... options, the related tables in the target database will be deleted first after applying the Export/Import command, as it is mentioned in the Usage section! If you want to merge data, you should leave those options unchecked.
DisclaimerThis software is provided 'as-is', without any express or implied warranty. In no event will the author be held liable for any damages arising from the use of this software.
www.virustotal.com/en/ site, you will see that it is safe tested by 54 popular anti-virus engines; the only one reporting a worm in it is F-Secure.