8 bit TIFF export can not be opened in Photoshop correctly
Today I came across a new and really bizarre bug.
I produced 8 bit TIFF files in Adobe RGB produced from old RAW files that were created with a Leaf AFi 7 system.
If I try to open them in Photoshop Camera RAW will open but with complete false settings. The picture is not useable.
Through some online research I found that TIFFs can contain develop settings. Capture one produces here files that have develop settings which triggers Photoshop to open them through Camera RAW.
These settings can be stripped away with Bridge and then the file opens correctly.
The problem runs deeper as well. I have tried to export these files in question in other formats, like 16bit and ProPhoto RGB. These files are opened correctly in Photoshop. But once I convert them and save them again as an 8 bit TIFF this file will then have those incorrect develop settings again.
Has anybody come across this problem?
Unfortunately it was a picture editor, a client who pointed it out to me today as I had delivered high res files that were meant to go into print for a magazine.
I had problems in the past with Capture one and TIFFs. It was just the other way around. After updating from C1 V9 to V10 Capture could suddenly not process TIFF files any more that were part of the catalogue inside a project. I had a long support conversation that lead to nothing.
Whenever I return to Capture One and hope all is good I come across another serious bug. I should be able to rely on a professional RAW software to produce correct export files in standard formats!
I produced 8 bit TIFF files in Adobe RGB produced from old RAW files that were created with a Leaf AFi 7 system.
If I try to open them in Photoshop Camera RAW will open but with complete false settings. The picture is not useable.
Through some online research I found that TIFFs can contain develop settings. Capture one produces here files that have develop settings which triggers Photoshop to open them through Camera RAW.
These settings can be stripped away with Bridge and then the file opens correctly.
The problem runs deeper as well. I have tried to export these files in question in other formats, like 16bit and ProPhoto RGB. These files are opened correctly in Photoshop. But once I convert them and save them again as an 8 bit TIFF this file will then have those incorrect develop settings again.
Has anybody come across this problem?
Unfortunately it was a picture editor, a client who pointed it out to me today as I had delivered high res files that were meant to go into print for a magazine.
I had problems in the past with Capture one and TIFFs. It was just the other way around. After updating from C1 V9 to V10 Capture could suddenly not process TIFF files any more that were part of the catalogue inside a project. I had a long support conversation that lead to nothing.
Whenever I return to Capture One and hope all is good I come across another serious bug. I should be able to rely on a professional RAW software to produce correct export files in standard formats!
0
-
Not sure if I understand you correctly.
Opening TIF images in ACR is a PS feature that seems to pop up when there is an XMP file for that TIF (same for JPEG).
If you want to to open your TIF in PS without going through ACR, go to the preferences in PS/ACR and set the TIF file handling for ACR to 'never'. Alternatively, remove XMP files if you don't need them.
Regards,
Hans0 -
Hi Hans, thanks for your reply.
I might have not made it clear enough. There is no XMP file with the TIFF.
There is information embedded inside the file. It definitely is a bug. It was noticed with an export of 5 files from the same catalogue. 2 were Leaf Credo 60 files, two were black and white TIFF files and only one was a .mos file produced with a LEAF AFi 7. And only this file caused that strange behaviour.
I then tried other mos files within the same catalogue and could reproduce the problem with all of them.0 -
Hi Berndt,
Do you use "open with...." or "edit with..." ?
In the former, you open your RAW with ACR, whatever you have done with your images in C1.
In the latter, you keep your settings, including color space/profile.
If they are tiff, you must uncheck the PS file handling with ACR, as told by Hans.0 -
Thanks very much for your input guys.
I am aware of all that. Let me add that I am a working professional and no Photoshop settings have been changed regarding input for many years. A simple double click on my Mac OPENS all TIFFs in Photoshop.
And as mentioned before: It only happens with the exported TIFFs from this particular camera system.
You can see from within Bridge that the TIFFs in question have develop settings.0 -
[quote="tenmangu81" wrote:
Hi Berndt,
Do you use "open with...." or "edit with..." ?
In the former, you open your RAW with ACR, whatever you have done with your images in C1.
In the latter, you keep your settings, including color space/profile.
If they are tiff, you must uncheck the PS file handling with ACR, as told by Hans.
I forgot to mention: The problem was noticed by the picture editor of a magazine that is published twice a month. Someone who opens most likely thousands of images in Photoshop every week and has only encountered this problem now.0 -
According to Phase One support the problem lies within the Adobe software. From what I gathered from the reply it should be that Photoshop and Bridge misinterpret the ICC information within the TIFF file. Strange only that it doesn't happen with TIFFs produced with the same recipe shot with other camera systems.
My interpretation of that problem is at present that there is a bug with the latest Capture One and these files from the Leaf AFi or Aptus system. I only wish I would have converted all these files to DNG with Lightroom in the past.0 -
Found a source of that weird behaviour. This particular digital back had after an accident a hardware failure and would not store information any more. So the Metadata was messed up. As a creator date all files would show Jan 1st 1970.
It seems that this and the added metadata within Capture One, like keywords and copyright causes the problem. The moment I change the export recipe and disable "copyright" and "all other metadata" the exported files do not cause that problem any more.
Thanks again for the input from the other members here. Manually completely disabling the use of Camera RAW certainly works but it is not a default setting. So when you work with other people along the line who all use the standard software like Photoshop and have possibly default settings enabled this isn't a solution.0
Post is closed for comments.
Comments
7 comments