Luminous Landscape Forum

Raw & Post Processing, Printing => Colour Management => Topic started by: Greg D on August 13, 2009, 10:09:00 am

Title: adobe gamma question
Post by: Greg D on August 13, 2009, 10:09:00 am

I recently got a new computer (running Vista 64-bit).  After calibrating the monitor (HP LP2275w calibrated with a Spyder 3), the next time I booted the computer, I got the message "Adobe gamma loader has stopped working".  Didn't surprise me too much, just thought the new profile had turned it off, so I disabled it (Adobe gamma loader, that is) in the startup programs so as not to get the annoying message each time I started the computer.  Next day or so I checked calibration, to find that the gamma was now way off.  So, my question is:  Should Adobe gamma loader be on or off when profiling the monitor?  Or does it matter as long as it stays one way or the other?  And if it should be on, why would it have stopped working and how do I correct it?

Thanks much,
Greg

Title: adobe gamma question
Post by: Jeremy Payne on August 13, 2009, 10:20:14 am

I believe that in the circumstance you describe, both Adobe Gamma and the Spyder Utlity would try to load conflicting profiles at startup.  I had a similar issue a few years ago when I upgraded to a Spyder and stopped "doing it by eye" with Adobe Gamma.

I think you are best off disabling Adobe Gamma, setting your monitor to the factory defaults and starting over with new profile from the Spyder.

Title: adobe gamma question
Post by: digitaldog on August 13, 2009, 10:30:57 am

Kill anything and everything related to Adobe Gamma!

Title: adobe gamma question
Post by: Mark D Segal on August 13, 2009, 11:02:59 am

Adobe Gamma should not be loaded either before you calibrate/profile your display with Spyder 3 or any other device. Go into your Start Menu folder in Windows and permanently disable it from starting up by unchecking that item in the list, then re-calibrate/profile your display starting the process from scratch.

Title: adobe gamma question
Post by: Greg D on August 14, 2009, 12:21:27 pm

Thanks all.  This is kinda what I thought, and did so (that is, disable Adobe gamma and recalibrate).  Looks fine now.
Thanks