Am using BridgeCS5 (Windows7) to Batch Rename (either during download from Lexar Card Reader using Bridge, or during download from Canon 7D with Cable via Bridge- or to batch rename files already in a folder within Bridge)
when I use YYYYMMDD_HHMMSS_milliseconds, milliseconds are set to 000 (thus photos are not in order necessarily if photos taken during burst mode), yet if I use YYYYMMMDD_HHMMSS_milliseconds, it sorts properly.
Have tried this multiple times, and it is *usually* reproducable - I did a batch rename on a subset of photos, and Bridge got the rename right, but then did a batch rename on the entire lot of photos, and preview said it would set the milliseconds to 000, even on the photos it got right in the subset-experiment
I need to use numeric month designation (MM) for proper file sequencing, as alpha (MMM) puts months out of chronological order.
I did NOT notice this problem in the past (say, 3-4 months ago) but it is possible I missed it.
I am NOT syncing multiple cameras or trying to integrate files from multiple cards.
BridgeCS5 is up to date with all patches.
(I checked the EXIF data on the files themselves, and it is correct, the milliseconds denote the proper image sequence, the camera is recording the files to card in correct sequence - in fact, exloring the card, all images are in proper sequence)
By having files renamed (without a sequence number added to the batch rename configuration) with milliseconds to 000, not only are they out of order, but Bridge is willing to have several files with the same exact name.
I'd be interested in a solution that allows me to continue using Bridge only for my workflow.
thanks - stir