P: - Green Previews in Filmstrip after Sync

[Paul Tansley]

Noticed this problem a few time now with the latest update 5.2 on OSX.

When I sync some frames in the film strip, some of the frames that have been synced show up with a green preview. Image attached to demonstrate this. The white balance gets reset to some bizarre figure. The original that the images were synching from was set to Auto WB. So no idea why the program decides to change it. Clearly a bug, this has happened quite a few times now.

[Kelly Castro]

Hi Paul,

Can you please provide some additional information on this issue (which camera model was used to shoot the photos? How were they converted to DNG?)

Once I have this info I'll see if I can reproduce the problem, but I may need to ask you to provide a file that displays the issue.

Thanks,
Kelly

[Paul Tansley]

They are Canon 5D3 files. Converted to DNG's in LR5.2 via the Convert to DNG menu option.

It's not a problem with the file though. I think that's probably irrelevant. As the issue is not repeatable on the same file. It's an issue that just appears - randomly, when I sync files. Its doesn't always happen. Maybe 5% of the time if that. But it does re-occur on a fairly regular basis. As I said before, clicking in the Dev module's history, one step back, one step forward, or simply redoing the sync produces the correct preview.

[Kelly Castro]

Thanks Paul. We're looking into it.

[MadManChan2000]

Paul, a follow-up question for you: When you are syncing the (auto) WB from the source image to the other images in the selection, do the target images have other image settings already? That is, have you previously adjusted (in Develop) the other images? Or, is the act of syncing the WB the first thing that you do (before editing the other images)?

This may seem like an odd question, but the order in which certain operations are applied can make a difference in whether the bug manifests or not.

Thanks,
Eric

[Paul Tansley]

Sorry Eric, I don't know the answer to that one. I really can't remember what the previous white balance was. Next time the issue occurs, I will check by going back in the files history.

[Paul Tansley]

Hi Eric

So, has happened today. As you can see in the screen grab below. In the history, the white balance was set to "As Shot" in all previous steps. Only on the last Synchronise Settings step was it changed to a Custom setting.I synced 4 frames, the original plus 3 others either side. It was synced from the 4th frame which had Auto White Balance set. The other 2 went to Auto WB as expected, this one went green with the settings shown. Go figure.

[MadManChan2000]

Thanks for the update, Paul. I noticed in your screenshot that for this image (the one that became green), the second-from-top history state is named "From Metadata". Do you recall what you did during that step?

Thanks.
Eric

[Guest]

I'm having the same problem. I shot these with a Nikon D3S in RAW format.

[MadManChan2000]

Hi Katie -- do you recall if you had done any other processing or steps with this image before you synced the WB? We're actively trying to track down the issue, and any clues you and Paul (or anyone else) can provide would greatly help.

Thanks!
Eric

[Guest]

I had done no other processing. All are straight from import. Let me know if you have any other questions!

[Guest]

I'm sure it will do it again - it's been pretty frequent today. So, let me know if there is some other screen shot that might help.

[MadManChan2000]

Thanks Katie -- and you are using version 5.2 of Lightroom, is that right?

[Guest]

Yessir. It never did this before I upgraded to 5.2

[MadManChan2000]

Ok thanks. And to be clear ... you changed the WB of the "source" image to Auto, and then you tried to sync this to the other images -- is that right?

[Guest]

No, actually. I tried Auto WB first, and didn't love it, so I fiddled with it. So the source image was actually Custom.

[Guest]

It just did it again, and I did have the WB to Auto. 😉

[MadManChan2000]

Katie, does it ever happen when you have the WB on the "source image" set to something besides Auto? For example, if you have it set to Custom or to Daylight, or something else? Thanks.

[Paul Tansley]

Hi Eric - in response to your earlier question regarding reading from the Metadata. I import the images onto my MacBook Pro. They are assigned a WB of "As Shot". The files are then transferred to the iMac. The problem has only been seen on the iMac, but that's not surprising as that is where I do most of my editing. I do minor editing on the MBP.

So far as I know, the image in question would have had an As Shot WB when imported, so that would have been the Metadata setting. Not Auto.

Sorry that probably doesn't help much. But at least I know the problem has been acknowledged and is being looked into. If it happens again, I'll post as much detail as I can.

Paul

[Guest]

I did a Sync All (option command s)...so yes. I had adjusted white balance, as well as a lot of other things! Probably: Exposure, Contrast, Highlights...pretty much everything in the Basic Panel. I also adjusted the sharpening.

[Guest]

I've played with it a little bit, and it's only doing the green thing when I have "Auto" WB the image. It doesn't do it if the WB is Custom. And it only does it sometimes on some images. That's the hard part. Sorry...Hope that helps

[MadManChan2000]

Ok thanks, Paul and Katie. I think the main clues I've gathered (which are common to both your cases) are:

1. you're always syncing Auto WB from the source image to the other images
2. in some cases, the target images have their WB popup menus set to Custom (instead of Auto), and the temp & tint values are set all the way to the left (temp=2000, tint=-150) which is what is producing the very strong green result

We'll keep looking internally for the problem, but this is a helpful start.

Any other patterns you can find ... please let us know. Thanks.

[Guest]

I have an image that is doing it to. I ran it through ALL of the WB options. It only does it when WB is set to Auto. It does fine on every other WB setting. (So, probably I was wrong on my original answer to that question! I probably synced it on WB Auto, but since then played with it)

[MadManChan2000]

Yup, that would make sense. Thanks Katie.

[MadManChan2000]

Hi Paul and Katie,

I believe we've identified the underlying cause and should have a fix available soon. Thanks to both of you for providing info and details. I should emphasize that the fact that you provided your screenshots was very helpful (even critical) to finding the problem.

[Paul Tansley]

That's excellent to hear. Thank you for letting us know Eric. Having good communication between the end users and the makers is fantastic. We don't complain because we want to, we complain in the hope that the product will be improved. So when it is, that's just great. We all win.

Superb stuff