Skip to main content
nico.kaiser
Known Participant
August 19, 2015

P: Develop module doesn't detect external changes to original file

  • August 19, 2015
  • 53 replies
  • 2367 views

When i choose "edit original" in Photoshop then the LR develop module doesn't reload the image after i saved the tif in Photoshop. But the library module DOES refresh. So i end up with different previews in library and develop. Only solution is to restart LR. After the restart i can see the current preview in develop module too.

Steps to reproduce:
- Open your raw file (i use dng) in LR.
- Choose "edit in Adope Photoshop". Make some changes and save. Lightroom will automatically import the created tif file. Switch to develop module in LR
- Now make another change in PS and save.
- LR should detect that change to the tif file and refresh the preview. Maybe you need to switch to the next image and back to have LR refresh the image. But it should work.
- Now close LR and PS.
- Start LR again.
- Select the tif file again, switch to develop module and choose "edit original" in Photoshop.
- Make changes in PS and save.
- LR will not refresh the preview in the develop module! But it will refresh the library module. You will now see different versions of your file in develop and library until you restart LR.

tested with Lightroom: CC 2015.1.1 and PS CC 2015.0.1 on Windows on two different machines.

This is a real pain for me since i often switch between PS and LR!

This worked flawlessly before LR CC.

This topic has been closed for replies.

53 replies

nico.kaiser
Known Participant
October 14, 2015
I updated the other thread too. Maybe he just wasn't aware that the problem doesn't occur on the first "edit in PS" but only in combination with "edit original file" on subsequent edits...
johnrellis
Legend
October 14, 2015
It's fixed for Jao but not for you. That's most unfortunate.
nico.kaiser
Known Participant
October 14, 2015
@17404668. Ellis: It's NOT fixed in LR CC 2015.2.1!

I just double checked and it's still there.
johnrellis
Legend
October 14, 2015
Jao vdL reports this has been fixed in LR CC 2015.2.1 / 6.2.1: https://forums.adobe.com/message/8063.... Before you update, however, be wary that many people are still reporting serious issues with that version.
Inspiring
October 14, 2015


I edit a photo using external editor (DxO Filmpack 4). The edited photo is now in Lightroom but in development mode LR shows unedited (original) version. If I save between the original and edited version, they look the same. In full screen version the edited photo can be seen sometimes but sometimes is is the original. The edited version quickly flash but the the original is seen. In catalog view (G) one an see the edited version. I couldn't find any logic in this.

If I quit LR and come back the it works as it should.
johnrellis
Legend
October 9, 2015
Excellent, thanks for the update.
Legend
October 9, 2015
Our QE have a repro case and the engineering team is investigating this issue. Thanks.
johnrellis
Legend
October 9, 2015
Similar symptoms started happening to me using Export to invoke a Photoshop droplet on TIFFs and add the result to the catalog (which is what some third-party plugins do too). Both Library grid view and Develop initially show the unedited image.

A workaround for me is to open the suspect image in Develop, use the right-arrow to move to the next image, then left-arrow to come back. Usually the image updates after a second or two.

Details:

I'm on LR CC 2015.1.1 / OS X 10.10.5. I invoke an export preset on a TIFF with these settings:

- Export To: Same folder as original photo, Add To This Catalog, Add To Stack: Above Original
- Rename To: Custom Settings
- Image Format: TIFF, Compression: ZIP, Color Space: ProPhoto RGB, Bit Depth: 16.
- Include: All Metadata, Write Keywords As Lightroom Hierarchy
- After Export: Open In Other Application, a Photoshop droplet that applies an action and saves the file.
nico.kaiser
Known Participant
October 9, 2015
removing all useful import options i guess 😞
Known Participant
October 9, 2015
I hope Rikk Flohr reads this and what a disapointment it wasn't fixed. What are they doing at Adobe?