Alexander's profile

137 Messages

 • 

2.1K Points

Wed, Oct 21, 2020 11:00 PM

Closed

In progress

Lightroom Classic 10 marks photos as Modified to Re-Publish after just viewing them

Hello.

LrC 10 marks photos in Publish Collections as "Modified Photos to Re-Publish" when I just view them in the Library DEVELOP module.

As far as I can see, this happens for photos that do not have a current 1:1 preview rendered. When I click on them and - maybe also - zoom in, LR renders a new preview, and that seems to trigger it. please see update below

Needless to say, this can easily be resolved by using "Mark as Up-To-Date" - unless I have a photo that actually has changed that aren't published yet. Also, I have quite a few Publish Collections (I haven't counted but it's easily over 100) and it's quite a nuisance to chase after LR and clean up this mess.

Latest Mac OS Catalina, LrC 10.

137 Messages

 • 

2.1K Points

1 y ago

PS: the suggested solution from two years ago (uncheck "Remove person information" in the publish service's "Metadata" group) does NOT work for me.

7 Messages

 • 

140 Points

1 y ago

I have the same problem. Only solution I have is to open each publish collection, then wait until it has marked all photos as modified, and then mark them as up-to-date.

Bug?

137 Messages

 • 

2.1K Points

@casper_pedersen_7749526 thanks for the confirmation! A friend of mine also confirmed this, on his Mac. Are you on a Mac or Windows?

And it surely is a bug - and a zombie of a bug too! If you look at the "Related Conversations" in the sidebar here in the forum, you'll find that it had occurred previously and was supposedly fixed in LR 6 (!).

I haven't played through all scenarios because I reverted to version 9.2.1 (again...) but a potential problem that I see is this:

What if the newly generated preview that triggered the "Modified" status ages, and is eventually purged? The only way to avoid that would be to set the Previews to never expire.

That in turn would mean an extremely large Preview Cache.

7 Messages

 • 

140 Points

I'm using MacOS (Macmini 2020, i7, 32GB mem). Regenerating preview does help, but it's not a solution.

In general LR10 is slow, not only in the Library browsing.

I'm going back to LR9.2 also, as this is no fun.

137 Messages

 • 

2.1K Points

1 y ago

Thinking that it was the (missing 1:1) Previews that causes this, I investigated a little more.

I rendered 1:1 Previews in LrC v9.2.1 (I skipped 9.3 and 9.4 because of the clone/heal bug), then updated to LrC v10.

After some tests, a correction to what I first wrote, above: it's viewing a photo in the DEVELOP module (just browsing/viewing) in v10 that triggers the "Modified to Re-Publish" signal, somehow. Zooming in is not necessary.

I suspect it is the additional Split Toning options (now called Color Grading) that are added to existing photos which mark a photo as Modified, but it happens even for photos where Split Toning isn't used.

It would be REALLY useful to get this fixed @Rikk  - I have ~3000 photos in Publish Collections and I rely on Lightroom to ACCURATELY tell me when something DOES need updating, online. I don't see myself browsing through 3000 photos in 150+ Publish Collections to trigger this, and then use "Mark as Up-To-Date".

Thanks.

(edited)

137 Messages

 • 

2.1K Points

1 y ago

Browsing the forums, I came upon this thread today, which might explain why all photos in a Publish Collection get marked as changed:

Lightroom Classic: Pointless metadata updates on upgrading to v10

(edited)

137 Messages

 • 

2.1K Points

1 y ago

This is not fixed in version 10.1 from December 2020.

45 Messages

 • 

716 Points

1 y ago

I'm having the same issue. I can go into a published collection and watch the photos move into the modified section without doing anything to them. It happens constantly now where photos are marked as modified with no changes at all. Even right after publishing them all they will start to be moved into modified.  I really hope someone can look into this. 

137 Messages

 • 

2.1K Points

The only workaround is to open every photo in the Develop module, at least once (like moving through all of them using the filmstrip, or the left/right cursor keys). That marked most of the photos as "modified" for me and once I used "Mark as up-to-date" it doesn't happen again for me, thankfully.

45 Messages

 • 

716 Points

I've already gone through all photos in Develop that are in any published collection. Unless you mean after adding them to a published collection I again need to go through each picture in develop.  That's not going to happen, I have to publish 1000 or more pictures sometimes for clients, I basically just ignore that it says pictures need to be republished for the most part. 

5 Messages

 • 

90 Points

1 y ago

Lightroom Classic 10.1 - Publish Services:  Photos which haven't been modified in any way are suddenly marked as modified to be re-published. The only workaround seems to be to wait for LR to mark all the photographs as requiring re-publishing and then mark them as up to date to avoid them being re-exported and 'seen' as updated files in the destination location.  When you have multiple sets of published folders containing many thousands of images this is extremely time-consuming to say the least and not what you expect from expensive software in a professional environment.

This bug has occurred in previous updates of Lightroom (Classic) and needs resolution please.  There are numerous reports from other users in forums relating to this bug.

Note: This comment was created from a merged conversation originally titled Lightroom Classic: Publish Folders - photos erroneously marked to re-publish in v10.1

537 Messages

 • 

12.8K Points

Yes.  A problem worth the effort to get fixed.  

While you're at it, would also like to see a "Publish All" capability where we could trigger multiple "re-publish" operations at once.  For example:

  1. All PS collections that contain selected images.  (select image or images in film strip, right click, and pick "Publish all selected"
  2. Be able to click on a Publish service and republish all PS collection within that PS
  3. Be able to multi select several PS collections and re-publish them all with one click

Adobe Administrator

 • 

563 Messages

 • 

10.2K Points

Could you please let us know which publishing service are you using?
Is it Hard Drive publish?

Thanks,
Sunil

5 Messages

 • 

90 Points

Yes it's a Hard Drive publish service which creates sets of downsized JPEGs for use in other library settings and for manual upload to other services.

MacBook Pro 2017, MacOS BigSur 11.0.1, Adobe Photoshop Lightroom Classic 10.1

Thanks,  Barry

Adobe Administrator

 • 

10.9K Messages

 • 

143.5K Points

This thread is being merged into an authoritative thread for better tracking and response. 

Adobe Photography Products

Quality Engineering - Customer Advocacy

137 Messages

 • 

2.1K Points

@sunil_bhaskaran for what it's worth, I'm using a Hard Drive publish service, Flickr, and to my own website (using WP/LR Sync). All show the same behavior.

537 Messages

 • 

12.8K Points

1 y ago

Problem exists in all my PS's.  these include several Hard Disk ones as well as ones from 3rd party Plugin developers.   I don't know, but this may be related to the problem that tens of thousands of photos magically show a metadata mismatch between LrC and the image files on disk (XMP Data) when there has been zero chance that a 3rd party application has changed the XMP data on disk.  In both cases, it seems that "dirty bit" gets set when it shouldn't (a dirty bit is used in programming to indicate "something has changed" and is often used to trigger the "unsaved changes" warning when closing a file)

137 Messages

 • 

2.1K Points

@dan_hartford I'm just guessing here, but the metadata "version" must have changed, to include the Split Toning -> Color Grading update. Since C.G. is compatible with the old S.T. this "dirty bit" should probably not be set.

38 Messages

 • 

508 Points

I'm also experiencing this.. I'm needing to use the ImageRights publish service plugin. I've been trying to use a feature for almost a week, but I can't because it keeps marking images that I've not touched since they were originally added to the collection as 'modified'.  


https://www.junction10.photography

38 Messages

 • 

508 Points

1 y ago

Related to: https://feedback.photoshop.com/conversations/lightroom-classic/lightroom-classic-new-photos-to-publish-photos-are-already-published-in-collection/601a7fd71dbf513517cb58a1

This is a potentially serious bug..

I'm having a really hard time trying to work on a set of images because they randomly keep being marked as 'Modified to republish', but what I've just noticed is this:

I selected three images in the library grid view.. the grid view keeps changing due to certain images in the collection being moved into the Modified Photos pane, without reason.

However, this then changes the sequence of the images in the grid view, but the selection doesn't move along with the originally selected images!
eg: If you have 4 images, and highlight image 2.. Image 1 gets moved to Modified Images pane and disappears from the 'Published photos' pane. So now image 2 is in the place of image 1, image 3 becomes 2, and image 4 becomes 3..  but the selection remains in the 2nd slot - but instead of image 2 still being highlighted, you end up with image 3 highlighted..  this could have serious consequences to your library if the selection changes while you're either editing metadata or choosing images to delete!

I've made a screen recording of it happening in real time..  this is not edited, and I am not clicking anything or touching the keyboard. See how the images shift every so often, but the selection stays in the same slot, choosing different images!


Screen Recording of 'selection' bug. 

Note: This comment was created from a merged conversation originally titled Lightroom Classic: selection in library grid changes due to Modified Photo flag

Champion

 • 

1K Messages

 • 

15.9K Points

Are you using a network drive or attached drive?

38 Messages

 • 

508 Points

@robert_somrak I’m using a Drobo, desktop attached storage rather than NAS. Have been for years though.

https://www.junction10.photography

990 Messages

 • 

14.9K Points

Dommage, les iMac 21.5'' ne permettent pas l'ajout de RAM par l'utilisateur car il n'y a pas de trappe à l'arrière prévue pour cela, alors que les iMac 27'' en ont une et donc l'utilisateur pourra acheter de la RAM compatible beaucoup moins cher que chez Apple et surtout pourra l'installer en 5 minutes !

Attention, LrC nécessite beaucoup d'espace libre sur le disque contenant le catalogue, alors un disque externe SSD thunderbolt pourra aussi améliorer les performances si celui-ci conserve suffisamment d'espace libre pour les fichiers temporaires.

Damage, iMac 21.5 " does not allow the addition of RAM by the user because there is not hatch in the back envisaged as it, while iMac 27 " have one of it and therefore the user will be able to buy of compatible RAM very cheaper that to Apple and especially will be able to install it in 5 minutes!

Attention, LrC requires free space on the disc a lot containing the catalogue, then an external disc SSD thunderbolt will also be able to ameliorate performances if this one keeps enough free space for the temporary files.

Champion

 • 

1K Messages

 • 

15.9K Points

Your description sounds like you are working in a Publish Service.  The video doesn't make it very clear about that or what you are doing during the long pauses when the cursor isn't moving but if you are making ANY change to the image (metadata, edits, etc) than the images will move to the Modified section and the selection in Published will move.  

38 Messages

 • 

508 Points

My iMac 27” has 64gb RAM, the catalogue is on the internal SSD and there’s over 400gb free, the image files are on the external drive, connected by Thunderbolt 3...

https://www.junction10.photography

137 Messages

 • 

2.1K Points

5 m ago

This problem persists in LrC v10.4 and I don't think it has been mentioned before, but I'm seeing a connection to the Catalog Setting "Automatically write changes into XMP".

In the past I always had this setting ON but deactivated it a few weeks ago for testing purposes. The photos that were marked as "Modified" I could trace back to changes that I made.

Two days ago, I turned "Automatically write changes into XMP" back on, and LrC began to write the XMP files/data in the background, instantly. And with that, a TON of photos in my Publish Collections showed up as "Modified" again.

If nothing that I did to those photos triggered the Publish Collection, then the write operation to XMP probably shouldn't, either...