Lightroom CC 2015.1.1: Develop module doesn't detect external changes to original file

  • 17
  • Problem
  • Updated 3 years ago
  • Solved
  • (Edited)
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.
Photo of Nico Kaiser

Nico Kaiser

  • 24 Posts
  • 1 Reply Like
  • frustrated!

Posted 4 years ago

  • 17
Photo of Amy Johnson

Amy Johnson

  • 13 Posts
  • 2 Reply Likes
Same problem. For me the edited version flashes on the Develop module before going back to the unedited version. I can see the edited version on the Library module. This is super annoying because if I take the time to go into Photoshop I actually want to *see* my changes in Lightroom.

Lightroom version: CC 2015.1.1 [ 1032027 ]
Adobe Photoshop Version: 2015.0.1 20150722.r.168 2015/07/22:23:59:59 CL 1032107 x64
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 5596 Posts
  • 1184 Reply Likes
Are you both running Windows or Macs here?
Photo of Nico Kaiser

Nico Kaiser

  • 24 Posts
  • 1 Reply Like
like mentioned in the original post i'm on windows and tested this on different machines. Also i've seen this on Windows 8 and 10.
Photo of Steen Knarberg

Steen Knarberg

  • 22 Posts
  • 3 Reply Likes
Ihave the same problem on Windows 7. This is extremely annoying Adobe, do something and fast. This causes enorumous amonts of wasted time for a whole lot of you customers. Adobe ought to issue subscription discounts for bugs like this. Thanks Steen Knarberg
Photo of Amy Johnson

Amy Johnson

  • 13 Posts
  • 2 Reply Likes
Thanks so much for the quick reply Rikk. I am running Windows 7.
Photo of Amy Johnson

Amy Johnson

  • 13 Posts
  • 2 Reply Likes
I feel like this bug was introduced recently because I don't recall the problem before.
Photo of Nico Kaiser

Nico Kaiser

  • 24 Posts
  • 1 Reply Like
This bug was introduced with the june updates.
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 5596 Posts
  • 1184 Reply Likes
A question for you all.

If you invoke Edit in PS from Library Grid View, does the file update?
If you invoke Edit in PS from Develop module, does it fail?
Photo of Nico Kaiser

Nico Kaiser

  • 24 Posts
  • 1 Reply Like
it's more complicated. If i startup LR in library module mode and invoke "edit in PS" then the preview updates after edits in photoshop. If i then switch to develop module and save another change in PS the LR preview does NOT update in the develop module but DOES update in the library modul. So i have two different views on my file then. To solve this the only solution is to close and restart LR.

The bug only affects the develop module. The library view always updates.
Photo of Steen Knarberg

Steen Knarberg

  • 22 Posts
  • 3 Reply Likes
It doesn't matter from where I invoke. But what matters is how the file is created. If I create the psd with "edit in photoshop" everything is OK. But if the file, both psd and Tif, are created with export and at the same time added to the catalogue it fails.

But Adobe, I have spent countless hours on this and now acting as your bug investigation unit, but unpaid. Adobe has to compensate us for this economicly! How much do we have to put up with. I would expect Adobe to have its own staff of testers and investigators to make sure that what customers pay for are fully working software. This approach is not acceptable!

Thanks, Steen Knarberg
Photo of Amy Johnson

Amy Johnson

  • 13 Posts
  • 2 Reply Likes
That's a little harsh. It's hard to replicate a problem and you can't fix it until you can replicate it. I worked in QA/QC for software for a couple years and he's actually trying to fix the problem so I really appreciate it.

In playing around with it quickly, it may be the fact that the image has a rating. For instance I create the PSD file in Develop mode using "Edit in Photoshop" and it's all good whenever I edit it - I can see all the changes in Develop. But once I assign it a rating of 4, it stops showing me the Photoshop edits. I don't know if that's the problem but that's what I came up with on this end.
Photo of Steen Knarberg

Steen Knarberg

  • 22 Posts
  • 3 Reply Likes
