What you see is not what you get
The preview display for C1 4 is nowhere near what is generated and shown in CS3. To match images I have to back off saturation by at least -10. What's going on? C1 Pro is much more accurate, as is ACR. This is a major bug! The program is almost useless if the preview isn't accurate.
What happened to the convenient method of creating a new folder for the output file? When the location button is clicked there is no option for creating a new folder - only the ability to point to a destination folder. Instead I have to go back to the Library, click on the folder I want to put a sub folder in and then create it. Then, I have to click my way back to the directory I was working in. This is VERY inconvenient.
What happened to the convenient method of creating a new folder for the output file? When the location button is clicked there is no option for creating a new folder - only the ability to point to a destination folder. Instead I have to go back to the Library, click on the folder I want to put a sub folder in and then create it. Then, I have to click my way back to the directory I was working in. This is VERY inconvenient.
0
-
I am having the same issue on my MB pro, and I have no external/secondary screen going...
still confused...0 -
[quote="Forgiss" wrote:
I am having the same issue on my MB pro, and I have no external/secondary screen going...
still confused...
Then I assume it is not the same issue, that is that the issue discussed here relates to the use of a secondary screen and it different profile.
Giving more details might give you more attention for your problem.0 -
[quote="Paul Steunebrink" wrote:
[quote="Forgiss" wrote:
I am having the same issue on my MB pro, and I have no external/secondary screen going...
still confused...
Then I assume it is not the same issue, that is that the issue discussed here relates to the use of a secondary screen and it different profile.
Giving more details might give you more attention for your problem.
Ok, I will take that, and correct my statement as to say that I have a similiar situation as was described in the original post.
I run a Macbook Pro 2.33ghz
OSX 10.4.11
Photoshop CS3
Calibration by Spyder (pantone)
I used to run RSP as a RAW converter on Windows based machines, and since switching to Mac, I have been looking for a stable, accurate alternative, so currently I am running the Trial for C1 4.
If I change all my saturation/exposure/white balance settings as required in C1 4 and process the file to 16bit Tiff, the image in the Preview window, and the tiff file I open in CS3 has drastically different Colours and saturations. I run the same profile from Camera (Canon 5D) to C1 to CS3, so it's not a case of sRGB converted to Adobe RGB, or something similiar.
Unlike the other posters, I run only on my Macbook's screen, and do not currently work on a secondary display.
I have only recently switched to mac, so my error can be completely my own doing... any advice would be helpful0 -
[quote="Forgiss" wrote:
(...)
I run the same profile from Camera (Canon 5D) to C1 to CS3, so it's not a case of sRGB converted to Adobe RGB, or something similiar.
(...)
This line triggered me. Do you use the camera profile as output profile (in CO4: Output tab) instead of sRGB or AdobeRGB? What is the working color space in CS3 (Color Settings, Sh+Cmd+K)? I suggest to bring those two in-line. The camera profile (5D in your case) is meant to use as input profile only (in CO4: Quick tab).0 -
The Quick-tab Profile for my input is: 5D generic
Output tab ICC is: sRGB Color Space
CS3 color space is: sRGB IEC61966-2.1
What I meant was that all color spaces are the same (or supposed to be...) They are all set to sRGB (that includes the Canon)[quote="Paul Steunebrink" wrote:
[quote="Forgiss" wrote:
(...)
I run the same profile from Camera (Canon 5D) to C1 to CS3, so it's not a case of sRGB converted to Adobe RGB, or something similiar.
(...)
This line triggered me. Do you use the camera profile as output profile (in CO4: Output tab) instead of sRGB or AdobeRGB? What is the working color space in CS3 (Color Settings, Sh+Cmd+K)? I suggest to bring those two in-line. The camera profile (5D in your case) is meant to use as input profile only (in CO4: Quick tab).0 -
Forgiss, it sounds you have setup your color management right. This puzzles me. Could you try to output a 5D file to 8-bit TIFF and JPEG. Open them in CS3 and also in Preview (including the 16-bit TIFF). Any differences? 0 -
Forgiss.
It sounds as if you and I have exactly the same problem.
The Quick-tab Profile for my input is: 5D generic
Output tab ICC is: sRGB Color Space
CS3 color space is: sRGB IEC61966-2.1
My settings exactly.
And yet the image that appears in CS2 is extremely dark and vastly undersaturated.
I never had this problem with C1 4 but only with C1 4.01.
I would uninstal C1 4.01 and reinstal C1 4 (which I liked), but it seems as if C1 4 has been over-written by C1 4.01 and therefore no longer exists.0 -
I am quite confused.
I did all the updates (and now it C1 4 seems slower) but more accurate.
Side by side comparison of the preview window for C1 and Photoshop appears to be matching now, but I agree. Going from C1 to Photoshop after conversion, I get the definite feeling that there is a difference in Saturation.
I have picked up a difference though: Green. I am not sure how to post it here though because its a side by side comparison difference in two seperate programs.
Green channels seem to suffer during saturation, and appears to be undersaturated when opened in photoshop.
The rest might just be an optical illusion. C1 runs on full black and dark grey, photoshop runs on the background of choice (mac) removing all the background and turning everything black seems to improve things, so at least half of the problem seems to lie with me.0 -
Viktor,Darko last week I downloaded C14 to make a workaround with C1pro.
I'm working with canon eos1ds and leopard. With both apps open I shoot thetered in pro and open them in 4. The same problems appear in photoshop, it doesn't match at all. Can this be a colormanagement problem in witch 4 cannot cope with?0 -
The difference in PS and c14 for me is solved. A better look at colormanagement solved the problem for me in leopard. Cmnd, shift K in PS gives the settings you can apply and save them. In Bridge you can link the saving you made in PS.
Check colorsync if your hardware is linked correctly. Then in C14 save your process files with Adobe RGB and not sRGB. For me it works .
Ron0 -
This thread got so long I got confused - apologies if this has been addressed:
Placing your OSX tool bar onto one screen or the other (System Preferences --> displays --> Arrangement) does NOT set a primary monitor.
Steps for setting primary display:
1) Close any open CM'ed software (eg - C1, Photoshop, etc.)
2) Open ColorSync Utility (Applications --> Utilities --> ColorSync)
3) Click on "Devices" from the icons along the top of the window
4) Click the drop-down arrow left of "Displays" to reveal connected displays.
5) Select the desired monitor for "primary" use.
6) Click the "Make Default Display" button on the right-hand side of the window.
7) A blue dot should appear to the right of the monitor's name, indicating "primary."
Now any programs which only support single-monitor color management should soft-proof colors properly on the primary display. I prefer this as standard protocol, as it saves me remembering which of the dozens of imaging programs out there properly support multiple monitors.
One thing I am unsure of which MAY be a problem (Phase tech's, feel free to answer this one).... In v3.7.x the preferences contained an outdated "rendering intent"; you could select "default," even though Mac's ColorSync no longer provided "default" rendering methods. This preference is no longer available in v4.x. As v3.7.x relied on ColorSync for soft-proofing, I am unsure whether v4.x uses any specific settings (eg - "perceptual/best), or is still attempting to rely on ColorSync's "defaults." If it is the latter, that could create errors (as, since I noted, ColorSync no longer provides "default" rendering settings). Just a thought.
But for anyone who didn't know where to set color support for your primary Mac display - hope this helped!
~Gully0 -
Thanks Gully! That made things work much better for me!
Hopefully they will still fix this but at least now it's not as much of a constant thorn in my side.0 -
Flindt & Forgiss -
Still trying to figure out what your problem(s) could be (since it's single-monitor). A couple things:
1) As mentioned, check your CS2/3 color preferences - and note the handling of "profile mismatches" - if it's set to convert without warning, you may be converting the profile without realizing. Also as mentioned, make sure that your color "workspace" is set up appropriately. Lastly, check your "proof setup" as well; if you are set to the default CMYK proof and have it "on" (cmd-Y), you'll see a CMYK soft proof - which will naturally look wrong. The proof setup (and on/off) is under the "View" drop-down menu in PS.
2) Make sure you REMAIN in "sRGB" in C1v.4's output ICC profile when comparing; you'll notice as you toggle between (for instance) sRGB and RGB1998 in the processing tool that the image in the viewer is altered to represent the selected color space.
3) When calibrating, your gamma should be set to 2.2 C1v.4 is set up to handle a gamma of 2.2. If you use 1.8 in generating a monitor profile, CS3 will adjust, but C1v.4 will create a bright, flat proof image. (Unless you are working with specific advanced parameters, 2.2 is now considered the proper gamma setting - yes, even on a Mac. This is documented by both Apple and Eizo, for those running either of those displays.) I mention this because one of you mentioned being a recent PC convert - and I thought you might have been mislead by the OLD "Macs are 1.8" rule.
Hope one of these suggestions helps. Please let us know how it works out - and post images if you can! (In reply to the "how to show two programs" - line up the windows so we can see matching image portions, and do a whole-screen grab using CMD-shift-3 or hit CMD-shift-4 and drag the crosshairs across the portion of the screen you wish to capture. They'll appear as PNG files on your desktop.)
And Victor - did the "primary display" setting work for you, or are you also still in limbo?
~Gully
[/img]0 -
Additional note on gully's fix for us dual monitor people:
If you're using a MacBook / External monitor setup as I am, I noticed that if you implement that fix, but then use the laptop on it's own without the external, the primary monitor in colorsync will revert back to the laptop screen. So whenever you hook back up to your external, you will have to set that as the main display again.0
Post ist für Kommentare geschlossen.
Kommentare
44 Kommentare