D500
Just installed 10.1 and it still doesn't recognize my Nikon D500 NEF's.
Regards, John
Regards, John
0
-
It seems to be a supported camera (it appears in the list in Capture One when I look). Perhaps you should raise it with support.
Ian0 -
No problem at all with my D500 NEFs.
But there might be problems with small NEFs or compressed NEFs that might not be supported (if I remember correctely / not sure 100%)
Regards0 -
I've done that, even sent them a file, but they seem flummoxed. John 0 -
Can you upload one of your NEF files to dropbox or similar and let us try it? 0 -
https://www.dropbox.com/s/3qjp6rm5dn62c ... 5.NEF?dl=0
An uncompressed NEF file from a couple of days ago. Hope this works. John0 -
Strange. I downloaded your NEF file. I can't get Capture One to see it to import it. I can open it and process the raw file in Affinity Photo, so there seems to be nothing inherently wrong with the file.
Ian0 -
I can't import it in C1 ☹️
but I can in Capture NXD and in LR5.7(via DNG converter)
Strange, indeed.0 -
The log files confirm that the NEF cannot be read. (Version 9.3 in this case)
Has it had any previous processing using Nikon software that makes changes to the NEF file?
Are you using any camera settings that might not be supported having somehow slipped through the assessment net for support?
Grant0 -
Affinity Photo suggests that it's an HDR/32 RAW file and offers no Lens information. 0 -
I can read d500 files in Breezebrowser which I use for renaming, and read and process the d500 files in Lightroom 6, ACDSee Pro 9, Photoninja and the latest version of NXD. The files are 12bit RAW with no compression, no HDR. There would be no lens info for this file because it was shot with an very old 500 mirror lens.
I've done tests with d500 files straight from the camera into Capture 10, without renaming them in Breezebrowser first, and they are also not recognized.
Capture 10 does read the d200, d300, and d800 files in my archives.
Thanks for confirming that this is actually a real problem and not just some sort of screw up on my part with the settings in Capture.
My d500 was one of the first into Canada so possibly there is a firmware issue although I have done the update that came out last year.
Regards, John0 -
[quote="NNN634406585152783376" wrote:
I can read d500 files in Breezebrowser which I use for renaming, and read and process the d500 files in Lightroom 6, ACDSee Pro 9, Photoninja and the latest version of NXD. The files are 12bit RAW with no compression, no HDR. There would be no lens info for this file because it was shot with an very old 500 mirror lens.
I've done tests with d500 files straight from the camera into Capture 10, without renaming them in Breezebrowser first, and they are also not recognized.
Capture 10 does read the d200, d300, and d800 files in my archives.
Thanks for confirming that this is actually a real problem and not just some sort of screw up on my part with the settings in Capture.
My d500 was one of the first into Canada so possibly there is a firmware issue although I have done the update that came out last year.
Regards, John
John,
I think all you can do is work with C1 support through a Support Case.
We know that other D500 users are not seeing problems.
You say the files are straightforward RAW with none of the special features used but my Affinity installation appears to see something related to embedded HDR functionality so clearly there is something odd happening here. Most likely only the C1 Support team will be in a position to work out what is happening so as far as I can predict that's about the only route you have open to a good answer at this time.
Grant.0 -
Thanks Grant.
Odd the HDR would show up in the files as the manual says it isn't available for NEF's. On my camera the HDR function is grayed out because I only shoot NEFs.
I might contact support again but when I sent them a file after the last upgrade they never got back to me other than to say they couldn't open the file and would look into it.
John0 -
John,
The HDR info in Affinity seems to be a bit odd. An artifact of how the program opens with your file perhaps? If I play around a while it changes mode. I have had the software for a while now but it's something I got to cover things I might need that C1 does not address and I have hardly used it so I have no idea why it does what it does when displaying your file. I have not found anything that seems to allow me to specify a display mode on file opening. Maybe I have missed something.
No lens info shown - is that to be expected? I assume you were using a manual lens of some sort or at least something not recognised by the camera?
Grant0 -
[quote="NNN634406585152783376" wrote:
https://www.dropbox.com/s/3qjp6rm5dn62c3m/2017-05-02_18-12-46-5.NEF?dl=0
An uncompressed NEF file from a couple of days ago. Hope this works. John
Very off topic, but a quick FYI for anyone posting a Dropbox link in public.
They have a 20GB bandwidth/100k hits cap for free accounts and 200GB/no hit limit for paid accounts. (daily cap, all shared links combined)
I got banned over a year ago and there is no one to talk to. The automated support is BS.
https://www.dropbox.com/help/security/banned-links
Hope it is useful to someone.
Cheers,
-Gus0 -
to OP:
You don't have installed or opted by accident for a Sony-only version?
AFAIK the Express version is Sony only and there's also a Sony-only Pro version.
This might explain why files from other brand's cam is not opened. At the same time the files may open just fine on another user's computer who has full Pro installed.0 -
Hi Michael,
A good question but C1 9.3 on my full Pro installation does not see the file either.
From the Release Notes documentation I believe A D500 NEF should be recognised by C1. However I wonder if there is an accidentally omitted restriction for some types of files from the D500.
Grant0 -
Well, I downloaded the file and yes, it doesn't open in my C1Pro Full either.
Interestingly it shows in Win Explorer (W10) - ok it may support NEF files. But then again I noticed that the file was originally created 17/05/02 but it also carries a date of 17/05/09. I'm not aware whether renaming only would cause this. Perhaps it's a different format output file which received accidentally the NEF extension. I'm not aware about Nikon's RAW file sizes but from my Sony's I usually get RAW file sizes in more or less the same MB size as is the MP size (20MP files almost 20MB of size and 24MP files with 24MB size). The NEF is over 30MB for a 20MP image. Uncompressed RAW? Not supported by C1?0 -
Hi Grant,
500 mirror lens about 30 years old.
John0 -
[quote="NNN634406585152783376" wrote:
Hi Grant,
500 mirror lens about 30 years old.
John
Ah! Interesting.
That probably explains the not unattractive overall slight "softness" then. I seem to recall that was a part of the "look" and suited the days of film reasonably well.
I have a 600mm Canon of a similar age (82 iirc.)
Has your image been touched at all by Nikon's software? (NXD?)0
Post ist für Kommentare geschlossen.
Kommentare
19 Kommentare