If you fix/edit a kma on one computer and then move the corrected files to another computer just make sure they go into the same folder as the ones you are replacing and windows will overwrite the old ones. Hoster will play the new corrected kma's although the database won't show the corrections until you rebuild. If you put them in a diferent folder and try to merge (or rebuild for that matter), Hoster will list them in the duplicate diskid log and then ignore them because they are duplicates.
The ONLY time Hoster will change a bookid requires using the merge command. When using merge, when Hoster encounters a kma with a duplicate bookid (same bookid as another file with a different diskid). These are generally only possible if you import using both computers (to save time for example) and then combine the files together.
If you use just one computer to import and then transfer to the other, duplicate bookids will never occur.
Quote:
But the Manual specifically says that if you "rebuild" and it finds a duplicate I.D. that those songs will be put in a list. And, it also states that those songs may need to be "re-imported". It also suggests merging, saying that "re-building" is rarely necessary.
My concern is having to re-import songs because of the rebuilding process.
|
Again this only an issue when you are using 2 or more computers to import a bunch of disks to combine later. If you use the same diskid for 2 different disks you'll have to reimport one of them to correct the situation because you can't use the edit screen to change a diskid.
If you are importing with 2 computers and are anal about making sure they have different diskids (using the manufacturers diskid is the safest way of doing this) this will never be an issue.
If all you are doing is adding new songs then merge is all you need. If you are fixing songs on computer A and want to use merge to add them to computer B you can delete those songs on computer B (using the edit songs screen) and then you can use merge for those as well.
Sam