When I open up Bridge CS3, I look at the images, and they look FINE in the content thumbnails... UNTIL I CLICK ON THEM to bring them up bigger in the PREVIEW pane. Then the thumb goes all wacky, and it looks HORRIBLE!

They look just like I want them to, until I click on them, then they jump to looking horrible. I open them in CR, and they still look BAD BAD BAD.

When I was taking them, I kept checking the LCD, and they looked like the ones in Bridge that HAVEN'T been clicked on. I have NO idea what's going on!!!

All of the thumbs over in the content area look just like I want, until I click on them. Then that one goes icky & one or two AROUND them.

Here's a quick screenshot. Can you tell which one I clicked on???

Does ANYONE know what's going on???

Click to view attachment

I checked to make sure NO AUTO CORRECTION is turned on in CR or Bridge

When I open up an image in CR, it looks like crap, and "auto" is NOT set. It's set to "default" ugh. I've tried and tried to look at every CR & Bridge setting, and I can't find how to get back what I see in the LCD and what I see in a thumbnail that hasn't been clicked.

carey, we talked about this. i'm posting to bring attention to this problem and prove that it isnt just you having issues with adobe software!!!

i've always noticed this but it never bothered me horribly until I processed the mexico wedding images with lightroom, and more recently a modeling shoot I did. when i import images into lightroom, they look great.... in thumbnail view. once i click on one to select or open it, the color immediately changes to a sort of muddy, dumbed-down, sh*tty looking version of the image! when i open the images in DPP, they look like what the thumbs looked like in LR before this mysterious conversion took place. rich, natural looking color and accurate tonality.

now, before i post the images, i want to reiterate that neither carey or i have changed any settings on our software to make auto corrections. i do not have any preset develop settings loading in lightroom, nor do i have an auto correct feature turned on ANYWHERE on either program. THIS IS EXTREMELY FRUSTRATING!!!!!!!!!!!!

someone... please help us! i'm going to call adobe and initiate some dialogue with them regarding this matter, but i'm curious to know if anyone knows what could be causing this problem.

First, a look at how DPP shows my images with no processing, no auto correction:



Next, here's how LR 1.0 makes the images look... no processing, no auto correction:



And here's a side-by-side comparison screen shot. DPP is on the right, LR is on the left. WTF?!

I hope you two can get someone to help you out. I know when I had a similar problem...it was a difference in color space. RGB and Adobe. The adobe always looked wonky to me.

http://barefoot-memories.com/cs3/
I took a video of what Bridge CS3 is doing, click by click.
This is SO frustrating! Even more so because it was NOT doing this TWO DAYS AGO when I processed out pictures from Thursday!!!! I went thru them in Bridge, processed them in CR, pushed out jpgs, peachy keen jelly bean.
now TODAY, what you see in that video is happening.
I went back to pictures I took Thursday -- and now Bridge is making them look WACKY, too!!!!!
I have been racking my brain trying to figure out what I could have changed, what settings I could have changed, and I can not figure out anything.
I made sure I was running the latest version of Bridge (upgraded from 2.0 to 2.1)... same thing!!

UGH.
I have to call Adobe on Monday. sheesh.

Carey, does anything happen when you select the image and go to Edit -> Develop Settings -> Clear Settings?

I've had the same thing happen to me on occasion but I have no idea how to reproduce the problem.

Thanks..
tried that...
nothing happens.

I tried applying one of my saved CR settings, it changed to that setting (which was crap on the picture I chose), then tried to go back to "default" or "as shot", and it went back to the crappy blue mess.

UUUUUUGH How frustrating for you. I really hope you get this figured out. Were these the pictures you took with Mark or Five? Would that matter? I am just throwing things out there ( I am sure you have thought of all this already!)

I posted about this and if you search under my login name you will find a little of what happened to me. All my CS3 settings were fine and nothing I did would help. There is an update, but unfortunately Canon and NIkon have proprietary RAW information that they of course will not share to anyone. Thus third party companies like Adobe have to make their best guess at how to read Canon or Nikon's Raw files. So I guess it boils down to that RAW converter. Bridge and Camera Raw is a time saveer but Canon and Nikon's software brings forth more appealing images straight out of camera. So take your pick.