I totally disagree with you Amy, we ate paying a fairly high amount for the use of Adobe's software, so it has to work. After all this is not beta software or free "use as is" And this is not a minor bug, this is essential key functionality. The tests I did last evening didn't involve rating, so this had no effects on my reproduction of the fault, which was easy to do. So either Adobe makes sure they can reproduce the fault in their lab with the number of PC's needed or they pay their customers to do the work for them and report back to them. The problem is not going away by it self.
Photo of Nico Kaiser

Nico Kaiser

  • 24 Posts
  • 1 Reply Like
I updated to 2015.2 and this bug is still not fixed...

this is a really annoying issue! I do this all the time and having to restart LR all the time just to refresh the preview really sucks!

Why isn't there a real issue tracker? Do Adobe devs even read here???
Photo of Steen Knarberg

Steen Knarberg

  • 22 Posts
  • 3 Reply Likes
I hope Rikk Flohr reads this and what a disapointment it wasn't fixed. What are they doing at Adobe?
Photo of Nico Kaiser

Nico Kaiser

  • 24 Posts
  • 1 Reply Like
removing all useful import options i guess :(
Photo of John R. Ellis

John R. Ellis, Champion

  • 4469 Posts
  • 1188 Reply Likes
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.
Photo of Jeffrey Tranberry

Jeffrey Tranberry, Sr. Product Manager, Digital Imaging

  • 15462 Posts
  • 2293 Reply Likes
Our QE have a repro case and the engineering team is investigating this issue. Thanks.
Photo of John R. Ellis

John R. Ellis, Champion

  • 4469 Posts
  • 1188 Reply Likes
Excellent, thanks for the update.
Photo of Nico Kaiser

Nico Kaiser

  • 24 Posts
  • 1 Reply Like
Great to hear that! This bugs me since june :(
Photo of Olli Malmivaara

Olli Malmivaara

  • 2 Posts
  • 0 Reply Likes
This reply was created from a merged topic originally titled LIGHTROOM External editor changes are not seen in development mode.

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.
Photo of John R. Ellis

John R. Ellis, Champion

  • 4469 Posts
  • 1188 Reply Likes
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.
Photo of Nico Kaiser

Nico Kaiser

  • 24 Posts
  • 1 Reply Like
@John R. Ellis: It's NOT fixed in LR CC 2015.2.1!

I just double checked and it's still there.
Photo of John R. Ellis

John R. Ellis, Champion

  • 4453 Posts
  • 1178 Reply Likes
It's fixed for Jao but not for you. That's most unfortunate.
Photo of Nico Kaiser

Nico Kaiser

  • 24 Posts
  • 1 Reply Like
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...
Photo of Nico Kaiser

Nico Kaiser

  • 24 Posts
  • 1 Reply Like
just for the records:

i have this problem on two windows machines. One workstation with windows 10 and a Dell XPS 15 laptop with windows 10. Both have gone through various lightroom updates in the past.

I don't see this bug on a Macbook Pro from late 2012 which has got a fresh Lightroom install some weeks ago.

All LR installs have been updated to the latest version.
Photo of Nico Kaiser

Nico Kaiser

  • 24 Posts
  • 1 Reply Like
and another update...

some users reported that there is a workaround like this: when the develop preview doesn't update then use the right arrow to switch to the next image and then back to your image. Unfortunately this doesn't work for me.

BUT: if i switch to let's say the 5th image right of my image and use the left arrow key 5 times to get back to my image then the preview updates. So instead of closing and re-opening LR just switch between images until LR "thinks" it needs to update the preview...
Photo of John R. Ellis

John R. Ellis, Champion

  • 4455 Posts
  • 1182 Reply Likes
I've noticed that if I open the image in Develop, I may have to wait 10 to 15 seconds sometimes for the updated image to appear. But it nearly always does if I just wait. (There's no "Loading" indicator or other indication it's computing.)

I think what might be going on in your case and in mine is that when you first display an image, LR kicks off a background thread to update the image, and you just have to wait for that to complete. Using the arrow keys to move to another image(s) and back isn't really affecting the outcome -- it's just something that we've been doing while waiting for the updated image to appear.
Photo of David Converse

David Converse

  • 683 Posts
  • 207 Reply Likes
Bridge has a similar problem of not showing changes to a file (in my case, replacing a JPEG with another created by Save for Web from a PSD) until the cache updates. I suspect that caching issues might be to blame. Unfortunately there is not a way in LR to delete a file's cache like there is in Bridge.
Photo of Gabriella Wetli

Gabriella Wetli

  • 3 Posts
  • 0 Reply Likes
This reply was created from a merged topic originally titled LightRoom CC develop module does not show edits done in PS CC.

Dear all
I have a proplem: lately the develop module in LR CC does not show the refreshed edits I have done in PS CC. If I switch to the library, it refreshes and I see the edits done in PS, if I switch back to the develop module I see only the old version of the file. This is very unnerving, as I cannot add edits in LR if I do not see the newest version of the image. Files coming back from PS are .tif 16 bit

I work with Windows 7 professional 64bit, LR and PS CC, newest versions, I have 24 GB RAM

Do you have an idea how I can solve this problem? If I close LR and reopen it, the newest image is shown in the develop module. But I really don't want to use that "workaround" all the time. It also is not a constant thing, sometimes LR refreshes the image in the develop module, but every so often, and very often, it doesn't.

below is one image of today. The library module shows the edits around the eyes, the develop module shows the old version with the bags around the eyes.

Many thanks and best regards
Gabriella

Photo of Carlos Oliveras

Carlos Oliveras

  • 130 Posts
  • 32 Reply Likes
This issue of saving in PS and not seeing the changes in LR has always existed at some level for me - it's one of those hundred things that for some reason, never get totally fixed in Lightroom. But it was relatively rare and at least, you could always force it to update by pressing left/right keys or switching between modules.

But since LR CC, far for being fixed for good, this issue has got critically worse - updating fails most of the time in the develop module and worse still, now there seems to be no workaround other than closing/restarting LR. Extremely annoying for anyone using the LR-PS-LR workflow. It's true that sometimes, if you wait, the image updates after some seconds. But for me, many times it won't update even after waiting for 1 minute (maybe it eventually updates but it takes extremely long).

I'm using LR 2015.2.1 on Windows 8.1. Please, fix this...
Photo of Steen Knarberg

Steen Knarberg

  • 22 Posts
  • 3 Reply Likes
I am so tired of this and have started the process of Switching to Capture one, which has much greater tools for grading, masking, sharpening, noise reduction etc. and most importantly works in every aspect and then it is like a race horse compared to Lightroom. In my view Lightroom has turned in to a catastrophy due for retirement.
Photo of addentro_nl

addentro_nl

  • 25 Posts
  • 13 Reply Likes
This reply was created from a merged topic originally titled Previews of PSD-Files not updated in Lightroom Devellop Module.

Hi there,

I've been searching without succes on Google moreover to find a solution for the following nasty problem:

In Lightroom CC2015 the devellop module shows the wrong preview file once a PSD-File is reopend from Lightroom to make further changes. The preview only updates in library module, but as soon as I get back to the develop module it jumps back to the elder version of the PSD-preview.

I tried to render new previews, but that didn't work. The only way to get the correct preview is deleting the file preview and reimport the file/synchronize the folder or just to close Lightroom and start again. Only then the correct preview is shown.

Does anyone hase this problem to and has a solution?

Thanks!
Photo of harperhaven

harperhaven

  • 2 Posts
  • 0 Reply Likes
This reply was created from a merged topic originally titled Spot removal edits from PS seen in Lightroom library but not Develop.

A photo is brought into LR but not edited. Then sent over to PS for spot removal (cuz it's so slow in LR) on the original photo. Saved as TIF. When return to LR, the edits are seen as expected in the Library. However, none of the PS edits are found in Develop. I have to sign out and back into LR in order for the edits to be seen in the Develop module.
Photo of John Mattson

John Mattson

  • 3 Posts
  • 0 Reply Likes
This reply was created from a merged topic originally titled .tif files not updating in the Develop module in latest update of Lightroom CC 20....

After the latest update to Lightroom CC 2015 6.1, once a .tif file is updated in photoshop, the image will not update in the develop module unless you restart Lightroom. It seems to work fine in the library module.