Bad Color after Processing

Comments

24 comments

  • Anonymous
    Studiowest,

    See if corruption of color sync is the issue here. Review Knowledge Base article #1715

    http://support.phaseone.com/KB/Home/Sea ... nguageID=1

    Regards,
    kc
    0
    Comment actions Permalink
  • Studiowest
    The corrupted color sync article states:

    \"If the colorsync preferences are corrupted, the monitor profile would typically be shown as Generic RGB, rather than the profile selected using the MacOs Display preferences.\"

    My display profile reads correctly in display prefs as the last \"Color Eyes\" profile I created and the various other profiles are \"active\" as I can change between them and see the monitor respond.

    I will try deleting the prefs as suggested but doubt this is the problem. Any other ideas as to what may cause the shift?
    0
    Comment actions Permalink
  • Studiowest
    OK, I've visited Terminal as suggested and realize I don't know how to use it . I'll need better directions. Hitting return to start a new line retains the beginning portion of the previous line. Is this normal? How do you correctg a mistake if you need to?

    Richard
    0
    Comment actions Permalink
  • Jason1
    Richard,

    Some quick questions first:

    1) If you view the processed TIFF file in C1, does it match the appearance of the file in Photoshop (i.e. is the file really pink, or does it just look pink in Photoshop?)

    2) Which version of coloreyes display are you using to create display profile?


    >OK, I've visited Terminal as suggested and realize I don't know how to use it

    >Hitting return to start a new line retains the beginning portion of the
    >previous line. Is this normal?

    Yes, if you are refering to the prompt that is there at the beginning of each line (I think it will be your computer name as set under Network, by default)

    >How do you correctg a mistake if you need to?

    Use the backspace or delete key (you can't click to position the cursor with the mouse, but can use the cursor arrow keys if necessary). Incidentally, you should be able to copy the lines directly from the web page (either PhaseOne's version or my original ) by highlighting the required text, Apple key C to copy, go to terminal and paste with Apple Key V as usual.


    >The corrupted color sync article states:

    >\"If the colorsync preferences are corrupted, the monitor profile would
    >typically be shown as Generic RGB, rather than the profile selected
    >using the MacOs Display preferences.\"

    Nope, they missed out a bit. The whole point about the Colorsync preferences problem is that the display profiles being used by the application are different to what is specified in SystemPreferences:Displays:Colour. See Cause 2 on my web page for details. What they probably should have said was:


    \"If the colorsync preferences are corrupted, the monitor profile would typically be shown in the colour editor of Capture One Pro as Generic RGB, rather than the profile selected using the MacOs Display preferences.\"

    Capture One used to show you what display profile was being used in earlier versions, but it doesn't anymore. My several requests for this very useful troubleshooting feature to be restored have, unfortunately, fallen on deaf ears.

    Good luck
    Jason
    0
    Comment actions Permalink
  • Studiowest
    Jason, Thank you for your interest and your help.

    Now your questions.

    1) Taking a processed TIFF from the \"Processed\" folder and putting it in the \"Captures\" folder and then viewing it in C1's preview window, I see no difference from how that image appeared originally when shot. Neutral with no obvious cast. That same image opened in PS CS2 has an obvious pink cast.

    2) ColorEyes 3.1.07

    After finding the \"Color Editor\" in C1 (never having used it) the display profile referenced does carry the same name as that I assigned in ColorEyes and I believe therefore IS that profile.

    Do you still think I should delete the pref file in question through Terminal? It seems there is no corruption if I understand the issues correctly.

    Thanks again,
    Richard
    0
    Comment actions Permalink
  • Studiowest
    Jason, I've again been to Terminal, again with less than necessary skills.

    Opened Terminal, pasted the two relevant lines from your web page EXCEPT only the first line pasted. I then got the \"three rules warning\" and a request for a password. At the password prompt no key strokes were accepted.

    A little knowledge is a dangerous thing!

    Richard
    0
    Comment actions Permalink
  • Jason1
    Richard,

    Some more questions!:

    1) Have you checked that the output image is tagged with the correct profile? (i.e. if you set the destination profile to be Adobe RGB, is the file being correctly tagged as an Adobe RGB file?)

    2) Does it happen for new image files as well (files which have never been previously opened in Capture One)?

    In many ways your problem does sound like a colorsync issue, but it isn't showing the usual characteristics. Test the above first,

    Jason
    0
    Comment actions Permalink
  • Jason1
    Richard,

    >Jason, I've again been to Terminal, again with less than necessary skills.

    It is something I have done many times, but without knowing the state of your system, there can be complications.

    Send me an e-mail using my address on that page and I'll send you a script which will do it for you, if you wish to go down this route.

    Jason
    0
    Comment actions Permalink
  • Studiowest
    Hello Jason,

    I'll double check the profile tab tomorrow at work but I'm 99% certain that it is Adobe 1998. Color profile is set as the default display for image tab at bottom left of window and I'm sure I would've noticed anything foreign.

    Richard
    0
    Comment actions Permalink
  • Jason1
    Hello Richard,

    This is a rather an unusual problem! I thought it would be worthwhile summarising things so far, just to make sure that we have it clear in our minds:

    PROBLEM: You installed 3.7.3 RC1 and found that your images (TIFF, processed to Adobe RGB) turn out pink when viewed in Photoshop. You then re-installed 3.7.2 and found that the same image(s) still came out pink with the older version.

    --------------------------------------------

    TEST 1: The first thing we need to determine is whether your images are actually pink or not. You have viewed the processed file in Capture One and that appeared normal. This would suggest that the processed image itself is fine, and that there is noting wrong with Capture One, the Capture One application preference file or the individual image .plist files.

    Since this is such a critical test, it would be worthwhile confirming that the processed image is indeed OK. Would it be possible for you to check the image on another machine, or even better post the image somewhere so we can check it out?

    --------------------------------------------

    TEST 2: If the image is fine, then I think it points to 1 of 3 possible problems:

    a) There is a problem with your destination profile.
    b) There is a problem with Photoshop's preferences
    c) There is a problem with the Colorsync preferences.


    Problem (a) is quite straightforward to test for: Try processing the image using a different destination profile (eg ProPhoto RGB). Does the processed image still appear pink in Photoshop?


    Problem (b) can be tested for by creating a new user account, log in as that user and run Photoshop. This will create new user-level preferences and caches. Is the image still pink?

    Problem (c) is a bit more tricky to test. In many ways, your problem sounds like there is something wrong with your ColorSync preferences, but it isn't showing the usual characteristics. If I was in your situation, I would just delete them anyway to eliminate this as a possible cause.

    Colorsync preferences (in the form of .GlobalPreferences) are located at three levels. The Terminal lines listed on the PhaseOne knowledgebase deletes two of these, the lines on my site deletes one (the one that causes the problems in 99% of the cases). In your case, I would suggest deleting all three .GlobalPreference files. I will e-mail a script to you for this, if you wish to follow this line.


    If anyone else has any thoughts or additions, please chip in,
    Best wishes

    Jason
    0
    Comment actions Permalink
  • Studiowest
    Good morning Jason, (well morning here at least).

    I've opened processed images on my retoucher's machine and they are pink. That may be all I have time for now.

    Unfortunately, today is day one of a very long project. Art Director's, clients, ets., etc. here all day.

    I am emailing you screen grabs showing the problem. The \"clean\" file is taken from C1's preview window. The \"pink\" file is as processed and opened in CS2. The client would not like these products on the web as they are not on the shelves as yet.

    Please email the routine for the color sync pref files, I hope I can squeeze in a shot at the problem later today.

    Many thanks, Richard
    0
    Comment actions Permalink
  • Jason1
    Hello Richard,

    I'm just putting the colorsync prefs script together now, and I will e-mail it to you.

    However :

    >I've opened processed images on my retoucher's machine and they are pink

    Thanks for sending the images by e-mail, I can see the problem clearly. As the images are still pink when viewed on the re-toucher's machine, we will also have to include problems with the Capture One preference file and image .plist files in the troubleshooting.

    If you get the chance, I would suggest trying these two tests first before the others:


    Test A: Test for problem with the application preference file

    1) Close Cpature One

    2) Move the preference file for Capture One (called com.phaseone.application.captureonedslr.plist) out of your HomeDirectory:Library:Preferences folder.

    3) Restart Capture One, which will be reset to the factory defaults. You will have to set your preferences again and add any sessions back in. Try processing a file


    Test B: Problem with image .plist files.

    1) Close Capture One.

    2) Move the Capture One Settings folder out of the folder containing the raw files.

    3) Restart Capture one. New settings, thumbnails and previews will be generated for the raw files. Try processing a file.


    If there is still a problem with pink images you can put the original preference file (test A) or Capture One Settings folder (test B) back in their original positions afterwards.

    I'll e-mail the script to you shortly,
    Best wishes

    Jason
    0
    Comment actions Permalink
  • Studiowest
    Hello Jason,

    I've just concluded running all the procedures you have suggested.

    C1 files regenereated (both prefs and session files) - no change.
    Ran \"Delete GlobalPrefs\" - no change.

    Previous to those tests I processed the image using ProPhoto profile - no change.

    I am now going create a new acct, log in as new user and try again. I hope I can get back to you with that result before the work day starts here.

    Many thanks, Richard
    0
    Comment actions Permalink
  • Jason1
    Richard,

    Thanks for the update! Look forward to hearing your results with the new user test, which will indicate if it is a user-level or system-level problem.

    Best wishes
    Jason
    0
    Comment actions Permalink
  • Studiowest
    Hello Jason,

    Had a minute with new user testing. All I've done so far was open a C1 processed file in CS2 and it was still pink. Next I will shoot, process and view from scratch.

    Richard
    0
    Comment actions Permalink
  • NN111
    Sorry, I have just skimmed through the messages in this topic so this might not apply to your situation, but I was wondering if you are using dual monitors. I have been fooled a couple of times when my palette monitor somehow becomes the default monitor and I have to open Colorsync Utility and select my main monitor as the default display.
    0
    Comment actions Permalink
  • NN111
    Sorry, forgot to sign the last post.

    Rick
    0
    Comment actions Permalink
  • Studiowest
    Hi Rick,

    One monitor, thanks for your interest.

    Richard
    0
    Comment actions Permalink
  • Jason1
    Richard, Any news about the new user / new image / new processed file Test?
    J
    0
    Comment actions Permalink
  • Studiowest
    Jason,

    Sorry, not a minute to test. I WILL get to it this weekend!

    Richard
    0
    Comment actions Permalink
  • Studiowest
    Hello Jason,

    OK, I've just finished the New User Account testing to learn (drum roll please)...

    No change, still pink. To review, I got a neutral preview and a slightly pink version when processed and displayed in PS CS2.

    My procedure was to open a new session in C1, set all the profiles as in my usual acct. Shot same and different objects. All else was exactly the same.

    Richard
    0
    Comment actions Permalink
  • Jason1
    Richard,

    The New user test suggests that it is a system-wide problem and confirm that it is not related to preference files which are stored at the user level. A few things you could look at that, but I'm running out of ideas:


    1) Perhaps it is a profile problem? When you re-installed CO 3.7.2, did you purge your /Library/Colorsync/Profiles folder of the profiles installed by 3.7.3 rc1?

    It might be worthwhile deleting Capture One again, and the old camera profiles (including the extra copy of Adobe RGB that gets installed) and re-installing.


    2) Have you tried clearing your system caches, using one of the various maintenance utilities available (e.g. Tiger Cache Cleaner)?


    3) When you ran the script to delete your colorsync prefs and re-started, was it obvious that the pref files had been deleted? (i.e. did your monitor change brightness, and did you have to re-select your display profile? If you check in the color editor again, is it pointing to the right profile?


    4) Could there be something wrong with your display profile itself? Have you made a new display profile recently?


    5) Have you installed anything else lately that might be messing things up?

    All the best,
    Jason
    0
    Comment actions Permalink
  • Studiowest
    Jason,

    So sorry for the long delay. I'm in the middle of a massive shoot (200+ pix). That combined with the fact that retouching fine tunes most all colors has made finding time for sleuthing very difficult. It has made finding time for anything difficult.

    So I'm going to put this problem to bed for now and just work around it.

    I can't thank you enough for all your help and suggestions. I have learned much and still plan to follow your last round of ideas as soon as time allows. I will keep you informed.

    Regards, Richard
    0
    Comment actions Permalink
  • Laurie Frankel
    I am experiencing the same thing. I am running C1Pro 2.7.2 Mac, OS 10.3.9. I just tried the procedure laid out in:

    http://support.phaseone.com/KB/Home/Sea ... nguageID=1

    resetting the colorsync preferences (We saw no sign that they were corrupt. But, it was the only path we saw to try). We also tried processing on another computer. Here is what we experienced:

    Computer A (where we found the problem and removed the colorsync preferences): Identical results (according to Photoshop's info window) in processed files before and after removing the colorsync preferences. But, the RGB readings from the processed images did not match those displayed in Capture One or those from the RAW file's embedded thumbnail (which we pulled into Photoshop).

    Computer B (which was running C1Pro 3.6.1): Visually more similar to original RAW. But, still off.

    So, we restored the old preferences files on Computer A (we put them aside instead of deleting them). And now, we're not sure what to do.

    Looking at the last batch of questions you asked Richard:

    >1) Perhaps it is a profile problem? When you re-installed CO 3.7.2, did you purge your /Library/Colorsync/Profiles folder of the profiles installed by 3.7.3 rc1?

    We never installed 3.7.3, so I doubt its profiles are having an impact on us.

    > 2) Have you tried clearing your system caches, using one of the various maintenance utilities available (e.g. Tiger Cache Cleaner)?

    We haven't tried any cache cleaners. What would they do?

    >3) When you ran the script to delete your colorsync prefs and re-started, was it obvious that the pref files had been deleted? (i.e. did your monitor change brightness, and did you have to re-select your display profile? If you check in the color editor again, is it pointing to the right profile?

    3) It was obvious to us new profiles had been generated. I thought the screen looked brighter. But, more importantly, Terminal showed that new preferences files had been created with a current date stamp.

    >4) Could there be something wrong with your display profile itself? Have you made a new display profile recently?

    We generate display profiles regularly. But, why would C1Pro and Photoshop -- on the same screen at the same time -- show a color shift if the problem is a display profile? Wouldn't the whole display be off? Also since the info window in Photoshop is showing different values betwen RAW and processed, wouldn't that indicate the problem is not profile based?

    >5) Have you installed anything else lately that might be messing things up?

    This is the first time we have noticed this problem on our computer since installing 3.7.2. But, to be honest, until we recently saw the same color shift happening on a client's computer (also running C1Pro . . . don't know the release) we hadn't compared the processed images to the RAWs for months. Since they always looked good, we stopped looking. So, this shift could have been happening for a while. We don't think we have installed any other software. We routinely run stuff like Disk Warrior.

    Thanks much for your help. Any ideas?

    Appreciatively,

    Gary Beberman
    (for Laurie Frankel)
    0
    Comment actions Permalink

Please sign in to leave a comment.