| Style Duplicates Manager is a program for managing Yamaha keyboard style files. | |
|
Help Topics
• Introduction • Search Method • Program Operation • Useull Features • Risk reducing • Legal Stuff • More information • Contact the Developer |
Contents
Introduction
This program operates with data files created with the PSR Style Database Application written by Peter Wierzba. The program will list duplicate style files found in one or two data files; and allow the user to delete these duplicate style files or to move or copy these duplicate style files to user selected folders. The duplicates list can be saved as a text file. Menu File | Save List to File.
Duplicate Search Methods
The program has four duplicate search methods:
Note that Method 2 and method 3 requires Data Files created with the "Export Style Data to CSV File" option in the File Menu of the "PSR Style Database" application. Method 1 and method 4 can use both data files created with the "Export Style Data" option and data files created with the "Export Style Data to CSV File" option. Warning for users of "PSR Style Database" version 4.x and newer:
Typical search time for a collection of 12,000 style files at a pc with a 1900 Mhz processor is:
Method 1
Theoretically 2 different style files can have the same checksum, but even in a collection of 10,000 style files this will have a very, very small probability.
Method 2
This additional method will reduce the very, very small probability of having two style files with the same fingerprint (CRC32 checksum) to an even smaller probability.
Method 3
If all these properties of style files are identical for two style files, these two style files may be duplicates, which have been revoiced or renamed or have had the tempo changed or have had the copyright notice changed or have had some other parameters changed. File size is typically from 15,000 to 45,000 bytes. This means that there are typically 30,000 different sizes. If some of the other properties are different (and they are!) there will be many more combinations. This means that two style files with these 7 properties equal will most probably be duplicates. However it is recommended to copy the duplicate styles listed to a disc (or to save the list to a file) and manually check the files.
Method 4
The number of first events can be set from 10 - 100. All valid main parts (A, B, C or D) can be used for comparison.
However it is recommended to copy the duplicate styles listed to a disc (or to save the list to a file) and manually check the files. Styles with no main part as selected are skipped. This method actually reads the style files. As the Main A part normally is found in the beginning of a style file and the Main D part normally is close to the ending (or not present at all) more off the file (or the whole file) must be read if search for Main D is selected. This has a big influence on the speed of the search process. Searching Main D compared to searching Main A will be app. 10 times slower.
Program Operation
Checking one Style file collection:
Checking two Style file collections:
Note:
Usefull Features
The "Select listed in CSF" button
Let us imagine that you have your primary style collection in i.e. c:\styles - and some subfolders to this folder.
Now you get 200 new styles. You store these in another folder i.e. c:\temp. Now you create a data file of this new collection. To find and seperate the duplicates in these two collections:
The "Select all but 1 of each" button
The "Unselect all" button
The "Clear List" button
Reducing Unwanted Operation Risk
This risk is reduced by:
Legal Stuff
Style Duplicates Manager ©2003-2010 Jørgen Sørensen. All Rights Reserved. You should carefully read the following terms and conditions before using this program. COPYRIGHT
DISCLAIMER
|