Help - issue with CS3 Camera raw and CS3 colour

  • Thread starter Thread starter Yv
  • Start date Start date
Found this on t'internet.

Apparently, if you calibrate with Adobe Gamma then use Photoshop CS, it disables the monitor calibration. To re-enable it, go to the View Menu, select "Proof Setup" and tick "Monitor RGB" Then , again in the "View" menu, tick "Proof Colors" or press Control and Y. Your monitor should then assume its calibration. From what I read, this was permanently enabled in PS6, but has to be selected every time a print is loaded into CS. Don't ask me why - it sounds to me like a huge mistake by Adobe. You can now work with the proper profile selected and see the colors properly.

Don't know if it's connected to your issue.
 
I've also read that it could be a problem caused by an update to your monitor driver. Try rolling back the driver.

Or it could be that NEF files are 12-bit and Photoshop opens them as 8-bit and screws the colours. Make sure you have the latest NEF plugins from Adobe. Nikon software also adds a NEF plugin to Adobe Bridge. If you've installed or updated any Nikon software it may have messed up the plugin. Find it and uninstall it.

Have you changed your in-camera colour settings recently?
 
A lot to go at - firstly, nothing changed between it working perfectly well on Sunday and not working monday, no updates for anything, either adobe, huey or monitor related. Camera setting shouldnt make a difference because its affecting ALL image files from last 3 years.

I tried a system restore, with no joy. I have uninstalled and reinstalled CS3, again, unsuccessfuly. Cleared all the preferences, still got the problem.

When I get a chance this afternoon I am going to uninstall the calibrator and reinstall the monitor/graphics card drivers, just to be sure.

I am starting to suspect a corrupt file somewhere, but which file is like a needle in a haystack - I am thinking now of also uninstalling all adobe applications, running a windows repair console to make sure there are no disc errors anywhere and seeing what that does, but tbh, I dont hold out much hope :shake: A full format-start-from-scratch seems a bit extreme but its just so wierd that its gone from functioning perfectly to totally effing up with no rhyme or reason.

Edit: Sorry, should have said thankyou everyone for your input so far, its what I love about this place, everyone is willing to try and help, so again, thankyou all! :hug:
 
A thought.....

As the problem seems to occur when Colour management is turned on, in both Photoshop and Bridge, I wonder if the conversion engine has got screwed ( a technical term!!).

Have a look in the preferences panel in photoshop under advanced and see what conversion engine you are using. With a normal installation you should have both the Adobe and the Microsoft options. Try changing engine, reboot, check the changes have taken place and see if the problem has gone away.

Beats the hell out a reformat. However If you do I bet the machine runs a damn site quicker with all the **** (another technical term) removed. It did on mine.
 
Well the real bummer is that it is a fairly new machine without too much of that c**p on it - however, I am trying something. A few weeks ago I installed Virtual PC on it in the hope of running a couple of work related legacy programs that won't run on the main computer because its a 64bit OS - so just trying an install on that and seeing what happens, merely for curiosity value, just the result should be interesting.
 
Well good news and bad - everything works perfectly inside virtual PC, which leads to the bad news, I am now convinced of a file corruption that adobe doesnt like somewhere on the windows setup on main OS, driver related, or graphics card or something. So, when I have a few hours to spare, I am going to do the driver reinstalls and then run repair console before taking the final format step as a alst resort if I have to. However it does mean I can now run things properly, as its no real hardship running within virtual PC. Phew!!
 
Glad to hear that it's all working OK. I would be surprised though if its a video driver problem as that should have manifested itself in both bridge and Photoshop.

Anyway good luck

John C
 
If anything is corrupt, chances are its a monitor profile. Someone could send you a 'clean' sRGB ICC and then you could try rebuilding your Huey modified one?
 
:woot: UPDATE!!

ok, not had much chance to play last day or two, but yesterday whilst doing some work, I got the pop up thing telling me there were adobe updates, so as I was doing other stuff, I left them to install as I figured I had nothing to lose and there was an outside chance they may solve the issue.

Couple of hours later, looking for an image to put into a webpage I was working on, I opened Bridge and wanted to scream - THAT was all funny hues to!! Worse, the tick box in the preferences that turned off colour management had gone :bonk:

So, late last night, decided to have one last go at resolving the issue, starting by just uninstalling all adobe applications including stuff like Acrobat, just everything with the intentions of then sorting monitor profiles, drivers etc. On opening add/remove programs, there was a new 'thing' - trouble is, I cant recall what it was called exactly, but it was some like Adobe Colour Tools or something... it certainly wasn't there prior to the updates, so I removed that first - to show how new it was, you know windoze tells you how often an application is used - this seemed unused, although having said that, as it didnt appear in the prgram list as something you could open, that could account for it, but I am about 99% certain it wasn't there before the update.

Of course because it was colour related, I couldnt resist clicking Bridge open again just to see if made any difference and...it did, that at least was back to normal. Phew! So of course, a double click on a pic and CS3 and ACR are open...NORMALLY!! :D Checked it was running with sRGB on everything and not just discarding embedded stuff and it was. All now running again on North American General Purpose 2 settings, exactly as it should be.

:woot::woot: I think it finally sobered up! :lol:


Anyway, huge thanks to everyone that offered assistance and especially Divine for his continued input.

Still not really sure what caused the problem, and it would be nice to know for future refence but at least its seems to be sorted for now :thumbs:
 
Great news! Being a computer numpty I haven't been able to contribute or offer any helpful suggestions but i've been watching this thread with baited breath hoping it would have a happy ending. Really pleased you got it sorted.:)
 
:woot: UPDATE!!

ok, not had much chance to play last day or two, but yesterday whilst doing some work, I got the pop up thing telling me there were adobe updates, so as I was doing other stuff, I left them to install as I figured I had nothing to lose and there was an outside chance they may solve the issue.

Couple of hours later, looking for an image to put into a webpage I was working on, I opened Bridge and wanted to scream - THAT was all funny hues to!! Worse, the tick box in the preferences that turned off colour management had gone :bonk:

So, late last night, decided to have one last go at resolving the issue, starting by just uninstalling all adobe applications including stuff like Acrobat, just everything with the intentions of then sorting monitor profiles, drivers etc. On opening add/remove programs, there was a new 'thing' - trouble is, I cant recall what it was called exactly, but it was some like Adobe Colour Tools or something... it certainly wasn't there prior to the updates, so I removed that first - to show how new it was, you know windoze tells you how often an application is used - this seemed unused, although having said that, as it didnt appear in the prgram list as something you could open, that could account for it, but I am about 99% certain it wasn't there before the update.

Of course because it was colour related, I couldnt resist clicking Bridge open again just to see if made any difference and...it did, that at least was back to normal. Phew! So of course, a double click on a pic and CS3 and ACR are open...NORMALLY!! :D Checked it was running with sRGB on everything and not just discarding embedded stuff and it was. All now running again on North American General Purpose 2 settings, exactly as it should be.

:woot::woot: I think it finally sobered up! :lol:


Anyway, huge thanks to everyone that offered assistance and especially Divine for his continued input.

Still not really sure what caused the problem, and it would be nice to know for future refence but at least its seems to be sorted for now :thumbs:

Was it Adobe color common settings per chance?
 
NP
 
Back
Top