Import of D2Xs images into catalog
Hi,
Usage of the C1 8.3 Windows 7 SP1.
I create a catalog and start to import a series of images taken with D2Xs (Nikon). I left the images at there place. For some of them the images have been transformed moving the colors in such a way one can believe a solarization (kind of negative of the image, nice colors by the way) did happen on them.
After some time doing the analysis, I found the only images which have been transformed was the ones developed with Capture NX2 (RAW developer software from Nikon).
I made a test taking one of the images concerned and bringing into Capture NX2, I remove any operation then save the image under another name still with the .NEF extension.
I redo the importation of the image and that time it did work fine.
So, I have the workaround, therefore it is not a lock situation, but at the same time it a little bit time consuming to have to edit the original file to unset the development already done into Capture NX2.
There is, maybe, a decoding which is not done or done improperly by C1, to be check by the development team ?
Phil.
PS: No matter about the development itself as it is not kept by C1 (normal), just the time spent to undo what was previously done.
Usage of the C1 8.3 Windows 7 SP1.
I create a catalog and start to import a series of images taken with D2Xs (Nikon). I left the images at there place. For some of them the images have been transformed moving the colors in such a way one can believe a solarization (kind of negative of the image, nice colors by the way) did happen on them.
After some time doing the analysis, I found the only images which have been transformed was the ones developed with Capture NX2 (RAW developer software from Nikon).
I made a test taking one of the images concerned and bringing into Capture NX2, I remove any operation then save the image under another name still with the .NEF extension.
I redo the importation of the image and that time it did work fine.
So, I have the workaround, therefore it is not a lock situation, but at the same time it a little bit time consuming to have to edit the original file to unset the development already done into Capture NX2.
There is, maybe, a decoding which is not done or done improperly by C1, to be check by the development team ?
Phil.
PS: No matter about the development itself as it is not kept by C1 (normal), just the time spent to undo what was previously done.
0
-
Hum,
I correct myself, it is even worse than that. I cannot save under the same name after having removed all the developments previously done with CNX2. I have to save the file under a new name in order to be able to import with no problem.
A little bit tricky, I just hope it will be limited to the D2Xs, I have not too much images with that one.
Phil.0 -
Only the files from the D2x itself is supported. Not the modified files from Capture NX. 0 -
Well,
Nice to know about it. Sound strange anyway as normally any of the modification done into the .NEF files are taken into account by C1 for all the other camera from Nikon.
I load some D200 files, developed or not by CNX2 that did not make any difference. Why it did with the D2X ? I guess is the secret of the C1 decoding 😉
PS: To be more precise : the colour tag is "interpreted" by C1, I mean a colour tagged image in CNX get a colour tag in C1, of course the colour does not match and the order either (for example the violet, position 7 in CNX, will set as yellow, position 3) . Why this its another question, since teh decoding is done it should be done fully and match, if not the color at least the order. I will make a specific entry for that, it will help handle the case if any.0 -
[quote="PhilR59" wrote:
I guess is the secret of the C1 decoding 😉
No, actually more a secret of the CNX coding. We do not know what they do inside CNX, nor do we claim to support it. We only claim support for the files coming directly and unmodified from the camera.
If some modifications are indeed readable from CO, this is unsupported, and we cannot garantee that CO will function as designed.0 -
Lightroom has exactly the same problem with NEFs "touched" by Nikon's own software. 0 -
Christian, Keith,
Thanks for the answers. I get the point here, I know Nikon is quite secret with the .NEF file format.
I understood this will be the same answer for the color tag am I right ?
Phil.0 -
[quote="PhilR59" wrote:
Christian, Keith,
Thanks for the answers. I get the point here, I know Nikon is quite secret with the .NEF file format.
I understood this will be the same answer for the color tag am I right ?
Phil.
Phil,
As far as I know - and certainly in a historical perspective - there are no "standards" related to colour tags. That makes it difficult to exchange the intended "coding" from file to file between applications.
Whether this is changing for future use I am not sure. Even if it is the legacy situation is unlikely to change.
HTH.
Grant0 -
Grant,
Yes, I do agree there is no standard as far as I know. Every editor put more or less the same color, not in the same order, and make a link with a number for codification. After that one may find any combination even if it very often red associated with 1 and no color with 0, after ...
Do you think people from Phase 1 had a look for having a proper decoding Ligthroom/CNX/Capture codification (I mean color matching between C1 and these software), I think it could be a nice feature to have. After all C1 propose to import catalog from LR and Capture.0 -
Phil,
I think attempting to work out what the "standard" conversion might be would be a lost cause and quite possibly completely pointless even if possible. So no, I doubt it would be a project that would have any attraction.
Grant0
Post ist für Kommentare geschlossen.
Kommentare
9 Kommentare