Develop module preview differs from Library + Exported JPGs

but they might exhibit differences in rendered results, especially under heavy/extreme adjustments.

@SimonChen Hi Simon, I have same issue currently with my Sony A9 files I did color corrected more than 300 images and there are are around 80 that are underexposed when exported, is there a way I can’t lost all the work done in those files, is this issue exclusively from Sony A9 files. 

Are you using Smart Previews with the original files offline (i.e. external drive disconnected), or with Edit> Preferences> Performance 'Use Smart Previews Instead of Originals for image editing' checked? If so try the export with the original files connected AND the above Preferences setting unchecked.

Thanks much Todd, i did it but with no results will try again creating a new catalog and importing files as original. I do have the files on a connected external drive. 

after importing the originals still having the issue when exporting... https://www.loom.com/share/d5c39fcbad4540b0862f23109b3d22f2

What does the export JPEG file look like when viewed inside LrC?

Hi Todd, thanks much after importing the files in a new catalog using the preferences you suggested they look OK in Library underexposed in Develop after exported they turn out underexposed , if I bump up the exposure in Develop and then export from there the jpg looks fine but in the library, they look overexposed. 

In LrC Edit> Preferences> Performance tab set 'Use Graphics Processor' to Off, close LrC and then restart it to load the setting change. Is there still a difference in exposure between the Library and Develop module's?

Yes, i did it (it was off), then restart Lr again and same difference https://www.loom.com/share/df17cf91b2ed4045bd38231b9ab024eb

Do you calibrate your display with A Spyder or other hardware device? You may have an incompatible display profile. Follow the procedure at the below link to check it.

https://www.lightroomqueen.com/how-do-i-change-my-monitor-profile-to-check-whether-its-corrupted/

Thank you i have done that set to D65 and still have the issue with library and develop 

Please export one of the files with the issue using your applied Develop settings. Upload the DNG to a file sharing site and I'll check it on my system for issues.

Hi Todd, thanks much for your help! here the link to the picture in different formats https://www.dropbox.com/sh/p6zcg4omqsr2i2y/AAAW2nWg2A_sE4F01sf7I3uKa?dl=0

I can confirm what you are seeing with both the DNG and ARW file with XMP settings. However, after building 1:1 Previews the ARW, DNG, and JPEG files look identical in both the Library and Develop modules. Not sure why since the Standard Preview should automatically get updated after applying settings in the Develop module. Try building 1:1 Previews using Library> Previews> Build 1:1 Previews.

I'm going to examine your settings further to see if one of them is causing the issue.

I could not find a specific Develop setting that is causing this issue. Forcing rebuild of previews by clicking on the image to Zoom in or using Library> Previews> Build 1:1 Previews fixes it. Why this is necessary is a mystery, but at leats you have a an easy workaround.

Hi Todd, thanks much I did that and there is still a little bit of automatic exposure adjustment in the develop module https://www.loom.com/share/691b47735c6444fca10d5c31bfadcf7a   will let you know how ends during export. thanks again

The Develop module builds its previews real-time using the camera raw cache data. Normally you don't notice it, but for some reason with this type of image file it's visible as in your video. The _RPS4813.arw file is about 2-3 EV underexposed, which seems to be causing the issue, but it shouldn't! Others in this post were seeing this issue only when using Smart Previews. You (and I) aren't using Smart Previews so it remains a mystery. Building 1:1 Previews should fix the issue so that the Develop, Library, and export files are all identical.

I forgot to add that the Highlights setting is what causes the difference. If you set it to 0 then no flashing or difference between Develop and Library previews. Apparently the Highlights setting is not being applied in the Library module unless 1:1 Previews are built. It appears if you build 1:1 Previews after the initial editing in the Develop module the issue does not reappear when making further edits. Like I said it's a mystery that Adobe needs to solve.

It's disappointing that I can't enjoy the increased performance of using Smart Previews but I'll gladly take that compromise if it means knowing my edits are accurate.