GuyScharf
December 29th, 2005, 03:46 PM
I am using DLP 1.7. Files are from Nikon cameras (D70, D200), so have file names like DSC_0123.NEF or _DSC0123.NEF.
I want to rename the "DSC" to indicate the specific camera. So, using the D70 as an example, I set the file name to be %T8_%r4. This changes DSC_0123.NEF to D70_0123.NEF, which is exactly what I want.
Two problems:
1) I also place the file name in the IPTC Object Name field. If I put %T8_%r4 in this field, I end up with D70_01234 in the field. The .NEF isn't there, which is fine. But where did that extra "4" come from???
However, if I use %r instead of %r4, I get the desired result (D70_0123).
This appears to be a case of %r4 not working as documented for IPTC data.
However, since I always have exactly 4 digits (at this time anyway, with Dxx_0123 format), it appears that %r and %r4 are the same thing?
But see last point to derail this solution in the general case. :)
2) If I set a Nikon camera to use AdobeRGB color space, it changes the form of the file name from DSC_0123.NEF to _DSC0123.NEF. I'd like to preserve that leading vs trailing underscore. E.g., I want to rename DSC_0123 to D70_0123 and _DSC0123 to _D700123.
How might I do that?
3) The D200 also allows the user to change the DSC string to just about anything else. I might want to change mine to be "D20" to indicate the camera in the file name. That results in file names like D20_0123, which works fine with %T8_%r token string. However, with AdobeRGB, the file name generated by the camera would be _D200123, and %T8_%r becomes an undesirable long name (I think it picks up 5 digits?).
I think this argues for making the %r4 token work as expected in the IPTC data.
Thanks!
Guy
I want to rename the "DSC" to indicate the specific camera. So, using the D70 as an example, I set the file name to be %T8_%r4. This changes DSC_0123.NEF to D70_0123.NEF, which is exactly what I want.
Two problems:
1) I also place the file name in the IPTC Object Name field. If I put %T8_%r4 in this field, I end up with D70_01234 in the field. The .NEF isn't there, which is fine. But where did that extra "4" come from???
However, if I use %r instead of %r4, I get the desired result (D70_0123).
This appears to be a case of %r4 not working as documented for IPTC data.
However, since I always have exactly 4 digits (at this time anyway, with Dxx_0123 format), it appears that %r and %r4 are the same thing?
But see last point to derail this solution in the general case. :)
2) If I set a Nikon camera to use AdobeRGB color space, it changes the form of the file name from DSC_0123.NEF to _DSC0123.NEF. I'd like to preserve that leading vs trailing underscore. E.g., I want to rename DSC_0123 to D70_0123 and _DSC0123 to _D700123.
How might I do that?
3) The D200 also allows the user to change the DSC string to just about anything else. I might want to change mine to be "D20" to indicate the camera in the file name. That results in file names like D20_0123, which works fine with %T8_%r token string. However, with AdobeRGB, the file name generated by the camera would be _D200123, and %T8_%r becomes an undesirable long name (I think it picks up 5 digits?).
I think this argues for making the %r4 token work as expected in the IPTC data.
Thanks!
Guy