herman
February 28th, 2005, 03:14 PM
Dear Chris,
Using DLPro 1.6.2 I encountered something unexpected.
I assume that the %r token in renaming files would read the image number from the EXIF data. Apparently it reads the OS file name though.
An example may make things clear...
I have a picture with filename 050114_155540_1.jpg (this is the year/date/time series, _1 indicating the first picture in that timeslot).
When I rename it using DLPro with just the %r token the resulting file is called 114.jpg, ie. the last three digits of the year/date combination.
When I do the same rename operation using BBPro 1.0.2 batch rename the file is renamed to 2420.jpg, the 2420 sequence being part of the image serial number (in this case 124-2420 as read from the EXIF information).
I run these programs on a WinXP prof box, all service packs and patches applied.
Just wondering if this is a bug or a misunderstanding on my side....
Best regards,
Herman.
Using DLPro 1.6.2 I encountered something unexpected.
I assume that the %r token in renaming files would read the image number from the EXIF data. Apparently it reads the OS file name though.
An example may make things clear...
I have a picture with filename 050114_155540_1.jpg (this is the year/date/time series, _1 indicating the first picture in that timeslot).
When I rename it using DLPro with just the %r token the resulting file is called 114.jpg, ie. the last three digits of the year/date combination.
When I do the same rename operation using BBPro 1.0.2 batch rename the file is renamed to 2420.jpg, the 2420 sequence being part of the image serial number (in this case 124-2420 as read from the EXIF information).
I run these programs on a WinXP prof box, all service packs and patches applied.
Just wondering if this is a bug or a misunderstanding on my side....
Best regards,
Herman.