David MMMM wrote:

 

Not sure what you mean by optimizing the catalog.

Go to edit, catalog settings, relaunch and optimise

I have the same problem.  While editing images, the image keeps reloading time and time again, interrupting my editing and in some cases, causing a loss of adjustments made prior to the "reload".  I read about this problem here, and also, in other forums.  I think I have found a fix/work-around, although I don't really like it.  If you turn off the option to automatically write changes into XMP in the catalog settings, the problem seems to disappear.

I wish someone at Adobe could report this as a problem, and try to fix it prior to the next maintenance release (I'm using LR 3 by the way).

Kenny in NJ

Same problem since upgrading from Lightroom 2.X to 3.3

I edit a lot of photos externally in PTLensEdit, then when developing the photo it keeps reloading the photo on every adjustment as described above.

ONLY happens on externally edited photos.  Very annoying.

My current workaround is to make a virtual copy of the edited photo, and develop that.

The virtual copy does not suffer from the continual reloading problem.

Disabling sidecar XMP is not a reason, it's a workaround for a LR3 bug.

Anyway I'm editing JPG files not RAW - there are no XMP files being generated.

Restarting LR fixes the reload problem, however I have 300+ photos to edit by Friday so doing that after every edit is just too slow.  My workaround of using virtual copies of edited photos is the best workaround for me, for now.

Here we are, 6 months since the last post and 2 years since the first, now at Lightroom version 3.4.1, and this problem still exists.  The edit function that bothers me the most with this is cropping.  It is very annoying and frustrating to have the image expand, contract and jump around for 2 or 3 seconds while reloading everytime I make an adjustment to the crop rectangle.  Yes, the couple of workarounds, using virtual copies and not writing to XMP files, work, but are not acceptable for long term use.  It seems to me that not writing to XMP files defeats the purpose of having a non-destructive editor if you can't save the changes as you go.  I hope Adobe eventually fixes this, but maybe they are leaving it until LR 4 is available, if they are even paying attention to this forum.

No, not fixed in 4.2RC...........just checked.

Turning off "automatically write to xmp" does not always help. Here that did nothing.

The problem is the tiff file that LR writes when using an external editor or when ACR is not up to date with LR.

If Photoshop writes the tiff coming back to LR, there is no problem in LR, no blinkies, no "Loading".

The problem only occurs when LR writes the tiff file. I have not tried it with PSD.

I haven't tried creating a VC to work on, I just close and reopen the program......voila...no more blinkies.

I have posted this twice in bug reports, the first time back in 3.x something. This started about 3.0.

And for the record, I also think this bug is long overdue. It seems to have the lifespan of a cockroach.

Rich

Back on Sep. 20th, I had reported that this problem seemed to have gone away, but R Owens came back and said it had not.  I now realize R Owens is correct; I think I had not been working with the files in the way that produces the problem, or else the problem now manifests it self in a more limited way.  I just ran a couple of tests that illustrates the issue clearly.  This is while running Lightroom 4.2 with Camera RAW 7.2 and Photoshop CS5 version 12.0.4 with Camera RAW version 6.7.0.339.

If I open a .CR2 file in Photoshop, I am asked whether to Render Using Lightroom or Open Anyway.  If I render with LR, the resulting TIF file will reload each time I manipulate it in the LR Develop module.  For example, using the crop tool, each time I resize the crop rectangle, or move the image within the rectangle, the file reloads, which takes a couple of seconds and is very annoying, as well as time consuming when it happens 7 or 8 times.  However, if I choose "Open Anyway," the resulting TIF file does not display this behavior.   Evidently this does has something to do with the incompatibilty between ACR versions in Lightroom and Photoshop.  Turning off Automatically write changes to xmp also stops this from happening, at least for me.  I also found that TIF files generated by exporting directly to TIF from Lightroom do not have this problem. 

So it's relatively easy to bypass this problem by converting to TIF first, or open in Photoshop without using Lightroom's current Camera RAW version, but is still something that shouldn't happen anyway.