Photoshop CS5 colorpicker sampling lighter color

When I try to edit the color of a shape layer by opening the color dialogue box of the shape layer, the color that is picked up is a lighter color than the color I clicked on. 
The eyedropper is set to point sample and all layers.  This problem does not occur if I open the color dialogue box that is part of the toolbar.

A screenshot showing everything at the moment just after you sample the color would be good as well.
Keep in mind that adjustment layers above the layer will affect how it looks on the screen, but when you're editing the color of the layer itself it's going to show you the actual color of the layer.
-Noel

Similar Messages

  • Printing from Adobe Photoshop CS5 on a HP Color Laserjet CP5225 printer

    Hi
    When I want to print something out from Photoshop CS5 on my printer I get this error.
    PCL XL Error
    Subsystem: KERNEL
    Error: IllegalOperatorSequence
    File name: derived_scr/1x55.ndbg.kernel.c
    Line number: 1820
    My windows system is Windows xp proffesional with servicepack 3.
    If I print out from other program I don´t get any errors.
    This is a new printer and before I got this I had a HP Color Laserjet CP5225 and there were no
    problems printing out from Adobe Photoshop CS5.
    I really hope someone can help my quickly because I have some tickets I have to print out for tomorrow.
    Kind regards

    You posted in the wrong forum, and an admin moved it for you.
    Unfortunately the error is from the printer driver, not Photoshop.
    Assuming you're using the latest version of Photoshop (12.0.4 or 12.1), you need to contact HP for an updated driver to fix their bugs.
    (if you don't have the latest version - go update now)

  • Photoshop CS5 Mac Dual Monitor color problems

    Hi all,
    I know this problem has been raised before, but I can't seem to find a definitive answer - there is a lot of conjecture and opposing opinions so I'm trying to get to the bottom of this once and for all.
    Gear: MacBook Pro, Photoshop CS5, Wacom Cintiq 12WX as second display, Mac OS X 10.7.4
    Problem: Photoshop seems to only use the Monitor Profile of the main display (i.e. the one with the menu bar in System Preferences>Displays>Arrangement) - some people say yes, this is the case, some people say no, Photoshop uses independent profiles for each display.
    Manifestation: If I set my MacBook screen to the main display, color looks good in Photoshop on the MacBook and terrible on the Wacom and vice-versa. However, in Lightroom and other applications changing the main display makes no difference to the output on each display.
    Preferred solution: I would like to have my MacBook as my main display with menu bars and dock etc, but then I want the Cintiq to be the display I use in Photoshop, for obvious reasons. In my workflow, I would like to have my image open in 2 windows, one on the Cintiq for retouching and one on the MacBook to check progress and color etc
    Curveball: I have a trial of CS6 and the problem seems to be fixed (maybe, my eyes and sense of reason are fried)
    Many thanks for any help anyone can shed
    Simon

    Make sure you have all the updates installed for Photoshop.
    Apple introduced new bugs in their display and window update pipelines in 10.7, which we didn't get a chance to completely work around until Photoshop CS6.
    We tried to work around them as best we could in the dot releases for CS5.

  • Photoshop CS5 not printing in color!!!

    I'm running Mac 10.7.5, with Photoshop CS5.  My printer is a Brother MFC-J435W.  Until just recently, I've not had any problem printing anything.  But a few days ago I can't get the printer to print in color off of Photoshop.  Any other program (LibreOffice, Preview, etc...) it prints color images just fine.  But all Photoshop documents for the past week have been coming out black and white.  I've checked and double checked all the Print dialog settings, and they're all set for color.  Puzzled and annoyed does not accurately express things... Help!  And thank you in advance...

    You have enabled "Photoshop manages color" and are using a specific color profile...
    Mylenium

  • Adobe Photoshop CS5 color replacement tool not working well

    I am using adobe photoshop  CS5, when I use color replacement tool it replace color with its own choice not mine and I have visited many blogs but no solution
    Please contact me at: [ links removed by admin ] I shall be very thankful

      This is picture before color replacement tool and this is after whereas i needed white backgroud and black foreground. I visited many blogs but couldn't do it correctly.

  • Photoshop CS5 Color Management

    My question has a complicated back story, but here is where I'm at.  I'm still a newby when it comes to color management.  I'm running Photoshop CS5, Lightroom 3.3, Windows 7 64-bit, Dell Studio XPS desktop, and a new Dell U2311H monitor.  I really struggled several months ago trying to learn color management and Photoshop printing work flow, and may have made an error during that process that created my situation.  When I attach a new monitor (or different monitor), all of my images in Bridge, Photoshop, and Lightroom display with a strong pink/magenta cast.  Images displayed by applications that are not color managed look normal.  Once I calibrate the new/different monitor (with Spyder2Express), and reboot, the color managed images display normally.  If I go to the Control Panel, and assign another profile (such as sRGB IEC61966-2.1) as the default profile for the monitor, all images continue to display normally.  If I go to the Control Panel, and disassociate ALL profiles from the monitor, the images displayed by Bridge, Photoshop and Lightroom again display with a strong pink/magenta cast.
    If no profile has been assigned to the monitor on which Photoshop is going to display an image, what does Photoshop do that might result in a pink/magenta image?  Might I have a corrupted profile somewhere, or might I have miscoded something in Color Management that is causing the condition?  If I need to provide some additiional info, please let me know what info is needed.
    Thanks for any assistance..

    Andrew, thanks so much for taking the time to respond.  I believe I found
    and corrected my problem last night.  When I attempted to do my own printing
    from Photoshop last summer, I experimented a lot as I tried to figure out
    the work flow.  I discovered last night that I had apparently introduced an
    error into the Monitor Color settings under Color Settings.  The RBG Work
    Space under Monitor Color was set to "Monitor RBG - xxxxx", where xxxxx was
    the profile for the Epson paper I was experimenting with last summer!  I
    suspect that Protoshop was using that profile when I didn't provide any
    other profile for the display.  I changed that setting to "Monitor RBG -
    sRBG", and my problem (the strong magenta casts when displaying images
    without profiling the monitor) is gone.
    I have been using the Spyder2Express for the past couple of years, and
    usually work with a monitor I have previously calibrated with the Spyder.
    This magenta problem only showed up when I switched to a new monitor, and
    displayed images before running the first calibration.  I wanted to resolve
    the magenta problem, however, to determine whether it might be connected to
    two other problems I have involving color management.  The first was my
    attempt last summer to print on a "hand me down" Epson 2200 printer.  I
    finally got the work flow figured out, but was never able to eliminate a
    slight magenta cast from some of my prints.  I tried printing from three
    computers, using two operating systems, downloaded the 2200 driver and paper
    profiles numerous times, printed on two different Epson papers, printed test
    prints of the same image on two other printers (without the slight magenta
    cast).  I've given up on the 2200 for now!
    My latest concern, which really prompted my renewed interest in color
    management, is my latest monitor calibration.  I just purchased a Dell
    U2311H, and calibrated it with the Spyder2Express.  At the end of the
    calibration/profiling process, the Spyder provides a before/after view.
    With other monitors, I've always felt that the calibration/profiling process
    improved the test image.  With the Dell U2311H, however, it appears to my
    eyes that the "before" image looks super, while the "after" image appears to
    have a yellowish, or yellowish-green, cast, and the after image is also
    "lighter", giving the image a bit of a "washed out" look.
    Any suggestions on what I might try next?
    Thanks again for your help, Andrew.  By the way, I read the two articles you
    sent links for.  I especially enjoyed the article on matching display and
    prints.  I'll keep rereading that one until it all soaks in!
    Mike
    www.mikelandwehr.smugmug.com

  • Adobe Photoshop CS5 Win 63 and 32 bit color replacement tool

    I opened a B/W jpg file, converted it to CMYK.  I have followed the directions from a few Color Replacement tool Help, etc.  I can't get it to work.  Converting Black to a lighter color, shows up very dark when it works, which is sporadic.  Very frustrating.  Open JPG file, convert to CMYK.  Select CRT, click Foreground color to a light color, select the black with one mouse click.  Drag to change color.  When/if it works color is very dark.  Doesn't work everytime.  Using the Color Mode and Sample Once.  Vista 64-bit with all SP's, CS5 32 and 64 bit, same results.

    I'm realyl not sure I understand why you try to use that workflow. A greyscale image is by all means devoid of all color and just contains lightness/luminance information, so there is actually nothing to replace. The times when it happens are probably just random compression artifacts that have a slight color fringe. With b/w imagery, you rather tint regions and that can be done using selections and adjustment tools or a global gradient map adjustment....
    Mylenium

  • Color change on exporting from lightroom and saving in Photoshop CS5

    I have been having issues with my pictures with color management.    I have Lightroom 4 and Photoshop CS5.  I thought over the last 2 years that it was just me.   I have bought a Eizo monitor with a hood, calibrate with a i1display pro, painted my walls gray, updated my strobes from alien bees to elinchrome bxri's.   Updated my sekonic meter to a L 758.   Have done custom white balance with gray card, expodisc, xrite kits.   The problem has been over the years when I work on a picture in lightroom and export it as jpeg or adobe rgb it gets saved to my external hardrive and the colors are really bad !!   You can go back and compare the picture in lightroom to the picture on my iomega external drive and there is a significant difference.   I do some animal photography and I had a dog that had brown fur and when I export it out of lightroom the dogs fur is actually a bright very orange color.  Same thing happens with skin tones.     When I import the photos into lightroom the pictures look ok.       The same thing is happening when I go from lightroom to photoshop the picture color looks good but when I go to File-save as - tiff or jpeg the colors are changing.   It does not matter what color space I am in I have tried them all it is still happening.    If anyone has any insight that would be great.  
    Teresa

             Thanks everyone for the help.   I have only been doing photography for about 2 years and the color managment part has been my hardest thing to get right.   My monitor ColorEdge CG243W LCD.   Wide color gamut of 98%.  Has a sensor on front of monitor that detects ambient brightness but this will only work if you are in a custom color mode.  Modes are: custom,  sRGB,DCI,EBU, Cal1.   I use the Cal 1 to be able to use the Colornavigator software that came with the monitor.  You also have to be in custom color mode to be able to manually adjust brightness, contrast, temperature on the monitr itself which I do not use because I use the Cal 1 mode.   I was not sure about the digital input signals.   I am on the DVI-I in which this allows digital signal input and analog signal input.    There is a DVI-D mode that allows only digital input only.    Also did not know if I needed to be concerned about setting the frequency that corresponds to the grahic board in the monitor ?    My bandwith was set to normal and now is on wide.   My digital input is for 1920x1200 resolution.   Appicable signal is Vesa CVT RB.  Frequency is 60 Hz.   Yes I did call Eizo twice last year when I got my monitor and did not get very far.     I have also called and spoke to a color specialist at my lab and told him the problems I have been having and he just told me to leave everything in sRGB.   Well I would like to get the most from my monitor's color gamut and when working on my pictures so that is why I am still determined to get this figured out.  
    I use the i1 Dislpay Pro hardware to calibrate with and the ColorNavigator software.     When calibrating.   I go to create a new target---select enter manually--Gamut ( monitor native--states recommended)--Brightness 100cd---White point (6500k)--set black level (recommemded states mininum 0.2)---gamma 2.20---priority (set automatically to standard, this adjusts gray balance while maintaining the contrast)---then I hit calibrate and it goes through the process.   The results I get are:                                            Target                                               Result
                          Brightness                                        100cd                                              99.9cd
                           Black Level                                    minimum                                       0.15cd
                          contrast ratio                                                                                            647:1
                          White Point                                    6500k                                              6501k
                           Gamma                                           2.20                                             R   0.6774,0.3136
                                                                                                                                            G   0.2031,0.6992
                                                                                                                                            B    0.1498,0.0499
    Thanks again for your help I know this is alot of information but I thought it might help ?
    Teresa

  • I'm using an iMac running Os X Yosemite, Photoshop CS5 Extended, R2880 Epson printer  In the Print Settings dialog box, I can't select Color, Advanced BW or Grayscale unless I select "Printer Manages Color". The pull down menu is grayed out. Even with "pr

    I’m using an iMac running Os X Yosemite, Photoshop CS5 Extended, R2880 Epson printer  In the Print Settings dialog box, I can’t select Color, Advanced BW or Grayscale unless I select “Printer Manages Color”. The pull down menu is grayed out. Even with “printer manages color” the tif or jpg image comes out in color overlaid with black. (See example - printer1. image on left is close to what it should be). Photoshop has no updates pending. I’ve downloaded the latest Epson driver which was working fine just before the problem occurred

    Is your Photoshop CS5 updated to 12.1?
    Are you on Yosemite 10.10.1 or Yosemite 10.10.2?
    Did you apply the recent Epson software 2.1.9 update?
    What type of file is it (file format)?  What bit depth and what color space?
    BOILERPLATE TEXT:
    Note that this is boilerplate text.
    If you give complete and detailed information about your setup and the issue at hand,
    such as your platform (Mac or Win),
    exact versions of your OS, of Photoshop (not just "CS6", but something like CS6v.13.0.6) and of Bridge,
    your settings in Photoshop > Preference > Performance
    the type of file you were working on,
    machine specs, such as total installed RAM, scratch file HDs, total available HD space, video card specs, including total VRAM installed,
    what troubleshooting steps you have taken so far,
    what error message(s) you receive,
    if having issues opening raw files also the exact camera make and model that generated them,
    if you're having printing issues, indicate the exact make and model of your printer, paper size, image dimensions in pixels (so many pixels wide by so many pixels high). if going through a RIP, specify that too.
    etc.,
    someone may be able to help you (not necessarily this poster, who is not a Windows user).
    a screen shot of your settings or of the image could be very helpful too.
    Please read this FAQ for advice on how to ask your questions correctly for quicker and better answers:
    http://forums.adobe.com/thread/419981?tstart=0
    Thanks!

  • I have Photoshop CS5 and a Epson 3880 . The print setting dialogue box won't open when selecting color output PRINTER MANAGES COLORS

    I have Photoshop CS5 and a Epson 3880 . The print setting dialogue box won't open when selecting color output PRINTER MANAGES COLORS
    It does ope when selecting PHOTOSHOP MANAGES COLOURS . This is first time in 7 year this has happened.
    Any one with ideas/

    What is your screen resolution?
    What operating system?

  • Photoshop CS5 already in 32-bit mode; Lighting Effects filter not showing in the Filter Menu

    Photoshop CS5 already in 32-bit mode; Lighting Effects filter not showing in the FIlter Menu. Please help!?

    Noel Carboni wrote:
    Doesn't a Mac have a definitive way to check to see whether an application is running in 64 bit mode or 32?  Some kind of process manager or something?  22 posts have gone by and the original poster doesn't yet seem convinced that it is actually running in 64 bit mode.
    I don't know why there has been doubt since post #12 where I explained that Ps must be running in 64-bit mode when more than 2100 MB RAM is reported in Preferences.
    Anyway, here's a screenshot of Activity Monitor showing CS6 in 64-bit mode and CS5.1 in 32-bit mode.

  • How to disable the printer's color management in Photoshop CS5 with Mavericks?

    Hi there, does anyone know how to disable the printer's color management in Photoshop CS5 with Mavericks? There doesn't seem to be an option. Could you help? Many thanks

    Just select Photoshop Manages Color, and the printer driver color options should be disabled.

  • Everything is Green in RGB color space in Photoshop CS5 Mac

    The image explains it all.
    CMYK works fine, but RGB doesn't. The preview (in the channels pane) looks fine though.
    Pixelmator had the same problem, but I fixed it by turning off color management in Pixelmator.
    My question is, how can I fix this problem in a legal copy of Photoshop CS5 Extended?
    My Monitor is a dell e193fp, and am running Mac OS X 10.7.2.
    My video card is an ATI Radeon HD 4600, and I have a Mid-08 Mac Pro.

    It could be your display profile, or a problem with the video card drivers.
    I'd bet on the profile.
    Also: RGB is not a colorspace. RGB is a color model, or color mode.  A model or mode describes the number of channels, not the meaning of the channels.
    sRGB and Adobe RGB are colorspaces.  A colorspace describes the meaning of the color channels (a specific red, a specific green, a specific blue, a specific white point, a specific tone curve) for a given mode or model.
    For a color mode or model, there can be many spaces.

  • Photoshop cs5 crash when using the color picker since Yosemite update

    Hello,
    I have photoshop crashing when I use the color picker outside the canvas, like on the black background. I got this problem since I upgraded my mac with Yosemite. I got this issue on my Imac and my Macbook pro. My version of Photoshop cs3 don't have this problem.
    Is there any upgrade soon for photoshop cs5 to solve this issue? It looked online and I am not the only one with this problem.
    After paying 800$ for cs3 and 250$ for cs5 upgrade, I don't want to pay again for the cloud version.
    Thanks,
    Martin

    adobe::q::QString&, adobe::q::QAttributeList&, adobe::q::QDocument*, adobe::q::QProject*, long) + 4053396
    3   com.adobe.Photoshop           0x00000001006bd842 AWS_CUI_GetVersionComments(OpaqueWindowPtr*, adobe::q::QDocument&, adobe::q::QString&, adobe::q::QAttributeList&, adobe::q::QDocument*, adobe::q::QProject*, long) + 4068262
    4   com.adobe.Photoshop           0x00000001006bdc99 AWS_CUI_GetVersionComments(OpaqueWindowPtr*, adobe::q::QDocument&, adobe::q::QString&, adobe::q::QAttributeList&, adobe::q::QDocument*, adobe::q::QProject*, long) + 4069373
    5   com.adobe.Photoshop           0x000000010038ba51 AWS_CUI_GetVersionComments(OpaqueWindowPtr*, adobe::q::QDocument&, adobe::q::QString&, adobe::q::QAttributeList&, adobe::q::QDocument*, adobe::q::QProject*, long) + 718261
    6   com.adobe.Photoshop           0x0000000100df2ab4 AWS_CUI_GetVersionComments(OpaqueWindowPtr*, adobe::q::QDocument&, adobe::q::QString&, adobe::q::QAttributeList&, adobe::q::QDocument*, adobe::q::QProject*, long) + 11626008
    7   com.adobe.Photoshop           0x00000001000c4d32 0x100000000 + 806194
    8   com.adobe.Photoshop           0x00000001000c4be9 0x100000000 + 805865
    9   com.adobe.Photoshop           0x00000001000c4be9 0x100000000 + 805865
    10  com.adobe.Photoshop           0x00000001000c4be9 0x100000000 + 805865
    11  com.adobe.Photoshop           0x00000001000c4be9 0x100000000 + 805865
    12  com.adobe.Photoshop           0x00000001000c4be9 0x100000000 + 805865
    13  com.adobe.Photoshop           0x00000001000c4be9 0x100000000 + 805865
    14  com.adobe.Photoshop           0x00000001000c9fb9 0x100000000 + 827321
    15  com.adobe.Photoshop           0x0000000100cdf3f8 AWS_CUI_GetVersionComments(OpaqueWindowPtr*, adobe::q::QDocument&, adobe::q::QString&, adobe::q::QAttributeList&, adobe::q::QDocument*, adobe::q::QProject*, long) + 10497884
    16  com.adobe.Photoshop           0x0000000100cdb13e AWS_CUI_GetVersionComments(OpaqueWindowPtr*, adobe::q::QDocument&, adobe::q::QString&, adobe::q::QAttributeList&, adobe::q::QDocument*, adobe::q::QProject*, long) + 10480802
    17  com.adobe.Photoshop           0x00000001000677e1 0x100000000 + 423905
    18  com.adobe.Photoshop           0x00000001006b099a AWS_CUI_GetVersionComments(OpaqueWindowPtr*, adobe::q::QDocument&, adobe::q::QString&, adobe::q::QAttributeList&, adobe::q::QDocument*, adobe::q::QProject*, long) + 4015358
    19  com.adobe.Photoshop           0x00000001000679e4 0x100000000 + 424420
    20  com.adobe.Photoshop           0x0000000100065f1b 0x100000000 + 417563
    21  com.adobe.Photoshop           0x00000001012dba1e AWS_CUI_GetVersionComments(OpaqueWindowPtr*, adobe::q::QDocument&, adobe::q::QString&, adobe::q::QAttributeList&, adobe::q::QDocument*, adobe::q::QProject*, long) + 16774530
    22  com.adobe.Photoshop           0x00000001012d4411 AWS_CUI_GetVersionComments(OpaqueWindowPtr*, adobe::q::QDocument&, adobe::q::QString&, adobe::q::QAttributeList&, adobe::q::QDocument*, adobe::q::QProject*, long) + 16744309
    23  com.apple.AppKit              0x00007fff8fed2f4f -[NSWindow _reallySendEvent:] + 12827
    24  com.apple.AppKit              0x00007fff8f95d50c -[NSWindow sendEvent:] + 368
    25  com.adobe.owl                 0x0000000103687f55 OWLRemoveObjCExceptionCallback + 617
    26  com.adobe.owl                 0x0000000103689fa4 OWLRemoveObjCExceptionCallback + 8888
    27  com.apple.AppKit              0x00007fff8f90f096 -[NSApplication sendEvent:] + 2238
    28  com.adobe.Photoshop           0x00000001012e242e AWS_CUI_GetVersionComments(OpaqueWindowPtr*, adobe::q::QDocument&, adobe::q::QString&, adobe::q::QAttributeList&, adobe::q::QDocument*, adobe::q::QProject*, long) + 16801682
    29  com.adobe.Photoshop           0x00000001012e1be1 AWS_CUI_GetVersionComments(OpaqueWindowPtr*, adobe::q::QDocument&, adobe::q::QString&, adobe::q::QAttributeList&, adobe::q::QDocument*, adobe::q::QProject*, long) + 16799557
    30  com.apple.AppKit              0x00007fff8f79be98 -[NSApplication run] + 711
    31  com.adobe.Photoshop           0x00000001012e04a4 AWS_CUI_GetVersionComments(OpaqueWindowPtr*, adobe::q::QDocument&, adobe::q::QString&, adobe::q::QAttributeList&, adobe::q::QDocument*, adobe::q::QProject*, long) + 16793608
    32  com.adobe.Photoshop           0x00000001012e0f01 AWS_CUI_GetVersionComments(OpaqueWindowPtr*, adobe::q::QDocument&, adobe::q::QString&, adobe::q::QAttributeList&, adobe::q::QDocument*, adobe::q::QProject*, long) + 16796261
    33  com.adobe.Photoshop           0x00000001000682e6 0x100000000 + 426726
    34  com.adobe.Photoshop           0x00000001002371f1 0x100000000 + 2322929
    35  com.adobe.Photoshop           0x0000000100237281 0x100000000 + 2323073
    36  com.adobe.Photoshop           0x00000001000022f4 0x100000000 + 8948
    Thread 1:: Dispatch queue: com.apple.libdispatch-manager
    0   libsystem_kernel.dylib        0x00007fff8cbb622e kevent64 + 10
    1   libdispatch.dylib             0x00007fff8af53a6a _dispatch_mgr_thread + 52
    Thread 2:
    0   libsystem_kernel.dylib        0x00007fff8cbb5946 __workq_kernreturn + 10
    1   libsystem_pthread.dylib       0x00007fff8f5564a1 start_wqthread + 13
    Thread 3:
    0   libsystem_kernel.dylib        0x00007fff8cbb5946 __workq_kernreturn + 10
    1   libsystem_pthread.dylib       0x00007fff8f5564a1 start_wqthread + 13
    Thread 4:
    0   libsystem_kernel.dylib        0x00007fff8cbb5946 __workq_kernreturn + 10
    1   libsystem_pthread.dylib       0x00007fff8f5564a1 start_wqthread + 13
    Thread 5:
    0   libsystem_kernel.dylib        0x00007fff8cbb5946 __workq_kernreturn + 10
    1   libsystem_pthread.dylib       0x00007fff8f5564a1 start_wqthread + 13
    Thread 6:
    0   libsystem_kernel.dylib        0x00007fff8cbb5132 __psynch_cvwait + 10
    1   com.adobe.amt.services        0x000000010a9e3c53 AMTConditionLock::LockWhenCondition(int) + 37
    2   com.adobe.amt.services        0x000000010a9dccce _AMTThreadedPCDService::PCDThreadWorker(_AMTThreadedPCDService*) + 92
    3   com.adobe.amt.services        0x000000010a9e3cbe AMTThread::Worker(void*) + 28
    4   libsystem_pthread.dylib       0x00007fff8f5582fc _pthread_body + 131
    5   libsystem_pthread.dylib       0x00007fff8f558279 _pthread_start + 176
    6   libsystem_pthread.dylib       0x00007fff8f5564b1 thread_start + 13
    Thread 7:
    0   libsystem_kernel.dylib        0x00007fff8cbb5946 __workq_kernreturn + 10
    1   libsystem_pthread.dylib       0x00007fff8f5564a1 start_wqthread + 13
    Thread 8:
    0   libsystem_kernel.dylib        0x00007fff8cbb0582 semaphore_timedwait_trap + 10
    1   com.apple.CoreServices.CarbonCore 0x00007fff961bc658 MPWaitOnSemaphore + 87
    2   MultiProcessor Support        0x0000000110666b93 ThreadFunction(void*) + 69
    3   com.apple.CoreServices.CarbonCore 0x00007fff961bc904 PrivateMPEntryPoint + 58
    4   libsystem_pthread.dylib       0x00007fff8f5582fc _pthread_body + 131
    5   libsystem_pthread.dylib       0x00007fff8f558279 _pthread_start + 176
    6   libsystem_pthread.dylib       0x00007fff8f5564b1 thread_start + 13
    Thread 9:
    0   libsystem_kernel.dylib        0x00007fff8cbb0582 semaphore_timedwait_trap + 10
    1   com.apple.CoreServices.CarbonCore 0x00007fff961bc658 MPWaitOnSemaphore + 87
    2   MultiProcessor Support        0x0000000110666b93 ThreadFunction(void*) + 69
    3   com.apple.CoreServices.CarbonCore 0x00007fff961bc904 PrivateMPEntryPoint + 58
    4   libsystem_pthread.dylib       0x00007fff8f5582fc _pthread_body + 131
    5   libsystem_pthread.dylib       0x00007fff8f558279 _pthread_start + 176
    6   libsystem_pthread.dylib       0x00007fff8f5564b1 thread_start + 13
    Thread 10:
    0   libsystem_kernel.dylib        0x00007fff8cbb0582 semaphore_timedwait_trap + 10
    1   com.apple.CoreServices.CarbonCore 0x00007fff961bc658 MPWaitOnSemaphore + 87
    2   MultiProcessor Support        0x0000000110666b93 ThreadFunction(void*) + 69
    3   com.apple.CoreServices.CarbonCore 0x00007fff961bc904 PrivateMPEntryPoint + 58
    4   libsystem_pthread.dylib       0x00007fff8f5582fc _pthread_body + 131
    5   libsystem_pthread.dylib       0x00007fff8f558279 _pthread_start + 176
    6   libsystem_pthread.dylib       0x00007fff8f5564b1 thread_start + 13

  • Photoshop CS5: Any color with zero red information will turn black

    I've been having this problem ever since I installed Photoshop CS5 (12.0.4) on a Windows 7 64-bit machine. I've used the program on a Windows Vista 64-bit PC in the past with no problems.
    Any color that has zero red information will turn black when in RGB mode and in either 8 or 16-bit mode. If I use the paintbrush, for example, a color with RGB 0/100/100 will be black. However, the color 1/100/100 will not. This problem also occurs with imported images. I've only tried JPEG and PNG so far. The problem does not save out though, as any image exported from Photoshop will appear fine. The issue seems to go away when in 32-bit mode, but it's a little RAM-intensive, and the file sizes are quite large.
    I have reinstalled Photoshop, reset its preferences, and reinstalled my video card's drivers (I have a Radeon HD 7870). My PC has 8 GB of RAM and plenty of free hard drive space.
    Below is a screencap of what's going on. I'm a bit lost here...any help would be greatly appreciated!

    It's a well-known issue with current ATI drivers and Photoshop's GPU-accelerated color-management logic.
    You can work around it a couple of different ways:
    1.  You can install ATI's latest Catalyst 13.2 beta driver, which does solve the problem, or you can uninstall and drop back to Catalyst 12.8.
    2.  You can switch to Basic GPU mode (and restart Photoshop).  Basic mode moves the color-management logic into the CPU.  This might be a workaround you'd prefer to take until AMD releases their next non-beta driver where the problem is solved.
    See also:  http://forums.adobe.com/message/5004198#5004198
    -Noel

Maybe you are looking for