R
Ruahrc
Guest
I was working on a large panoramic shot today and spent a long time getting everything right the way I wanted in the develop module. I then went back to the library view ("E") where the program spent a lot of time rendering the full sized view. When it was done rendering the image looked different than it had looked in the develop module. I wasn't sure what to make fo this but I then proceeded to export the image to JPG. I selected sRGB as the color space since I was going to email this picture and when the export was finished the JPG looked like the (crappy) version I saw in the library module!
Thinking it may have been color space issues (unlikely but who knows) I exported in the other two formats, AdobeRGB and ProPhotoRGB. Neither worked. Still looked like the crappy version in the library module.
This is the first time I've seen this happen, or at least seen it happen to a degree that I noticed it. What is the cause, and is there a solution? Since we have to edit things in the develop module it is a hopeless guessing game to try to make adjustments in the develop module not knowing what they will look like in the library module or upon export!
I should note that this was the first time I really made heavy use of the local adjustments brush. The image I was working on had white balance problems wherein one portion of the image needed a very cool white balance whereas the other portion needed a warm white balance. To fix this I applied the warm white balance all over using the WB adjustment tool, and then I painted in a blue cast using the adjustment brush over the parts of the image that were too yellow as a result of the WB adjustment, in order to bring the colors back to neutral. Could this be causing the problem? Switching back and forth between the two modules it looks like the only places where the previews differ is in the areas where I adjusted the color using the local adjustment brush.
Ruahrc
P.S. this is LR2.1 updated yeseterday. Source panoramic file was a TIFF in ProPhotoRGB color space stitched in Hugin.
Thinking it may have been color space issues (unlikely but who knows) I exported in the other two formats, AdobeRGB and ProPhotoRGB. Neither worked. Still looked like the crappy version in the library module.
This is the first time I've seen this happen, or at least seen it happen to a degree that I noticed it. What is the cause, and is there a solution? Since we have to edit things in the develop module it is a hopeless guessing game to try to make adjustments in the develop module not knowing what they will look like in the library module or upon export!
I should note that this was the first time I really made heavy use of the local adjustments brush. The image I was working on had white balance problems wherein one portion of the image needed a very cool white balance whereas the other portion needed a warm white balance. To fix this I applied the warm white balance all over using the WB adjustment tool, and then I painted in a blue cast using the adjustment brush over the parts of the image that were too yellow as a result of the WB adjustment, in order to bring the colors back to neutral. Could this be causing the problem? Switching back and forth between the two modules it looks like the only places where the previews differ is in the areas where I adjusted the color using the local adjustment brush.
Ruahrc
P.S. this is LR2.1 updated yeseterday. Source panoramic file was a TIFF in ProPhotoRGB color space stitched in Hugin.