well dag nab it! That was my suspicion -- adobe not being able to "understand" everything that's in the RAW files.
The VERY FRUSTRATING thing is that on Thursday I was able to use CS3 with no problems -- processed out jpgs from my RAW images. Why can't I do that now, on the weekend? Bridge CS3 wasn't altering my images at all 2 days ago, and now it is.
I went back to Bridge CS2 and looked at RAW pics from the 5D. It does NOT alter the image at all.
I open up Bridge CS3 and look at RAW pics there, and I see it alter them a lot like LR is doing to Meeks'.
CS3 is really pissing me off!

charles, i suspected it was something like that... what a PAIN IN THE ASS!!!!!

Thanks for posting though... im going to go cry now.

I'm calling Canon & Adobe in the morning.
The guy who sold me this camera (brand spankin' new, authorized Canon shop) said he knows lots of people with this camera and CS3 who are not having this problem, so he's putting me in touch with Canon tech guys he knows.

We'll see what they say!

ADOBE UPDATE:

I just got off an hour long call with Adobe tech support.
They were very helpful, as they always have been.
The nitty gritty is that something in my Windows user account was affecting how PS CS3 was running because when we created a brand new user account and ran Bridge, everything worked as it should -- no ugly blue pictures.
There's no real way to tell what changed in my user account, and the lady from Adobe didn't really care to find out once we saw that Bridge & CS3 were working correctly in a new user account.
She said it could be anything and Windows is so huge that there's no way for them to find out exactly what happened.
If you're a mac lover, please spare me the Windows bashing, OK? Trevor's still having his LR issues, and he's on Mac, so rake is reasy if you want to venture in to Windows bashing!

Nathan and I had a convo on AIM about this as well. I have taken the exact same image, saved it at a JPG level 12 in ACR, then gone to dpp and done the same. The DPP file has about 20-30% more file size than the ACR converted JPG file. Very interesting stuff. And I too have found that the DPP files have a rich saturated colour straight out of the software.

Now that I've looked at the images in both DPP and ACR, DPP seems to be "richer". But for some images, I need the ACR CS3 power that I can't get in DPP (lowering exposure, bumping up the mids a bit w/o flattening it out so much).
I can't decide which I'm going to use. ... but at least I CAN use both now!!

i upgraded to DPP 2.2.whatever and it still sucks. i mean, the results are great but i see no real difference in the interface... im so mad still.

btw, before anyone gives carey a hard time about using windows.... just dont. i give her enough crap about it already

You know I have the MBP, so lay off!

i know, i know! thats why i dont give u more crap

Carey,

I wouldn't consider it fixed because, as you stated, you were fine on Thursday, and then it went screwy over the weekend. Who's to say your new Windows user is going to be rock solid?

So, don't be surprised if this happens again. At least you now know a quick fix in case your deadline is tight. I'm still using CS2 because I don't usually jump on the software upgrade train until about a year after it is released. Too many bugs in the early releases.

YUP! I know -- I'm worried about that happening! That's why I'm not going to take all the effor to migrate everything over to a new user accout. I'm just going to keep that plain 'ole user account there for Bridge/ACR.



BELIEVE ME, I would still be using CS2 as well if Adobe didn't have me by the proverbial nads and FORCE me into upgrading just to be able to see RAW images from this new camera!!!!! That really ticked me off (and I told them so... as if they care or hadn't heard it before).

Now, at least I have the choice between ACR/Bridge-CS3 and DPP. I really like the management tools of Bridge, but I know DPP has all of the same stuff (batch processing, batch renaming, etc), just a little different in the interface.
I really need/want the exposure control in ACR to be available. I'm not happy about having to spend $199 and a TON of heartache to get it, though!!!

I don't know if this is the problem.....

