Adobe applies its settings to C1 procesed files
I'm new to C1, using 12 pro for Windows.
When re-processing a RAW file previosly processed in ACR and saving out as a TIFF, if I then look at the saved Tiff using Adobe Bridge, the colours look off. If I then open the Tiff, it opens in ACR in Photoshop.
If instead of opening in Photoshop I open in SilkyPix, its all good.
It seems that Phtoshop knows and reads from the Tiff the earlier processed setttings and (wrongly) treats the Tiff like a raw file and opens with adjustments (including crops) previously made.
A new raw file not previpusly processed seems to be fine.
Any ideas on how to resolve this issue?
QB
When re-processing a RAW file previosly processed in ACR and saving out as a TIFF, if I then look at the saved Tiff using Adobe Bridge, the colours look off. If I then open the Tiff, it opens in ACR in Photoshop.
If instead of opening in Photoshop I open in SilkyPix, its all good.
It seems that Phtoshop knows and reads from the Tiff the earlier processed setttings and (wrongly) treats the Tiff like a raw file and opens with adjustments (including crops) previously made.
A new raw file not previpusly processed seems to be fine.
Any ideas on how to resolve this issue?
QB
0
-
It's not clear where Capture One comes into this workflow. Can you clarify?
Ian0 -
I going to take a SWAG here and assume that you mean you process a Raw in C1 and then try to re-process the Raw in PS. If that's the case, then of course PS opens to ACR: that's what it does when you tell it to process a Raw file. PS has no idea that it was previously processed in another program and PS has no idea what to do with C1 adjustments in a sidecar file.
I don't understand the "saving with Bridge" part though: Bridge is just a browser if I remember correctly, and for editing it opens PS or PS Elements (whichever you have).
If you want to use PS to work on an image processed by C1, you need to export a TIFF (which apparently you may have done). At that point your experience is like mine with PS CS6: more often than not, PS screws up the color rendering of C1 TIFF files (I generally use aRGB color space, but the same happens for sRGB).
Every other bit editor I use correctly interprets color from C1 TIFF files except for PS CS6, and my solution is to now use Affinity Photo. A fringe benefit is that Affinity Photo does a better job on a number of things than CS6 does, including stitching panos, healing, and inpainting.
For starters, though, it sounds like you need to really understand what program's opening what file, and which program is saving (and in what format). Raw is Raw and TIFF is TIFF. As long as you keep trying to open the Raw file in different programs, they'll try to apply their base Raw adjustments, whereas if you open a TIFF, they should work off the TIFF parameters. Caveat: not all programs understand layered TIFFs.0 -
Perhaps I can clarify
1. The raw file has previously been processed in Adobe Camera Raw. It's a Fuji GFX 50S raw file
2. I am now processing the same raw file in C1. The resulting TIFF file is then Exported (File / Export Images / Variants).
3. The file looks fine before export in C1. When viewed in Adobe Bridge, or Photoshop, its obviously wrong, and very different from the file as seen in C1. Although the file is a TIFF exported from C1, it still picks up the (now redundant) ealier processing parameters from ACR. The question I have is why that is the case and what can be done about it?
The issue is this: why is a raw file, processed before in ACR, but now being processed in C1, inheriting the earlier ACR settings at all? Its a raw file!
Thanks
QB0 -
So, if you work in Capture One on a file that hasn’t previously been processed in ACR, does that a look right in Bridge or Photoshop?
Ian0 -
I think here's the problem: you're exporting when you should be processing. Exporting sends copies of the original [Raw] files to your chosen destination, whereas you need a Process Recipe to output a TIFF.
When you exported, what was the file suffix? I'm guessing it was whatever your camera's Raw format is and not TIFF.0 -
But you can just as readily create a TIFF using File>Export images>Variants as long as you select TIFF as the output format.
Ian0 -
Re-reading your clarifying post, which sounds like you "exported" a TIFF file (see my last post as to why you should use a process recipe to output a TIFF)...
This is just a guess, but if you first processed the Raw in ACR, then ACR probably saved its adjustments in an xml (sidecar) file. And then when you imported the resulting mess into C1, C1 imported both the Raw and xml. However, C1 can't interpret ACR's adjustments (different algorithms and so on), and so just ignored them.
Now here's where I'm guessing again: Assuming that C1 imported the ACR sidecar, then it could be that C1 adds its adjustments to the same sidecar (still ignoring whatever was done in ACR). Then if you export the Raw + adjustments, the sidecar file could include both ACR and C1 adjustments. Going back to an Adobe product, that product will then read the previous ACR adjustments and ignore those by C1 (again, different algorithms, etc.).
But of course that doesn't explain why a TIFF (hopefully obtained via Process Recipe and not Export) would behave as you say.
The first thing I'd try is creating a Process Recipe for your choice of 8- or 16-bit TIFF in your choice of sRGB or aRGB color space and let us know what happens.0 -
[quote="Ian3" wrote:
But you can just as readily create a TIFF using File>Export images>Variants as long as you select TIFF as the output format.
Ian
Sorry; I've never done that. When you do that, are you having C1 include adjustments? If so, you may be back to the sidecar issue I described earlier (Adobe reads the sidecar, sees ACR adjustments, and erroneously applies them to your TIFF file).
So 2 things to try now:
1. Export without adjustments, or
2. My preferred method: create a Process Recipe.0 -
[quote="Nature Isme" wrote:
[quote="Ian3" wrote:
But you can just as readily create a TIFF using File>Export images>Variants as long as you select TIFF as the output format.
Ian
Sorry; I've never done that. When you do that, are you having C1 include adjustments? If so, you may be back to the sidecar issue I described earlier (Adobe reads the sidecar, sees ACR adjustments, and erroneously applies them to your TIFF file).
So 2 things to try now:
1. Export without adjustments, or
2. My preferred method: create a Process Recipe.
Yes, my preferred method too. Creating a process recipe is just a more efficient way of doing the same thing. (I do it with process recipes too - for one thing, you only have to set it up once, instead of selecting the parameters every time you export.) But it’s much the same thing, with similar options to those you can save in a recipe.0
Post is closed for comments.
Comments
9 comments