Upgrade Issues LR 2015.1 - Hazy Photos

  • 1
  • Problem
  • Updated 4 years ago

This conversation has been merged. Please reference the main conversation: Lightroom: D810 Adobe Standard Profile missing - update lowers contrast of images

All of my photos are now hazy after upgrading to yesterday's release. I was up to date on CC prior to the upgrade. Am I able to roll back to the previous version?

Current info:
Lightroom version: CC 2015.1 [ 1025654 ]
License: Creative Cloud
Operating system: Mac OS 10
Version: 10.9 [5]
Application architecture: x64
Logical processor count: 8
Processor speed: 3.1 GHz
Built-in memory: 16,384.0 MB
Real memory available to Lightroom: 16,384.0 MB
Real memory used by Lightroom: 747.8 MB (4.5%)
Virtual memory used by Lightroom: 2,769.0 MB
Memory cache size: 590.9 MB
Maximum thread count used by Camera Raw: 4
Camera Raw SIMD optimization: SSE2,AVX,AVX2
Displays: 1) 1920x1080

Graphics Processor Info:
NVIDIA GeForce GT 750M OpenGL Engine

Attached photo example. This is the same photo. The one on the right is the original with LR edits (after the upgrade showing new haze). The one on the left is the version I brought into Photoshop for additional edits prior to upgrade. After the upgrade ALL my LR files look hazy like the one on the right.

I know they have this new dehaze option, but these were not hazy prior to the upgrade.
Photo of Jennifer Ona

Jennifer Ona

  • 3 Posts
  • 0 Reply Likes
  • confused

Posted 4 years ago

  • 1
Photo of Becky Sowada

Becky Sowada, Adobe Employee

  • 510 Posts
  • 107 Reply Likes
Hi Jennifer,

Are these images from a Nikon D810? I have a feeling this could be the same as the issue noted here: http://feedback.photoshop.com/photosh...

Photo of Jennifer Ona

Jennifer Ona

  • 3 Posts
  • 0 Reply Likes
Thank you I think that may be it. The string doesn't really provide a solution for what to do until the bough fix though.
Photo of Chris Castleberry

Chris Castleberry, Camera Raw Engineer

  • 378 Posts
  • 115 Reply Likes
Hi Jennifer,

Please try the workaround in the following document.


Hope that helps,

- Chris

This conversation is no longer open for comments or replies.