![]() I had to avoid newer versions of Bridge because this was a hassle. Batch Rename should automatically pick 031945, like it would for over a decade before, but nope, image 7 shows it picked 31953.įix this so it works like it used to. Image 6 shows the next batch, which starts at 1945. 31943? Where di that come from? In the 5th image I had to enter the correct number, 031937. The 4th image shows what Bridge thinks the next number should be. The third image shows the results highlighted. I'm renaming both JPG and CR2 files, so the count should increase by 6, so when I select the next batch of images, I should see it fill in 131937, which would be the next number since the last renamed file is numbered 0311836. ![]() ![]() In the second image, I have to enter 31931 to get the correct sequence number to match the original file number (1931). ![]() In the first image, I have the files highlighted that I want to rename. Now it picks some random number that's of no use to me. When I'd go to rename the next files, G to M,, the Batch Rename would automatically apply 007 as the next starting number, so the first renamed file would be img007. Say, files A to F are renamed to img xxx, I would get img001 to img 006. When batch renaming files, Bridge used to automatically advance the sequence number to the next number after the current sequence, which let you select the next group of images and they would automatically get the next numbers in the sequence.
0 Comments
Leave a Reply. |