Tweet
I'm not sure how the batch ripper currently handles this.
The simple way to deal with multiple matches (regardless of metadata source) in the batch ripper would be to pick the first one and/or the most common one.
Perhaps the most comprehensive way would be to store the metadata for all matches and provide a post-batch accounting/validating step where the operator goes through all multiple-match CDs and can choose which one is the correct one. This would automatically update file-internal metadata of the ripped track(s) and also would rename the path of the associated files to match that.
-brendan
The simple way to deal with multiple matches (regardless of metadata source) in the batch ripper would be to pick the first one and/or the most common one.
Perhaps the most comprehensive way would be to store the metadata for all matches and provide a post-batch accounting/validating step where the operator goes through all multiple-match CDs and can choose which one is the correct one. This would automatically update file-internal metadata of the ripped track(s) and also would rename the path of the associated files to match that.
-brendan
Comment