CS question -- possible problem with profiles & untagged tiff files

Just got CS and so far the RAW converter and a couple of other things look terrific for photographers.

However, one troubling problem I thought I'd vet with the group. When I open an untagged tiff file in PS 7 I get the proper dialog box, "Missing Profile" with "does not have an embedded color profile". When I open the same file in CS I get the "Embedded Profile Mismatch" box instead and it says the file is tagged as sRGB and do I want to change to my working profile (AdobeRGB for this film scan).

Anyone know what's going on here and if this is a bug? If CS is changing the profile from untagged to sRGB it's a major problem. If it's simply assuming untagged files are sRGB then it's a bit of a nuisance since I can't tell the truly untagged files (generally film scans) from the actual sRGB files (generally digital camera files).

If I open the file in CS without converting to the working profile the Profile box at the bottom left indicates the file is now sRGB.

Anyone else seeing this?

Bill

When I open
an untagged tiff file in PS 7 I get the proper dialog box, "Missing Profile" with "does not have an embedded color profile". When I open the same file in CS I get the "Embedded Profile Mismatch" box instead and it says the file is tagged as sRGB

I've played with this a bit more, maybe this is just a problem with untagged files from certain scanners? Dunno ... here is what I saw with further tests.

Opening up an untagged jpeg file in CS worked as expected, there was no profile assumed and all is well.

Opening up an untagged tiff file (from my Nikon scanner) in PS 7, cropping a bit and saving this as untagged and then opening this untagged crop in CS works as hoped, ie, it is seen as untagged.

Seems like the only files I have problems with thus far are the raw scans from my Nikon 8000 scanner. These are supposed to be untagged (I'm applying a custom scanner profile in Photoshop when I open them) but for some reason are seen as tagged with sRGB when opened in CS.

Given what I saw with the other two tests (jpeg and file saved untagged in v7 opening up correctly) I'd say this is a problem between the Nikon-generated tiff header and CS. Still doesn't explain why the files open correctly in v7 and not CS, but it suggests it's not a global problem with CS unable to recognize untagged tiffs, which is good.

Adobe is closed for the weekend, I'll try tech support on Monday and let you know what happens.

Bill

Seems like the only files I have problems with thus far are the scans from my Nikon 8000.

I also tried opening untagged tiff files generated from a Canon 10D digital camera via the Canon software, and these open as they should in CS, ie, with a "Missing Profile" dialog box.

So untagged Canon 10D tiffs work, files saved by Photoshop as untagged and reopened work and untagged jpegs open correctly too. It's just the Nikon tiff files ... maybe there's a problem with the way Nikon writes out the tiff header data, though these files open correctly on V7.

Bill

Most likely Nikon is adding EXIF data which indicates that it is in sRGB.

Chris

In article , Bill Hilton
wrote:

Seems like the only files I have problems with thus far are the scans from my Nikon 8000.

I also tried opening untagged tiff files generated from a Canon 10D digital camera via the Canon software, and these open as they should in CS, ie, with a "Missing Profile" dialog box.

So untagged Canon 10D tiffs work, files saved by Photoshop as untagged and reopened work and untagged jpegs open correctly too. It's just the Nikon tiff files ... maybe there's a problem with the way Nikon writes out the tiff header
data, though these files open correctly on V7.

Bill

Seems like the only files I have problems with thus far are the scans from my Nikon 8000.

From: Chris Cox

Most likely Nikon is adding EXIF data which indicates that it is in sRGB.

Chris, I scanned a small crop of a slide to get a 6 KB sized untagged tiff file that shows this problem (opens correctly with "Missing Profile" in V7, opens incorrectly with "Profile Mismatch" in CS). I did this to get a tiny file I can easily send to Adobe for checking.

I'd like to email this tiff file to someone in tech support so they can check the header and figure out what's changed with the CS EXIF decoding, if you can give me a name or email of the right person. Once we get that pinned down I can contact Nikon if need be.

Thanks.

Bill
(change .comedy to .com to reply)

From: (Bill Hilton)

When I open an untagged tiff file in PS 7 I get the proper dialog box, "Missing Profile" with "does not have an embedded color profile". When I open the same file in CS I get the "Embedded Profile Mismatch" box instead and it says the file is tagged as sRGB ...

From: Chris Cox

Most likely Nikon is adding EXIF data which indicates that it is in sRGB.

I asked this Q on the Adobe User Forum and got the fix from a lady named "Carol from England" ... basically she said to do Edit > Preferences > File Handling and in the File Compatibility box check the "Ignore EXIF profile tag" box.

This fixed the problem.

Bill

"Bill Hilton" wrote in message

From: (Bill Hilton)

When I open an untagged tiff file in PS 7 I get the proper dialog box, "Missing Profile" with "does not have an embedded color profile". When I open the same file in CS I get the "Embedded Profile Mismatch" box instead and it says the file is tagged as sRGB ...

From: Chris Cox

Most likely Nikon is adding EXIF data which indicates that it is in sRGB.

I asked this Q on the Adobe User Forum and got the fix from a lady named "Carol from England" ... basically she said to do Edit > Preferences > File Handling and in the File Compatibility box check the "Ignore EXIF profile tag" box.
This fixed the problem.

Is this really a fix? If Nikon is using the sRGB color space, do you not want to know that when loading images into PS?

Rick

"Bill Hilton" wrote

Edit > Preferences > File Handling and in the File Compatibility box check the "Ignore EXIF profile tag" box ... this fixed the problem.

From: "Rick"

Is this really a fix?

Some might call it a kludge or hack, but it fixes MY problem with scans.

If Nikon is using the sRGB color space,
do you not want to know that when loading images into PS?

The Nikon scanner will scan into whatever space you tell it to use, or none at all, and hell will freeze over before I ever tell it to scan into sRGB. But regardless, the tag info is in a different spot than the EXIF data so it's irrelevant for scans.

I checked three scans, one with Ektaspace as the working space, one in AdobeRGB and one untagged. Now all three open correctly. In the File Browser Metadata the working space is enumerated in "File Properties > Color Profile" and all three flavors now show correctly. This is NOT the EXIF data.

What is now ignored is in "Camera Data (Exif) > Exif Color Space". Apparently if a scan was untagged it had no "color profile" but it still had bogus default filler data of sRGB in the "Camera Data (Exif) > Exif Color Space" field and this is what was getting picked up.

So it's fixed for scanned files by ignoring this irrelevant filler metadata.

Whether setting this option will cause a problem with digital camera files is something I'll check with my 10D.

Bill

Edit > Preferences > File Handling and in the File Compatibility box check the "Ignore EXIF profile tag" box ... this fixed the problem.

From: "Rick"

If Nikon is using the sRGB color space,
do you not want to know that when loading images into PS?

From: (Bill Hilton)

it's fixed for scanned files ... Whether setting this option will cause a problem with digital camera files is something I'll check with my 10D.

I checked both jpegs and tiffs (processed from RAW) files from a Canon 10D and both open correctly with the "Ignore EXIF profile tag" box checked, so that covers all bases for me. YMMV ...

Bill