I was batch renaming about 1,200 photos. I manually moved all the photos in chronological order and assigned ratings...some photos had five-star ratings, and others had no ratings. During the batch rename process, Bridge started to act wonky, then the spinning pinwheel. Finally, Bridge crashed. After restarting Bridge, all my files were entirely out of order, and hundreds that previously had five stars now had no rating and vice versa. I noticed that many files had also been assigned a '(1)' ending and some a 'copy' ending. I retraced my steps and realized that I chose a three-digit numbering sequence in the batch rename settings (beginning with 001), but I had over 1,000 photos to batch rename. I think this is what caused the problem. If you've ever watched your finder folder during a batch rename, you will know that Bridge runs a script that maybe creates a copy of the file, then renames and reassigns metadata, etc. I think that my choosing a three-digit ending for a four-digit volume of files may have created a sort of infinite loop that crashed Bridge while it was executing the batch rename - ruining my file order and metadata. Overall, just a huge mess, and an entire weekend of culling gone to waste. If this is the case, shouldn't bridge refuse to execute a script it knows will cause problems? Can this be salvaged?
7
Replies
AdChoices