Problem with CS5 processed b/w files in C1E
Hello,
I got a "strange" problem with my Photoshop CS5 created b/w files after saving them in Capture 1 Express.
Here's the problem: I am exporting the adjusted file from C1E (16bit-tiff, AdobeRGB) to CS5 and turn it there into a b/w image without colorization. When i then use the OSX DigitalColor-tool in CS5 i got the same RGB-value in every channel and on every place in the image (for example R:92%,G92%,B92% in the sky and R:38%,G38%,B38% on the clothes and so on...) like it should be. But when i am saving this developed file in C1E and using the DC-tool again the RGB-values have changed - for example R98%,G92%,B92,7 (and the same in C1E's own RGB-scale) instead of beeing equally like they were before in Photoshop (i have to admit that nobody cant see any difference but the measurements cant lie, or?;)
If i save the file directly from CS5 on any folder on my hd instead of sending it back to C1 there is no problem (no matter if it's a tiff or a jpeg or if its in sRGB or AdobeRGB colorspace). But when i am sending the b/w file from C1E back to CS5 or export it directly from C1E the RGB-value problem still remains....!
I would be very glad if someone could help or explain me what the problem is or if it's problem at all!!
With kind regards,
Daniel
I got a "strange" problem with my Photoshop CS5 created b/w files after saving them in Capture 1 Express.
Here's the problem: I am exporting the adjusted file from C1E (16bit-tiff, AdobeRGB) to CS5 and turn it there into a b/w image without colorization. When i then use the OSX DigitalColor-tool in CS5 i got the same RGB-value in every channel and on every place in the image (for example R:92%,G92%,B92% in the sky and R:38%,G38%,B38% on the clothes and so on...) like it should be. But when i am saving this developed file in C1E and using the DC-tool again the RGB-values have changed - for example R98%,G92%,B92,7 (and the same in C1E's own RGB-scale) instead of beeing equally like they were before in Photoshop (i have to admit that nobody cant see any difference but the measurements cant lie, or?;)
If i save the file directly from CS5 on any folder on my hd instead of sending it back to C1 there is no problem (no matter if it's a tiff or a jpeg or if its in sRGB or AdobeRGB colorspace). But when i am sending the b/w file from C1E back to CS5 or export it directly from C1E the RGB-value problem still remains....!
I would be very glad if someone could help or explain me what the problem is or if it's problem at all!!
With kind regards,
Daniel
0
-
Not sure I understand your workflow, but what I certainly do not yet comprehend is what you like to achieve with the step to open the file in CO6 and process it again after you have post-processed it in CS5. What is the point in that step?
In other words, your workflow sounds unnecessary complex to me, so I must be missing something.0 -
[quote="Paul_E" wrote:
Not sure I understand your workflow, but what I certainly do not yet comprehend is what you like to achieve with the step to open the file in CO6 and process it again after you have post-processed it in CS5. What is the point in that step?
In other words, your workflow sounds unnecessary complex to me, so I must be missing something.
Hello Paul,
at first thanks for your reply.
My workflow starts in C1 where I develop the raw file and then send it to Photoshop to post-process it. After that I save it in my C1 folder, that's all. I like to have my Photoshop post-processed files in the C1 library (e.g for comparing) and I don't work on them anymore. How is your C1-Photoshop workflow if I may ask you this?
Like I wrote in my opening post I could not see any differences between the b/w image in CS5 (with the right values: R:92%,G92%,B92%) and the image in C1 (with the wrong values:R98%,G92%,B92,7) but the DC-tool and the C1 RGB-scale are showing them. That makes me wonder because it should not be, or?!0 -
Hi, thanks for explaining. I might take a look at your issue if time allows me (which is pretty limited currently).
My CO6 > PS workflow is as simple as it is. Processed raw files (CO6) are opened in PS for post-processing if deemed necessary. End of workflow.
The CO6 library is not a library in the sense of a searchable database; it is just a file browser with some session features (great features by the way). Also, CO6 does not dynamically update your preview in case you change your RGB file.
Last, in case you ever upgrade to CO Pro 6, you'll have access to an incredible B&W tool which might change your workflow.0 -
[quote="Paul_E" wrote:
My CO6 > PS workflow is as simple as it is. Processed raw files (CO6) are opened in PS for post-processing if deemed necessary. End of workflow.
Yep, same here - PS mainly being used to access a couple of Topaz plugins ("Denoise" and "Detail") which are very important to my end result.0 -
Interpolation results.
Having three channels with the same information in one image file is pretty useless. Convert to grayscale if you want grayscale.0
Post is closed for comments.
Comments
5 comments