Is there some way to get PSU to perform a rounding function so the '.299999232' gets rounded to '.3' ? Then my worries would all disappear. I want my rename rule to be robust enough that I get the same result when applied to both the NEF and the derived JPG. For example, for the above image I get the following results from exiftool: The -b option tells exiftool to output data in binary format and extract.jpg is the destination file of the new image created. The NEFs seem to record the fractional part of seconds differently to the derived JPG. Just in case you have a corrupted image, you can attempt extracting preview image or even the thumbnail using this command: exiftool -b -PreviewImage IMG.CR2 > extract.jpg. The milliseconds is where my problem lies. Note the funny string manipulation of the milliseconds ( I could have used 'left' rather than 'mid' but I was experimenting). SGH_%yyyy-%mm-%dd_%hh%nn%ss.%zzz.%FileExtension
Having added a D7100 I regularly shoots bursts and also need to deal with results from a 'two camera shoot', So I figured I would add fractional seconds and also the camera model: The burst capability of the D50 in RAW was limited so I rarely produced multiple shots per second. This worked most of the time although I would occasionally get a (001) appended. SGH_%yyyy-%mm-%dd_%hh%nn%ss.%FileExtension For the last few years with my D50 I have used the rule: I've been playing around with renaming rules for a while with the aim of getting something that I can guarantee to be unique across my whole collection and (hopefully) remain unique if I add in third party files.
0 kommentar(er)
