Output naming bug in CO7 exporting
tl;dr - when exported filenames get truncated after the 'dot'
-----------------------------------------------------------------------
i name my projects like this YYYY.MM.DD-PROJECTNAME
that means that filenames after import/tethered shooting look like this
YYYY.MM.DD-PROJECTNAME0001.NEF
YYYY.MM.DD-PROJECTNAME0002.NEF
YYYY.MM.DD-PROJECTNAME0003.NEF
...
i always set Output naming as [Image name] so naturally when exported to TIFF (or JPEG) in CO6 the resulting files would look like this
YYYY.MM.DD-PROJECTNAME0001.TIF
YYYY.MM.DD-PROJECTNAME0002.TIF
YYYY.MM.DD-PROJECTNAME0003.TIF
...
but now in CO7 something changed and with the same [Image name] in Output naming i get this
YYYY.TIF
YYYY 1.TIF
YYYY 2.TIF
...
PLEASE FIX IT!!!
-----------------------------------------------------------------------
i name my projects like this YYYY.MM.DD-PROJECTNAME
that means that filenames after import/tethered shooting look like this
YYYY.MM.DD-PROJECTNAME0001.NEF
YYYY.MM.DD-PROJECTNAME0002.NEF
YYYY.MM.DD-PROJECTNAME0003.NEF
...
i always set Output naming as [Image name] so naturally when exported to TIFF (or JPEG) in CO6 the resulting files would look like this
YYYY.MM.DD-PROJECTNAME0001.TIF
YYYY.MM.DD-PROJECTNAME0002.TIF
YYYY.MM.DD-PROJECTNAME0003.TIF
...
but now in CO7 something changed and with the same [Image name] in Output naming i get this
YYYY.TIF
YYYY 1.TIF
YYYY 2.TIF
...
PLEASE FIX IT!!!
0
-
I have never found anyone who would recommend using "." in a file name anywhere except between the intended name and the extension file type identifier. In fact going back to the early days of Windows the advice was to never use a dot on a file since many programs (Utilities and so on) would assume, rightly or wrongly, that the dot was always a name/extension separator. I often use a similar naming convention but mostly use underscore rather than dot.
Interesting that V6 has not caused any problems for you. That's quite positive I think.
Have you opened a support case for this? I ask because that is the best way to make your problem visible to the support team.0 -
The magic word is 'early days of Windows'. But it's 2012 so I expect my software to understand what the dot means. And thanks for the advice to open a support ticket. I'm gonna do it right now. 0 -
Thanks for the support case.
It's a verified bug and has been fixed in the upcoming service release.
😉0 -
Thanks, Drew.
It was driving me crazy =)0 -
[quote="NN13970" wrote:
The magic word is 'early days of Windows'. But it's 2012 so I expect my software to understand what the dot means. And thanks for the advice to open a support ticket. I'm gonna do it right now.
I agree - but it can still be a brave assumption! (And in some other things I deal with away from image processing it really helps quite often if one can rely on consistency of how the "." is used .... but that's another story)
Good to see the ticket looks like it will have worked out for you soon.
Grant0 -
Hopefully this is fixed. I was beta testing and put in a support case. I use imagename . camera counter and then rename the camera counter. The period terminates everything after it is processed, but will re name raw files. I just got word that they fixed the issue of the termination from the . on. Wait till the next update! 0
Post ist für Kommentare geschlossen.
Kommentare
6 Kommentare