Photo rename ignores SubSeconds when 00
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Rapid Photo Downloader |
Fix Released
|
Medium
|
Damon Lynch |
Bug Description
I shoot with a Nikon D700, which can take 8 frames/second.
Viewing those frames in order is key, and sometimes I use
various software and web sites that know how to sort by name,
but don't know how to sort by EXIF date to the sub-sec.
So I have Rapid Photo Downloader's Photo Rename
configured to use the Subseconds field like so:
YYYYMMDD_
resulting in file names like this:
20121223_
where subseconds is 33 above.
But if it were 00 msec, RPD would ignore the SubSeconds filed, creating this file:
20121223_112455.NEF
instead of the expected
20121223_
This can cause sorting by name ( one of the reasons I re-name files in the first place) to give the wrong order:
20121223_
20121223_112455.NEF
instead of the expected:
20121223_
20121223_
Related branches
Changed in rapid: | |
status: | New → In Progress |
summary: |
- Photo Rename ignores SubSeconds when 0 + Photo rename ignores SubSeconds when 00 |
Changed in rapid: | |
status: | In Progress → Fix Released |
Oh, and I'm running version 0.4.5
on 64-bit Fedora Core 16 Linux