Lens correcting tool
It seems that the lens correcting tool dont load lens data any more...?!
In previous versions of CO1 it worked, but in 6.1 and 6.1.1 the tool dont load data from my NEF files...?!
No Focal length nor aperature is shown..?
-Any one experienced this 😕
Windows 7 Ultimate x64 and Nikon D3 NEF files.
I think I make a support case of this problem!
/Per
In previous versions of CO1 it worked, but in 6.1 and 6.1.1 the tool dont load data from my NEF files...?!
No Focal length nor aperature is shown..?
-Any one experienced this 😕
Windows 7 Ultimate x64 and Nikon D3 NEF files.
I think I make a support case of this problem!
/Per
0
-
How do you do Per,
I wanted to let you know that I also sent in a Tech Support for this observation. I too noticed this. I've been using C1PRO since 3.7.8 and I remember 4 PRO and 5 PRO displaying the lens' focal length and aperture values. Now, on my Canon 7D, 30D, and Nikon D40X files, they both default to "--."0 -
Anything new about this issue?
It seems to be the same problem with ARW-files (Sony).
I use NEF and ARW, and the f-stop and focal length is presented below the image viewer, but I can't even key them in.
Br. Eigil0 -
Create a support case and provide some RAW files please.
We'll be able to tell where that information is stored in the file and why it is not read. If possible, we can adjust for it or find a workaround.0 -
Why are the fields blocked?
The information is at hand. CO1 has already written f-stop and focal length below the display.
It would be easy to key data in, if the fields were just open.
Actually the fields look as if they are open, i.e. "-- mm" is not greyed out. It's just impossible to write to them.
I think it has been possible earlier. As it is now, you can't get anywhere.
Br. Eigil0 -
Eigil,
Please create a support case and provide a RAW file so we can look into the issue further.
The fields cannot be edited as this would be a bit counter to the idea of Metadata, that being a relatively reliable record of your Captured data.0 -
Hi Drew,
For your information: Support case 86395.
Br. Eigil0 -
This problem seems to be corrected with 6.2.
Br. Eigil0
投稿コメントは受け付けていません。
コメント
7件のコメント