C1 using non-standard/"broken" color space profi
I've recently begun using Neat Image, and after getting some setup and profiling niggles worked out, everything seems to be going well. I had one strange issue; when processing C1-created JPGs in Neat Image 4.5, I get all the EXIF data including the color space profile tag, but only when I save as JPG. If I save as a TIFF, the color space profile tag is missing, and I have to manually add it in Thumbs Plus. I pointed this out to tech support for Neat Image, and here is their response (they are confused about where the JPGs I am using for input to Neat Image are coming from; they come direct from C1):
AW> Aalthough for some reason, TIFF output does not seem to keep
AW> the standard color space tag, whereas JPG output does.
I think this is causes by incorrect encoding of this tag by Photoshop or another software that you used to save this image. It is apparently saved by Photoshop and in other image samples that I have here saved by Photoshop its encoding of the color space tag is accurate and Neat Image knows how to deal with it. In your image (that you sent earlier) the encoding of the color space tag is not accurare so Neat Image does not know how to copy it from JPEG to TIFF image (in case of JPEG to JPEG there is no problem).
Please review the way you save converted RAW images into JPEG files that they get this incorrect encoding of the color space tag. Check which software tools participate in this process and try to exclude them one by one to see who is writing an incorrect tag. If the tag is correctly encoded then Neat Image will copy it to output TIFF file.
Now, this doesn't sound right to me. Thumbs Plus, Capture One, and Photoshop 7 and CS have no problem with the working space profile tags assigned by C1, and they appear identical in the info section in Thumbs Plus as in-camera JPGs, when it comes to how the color space profile is tagged. It's a niggle at this point, but I was wondering what the real lowdown was. Anyone?
AW> Aalthough for some reason, TIFF output does not seem to keep
AW> the standard color space tag, whereas JPG output does.
I think this is causes by incorrect encoding of this tag by Photoshop or another software that you used to save this image. It is apparently saved by Photoshop and in other image samples that I have here saved by Photoshop its encoding of the color space tag is accurate and Neat Image knows how to deal with it. In your image (that you sent earlier) the encoding of the color space tag is not accurare so Neat Image does not know how to copy it from JPEG to TIFF image (in case of JPEG to JPEG there is no problem).
Please review the way you save converted RAW images into JPEG files that they get this incorrect encoding of the color space tag. Check which software tools participate in this process and try to exclude them one by one to see who is writing an incorrect tag. If the tag is correctly encoded then Neat Image will copy it to output TIFF file.
Now, this doesn't sound right to me. Thumbs Plus, Capture One, and Photoshop 7 and CS have no problem with the working space profile tags assigned by C1, and they appear identical in the info section in Thumbs Plus as in-camera JPGs, when it comes to how the color space profile is tagged. It's a niggle at this point, but I was wondering what the real lowdown was. Anyone?
0
-
Well, I got a reply to my email response to the Neat Image folks:
AW> How odd. All my color-managed software seems to
AW> handle it properly (of course, only Thumbs Plus,
AW> Capture One, and Photoshop CS are color-managed on the
AW> PC; Thumbs plus shows the tag in the same place and
AW> same way as it does for in-camera JPGs and
AW> Photoshop-saved JPGs, and correctly converts it to the
AW> monitor profile and shows accurate tonality and color.
Well, I can also make Neat Image show it there, I mean copy it to the output image. However the tag is encoded agains the ICC specifications, I have just double-checked the specifications. Basically the encoding does not comply with the specifications.
It is possible that I will make Neat Image more tolerant to this kind of corrupted metadata in input images but the problem should be resolved at the source - in the software that writes such images.
AW> I'll email Phase One and see what they have to say on
AW> the subject.
Thank you. I am ready to help them if they need my assistance.
What is non-standard about the way C1 tags images with EXIF color space tags? Why does no other software seem to have an issue with this? I don't know enough about the EXIF standard to identify the issue myself.0
Post is closed for comments.
Comments
1 comment