but I believe that initially, from what I can remember (I used to use bridge cs2 and then switched to lightroom), bridge (and from what I can see, LR too) creates the thumbnails from the embedded JPEG files in the RAW, so they'll look just like they looked on the back of the camera LCD screen. I believe it updates thumbnails in the background when it gets to them.

I noticed when I would go into a folder for a new shoot where no thumbnails were generated, and then jump halfway into the photo collection, that same thing would happen to me. The thumbnails looked great and then I'd click them and the preview window would come up, and it would look great... for about two seconds, and then turn ugly. I was told this was because the program just quickly displays the embedded JPEG file while it reads all the RAW data and creates the RAW preview and thumbnail. Once all the RAW data is loaded and ready to display, it switches out the JPEG preview and puts up the RAW preview, which is usually dull, ugly, and off colour. (One of my cameras produces overly orange files, another is overly reddish, and looks like yours produces a lot of blue)

Once the Program sees that you are looking at files halfway into the shoot, it seems to switch the processing order and begins to generate the ugly RAW thumbnails/previews for the photos right around the one you selected, thinking that you are going to be working in that area.

Again, I don't know if this is your problem or not, but both bridge and LR does the same things to me. I have to bring the colour back reality with the colour calibration settings and then start doing the rest of the processing. (i.e. exposure, contrast, saturations etc...)

Yup. From what I've learned over the last 2 weeks, Adobe is doing a "best guess" to read the RAW data out of the camera, since Canon won't "share" (Nikon won't either). The jpg that the camera creates is created by CANON, so it looks RIGHT. Adobe tries as hard as it can to read the RAW data out of the Canon camera but ends up doing a "best guess". That's why the Canon view of a Raw file inside Canon's DPP looks RIGHT, and the Adobe view inside ACR & Bridge looks WRONG.
I didn't have this big of a problem w/my 5D, and CS3 has been driving me so nutso with instability, I just got fed up last night and returned my Mark III this morning. I was spending WAY too much time in ACR trying to get the Canon Raw files to look decent (back to normal). Maybe I should have just shot JPEG on the Mark III. But why would I have to shoot jpg on a $4000+ camera to get good/reliable/accurate images!?

I'm happy with the decision I made. It's a bummer that the fancy schmantsy Mark III wasn't all it was cracked up to be for me, but oh well.

~Carey

[quote name='MeeksDigital' date='June 16 2007, 10:15 PM' post='154352']
carey, we talked about this. i'm posting to bring attention to this problem and prove that it isnt just you having issues with adobe software!!!

i've always noticed this but it never bothered me horribly until I processed the mexico wedding images with lightroom, and more recently a modeling shoot I did. when i import images into lightroom, they look great.... in thumbnail view. once i click on one to select or open it, the color immediately changes to a sort of muddy, dumbed-down, sh*tty looking version of the image! when i open the images in DPP, they look like what the thumbs looked like in LR before this mysterious conversion took place. rich, natural looking color and accurate tonality.

now, before i post the images, i want to reiterate that neither carey or i have changed any settings on our software to make auto corrections. i do not have any preset develop settings loading in lightroom, nor do i have an auto correct feature turned on ANYWHERE on either program. THIS IS EXTREMELY


FRUSTRATING!!!!!!!!!!!!

someone... please help us! i'm going to call adobe and initiate some dialogue with them regarding this matter, but i'm curious to know if anyone knows what could be causing this problem.

First, a look at how DPP shows my images with no processing, no auto correction:



Next, here's how LR 1.0 makes the images look... no processing, no auto correction:




I have been having this exact same problem in LR!!! EEEEEKKK. I thought it was maybe just me and my D200 and its lack of "butter." I actually compared images that I processed through CS2 a while back and the difference is incredible-- bridge in CS2 looks way better. For some reason, LR is turning my images to mud. What is going on here? Does anyone know what to do???

Trevor figured out the problem & downloaded new profiles for LR (I think?)
PM him, and I bet he can point you in the right direction

ooohhhh, I sure hope so...

my bridge has started wigging out now!!! anyone figure this issue out! mine is doing exactly what trevor's was doing...

Ok, mine has always done this. I thought it was normal?!?