Participating Frequently

Question

P: Photos incorrectly considered as "changed" by republishing and smart collections

Forum|Forum|9 years ago
September 4, 2016
66 replies
3796 views

[Update from John R. Ellis:

At least some instances of this bug are caused by the new develop settings added by CC 2015.6 for the Guided Upright tool (2015.6 was released 6/8/2016). When 2015.6 or later first renders a photo at 1:1 zoom that had been imported by 2015.5 or earlier, it adds those develop settings before rendering. Then it compares those develop settings with the old, notices they are different, and incorrectly marks the photo to be republished.

Here's how to work around this instance of the problem: https://feedback.photoshop.com/photoshop_family/topics/modified-to-republish-problem?topic-reply-lis...

See here for a detailed recipe to reproduce the bug, along with an analysis of the problem and suggested fix: https://feedback.photoshop.com/photoshop_family/topics/modified-to-republish-problem?topic-reply-lis... ]
-----------------------------------------------------------------------------------------------------------------

Sometime photos in my published collections began to randomly mark themselves as modified to republish. Photos I haven't touched in years, in galleries I haven't recently changed, all of a sudden appear under 'Modified Photos to Re-Publish.' If I even scroll through a collection, dozens of the images begin to jump up to 'Modified Photos'. I can select the photos and send them back to 'Published' with 'Mark as Up-to-Date,' but then more immediately jump up to Modified.

macOS

Show previous replies

Califdan2

Inspiring

I'm having same problem. But, just to throw a wrench into this issue, For me it seems to have started when I started putting images into a dumb collections that are synced to LR Mobile. I DO NOT modify images on any mobile device, only on my desktop. But I do use LR Mobile on my smart phone to view images. Could the sync process to LR Mobile or the fact that I view synced images on a mobile device trigger the "modified to republish" in Publish Services that those images also appear in?

bramnani

Participant

Thanks for reporting the issue. We are looking into it.

M

magw77

Participant

Thank you soooo much! This seems to have fixed the issue for me. I've been putting up with it for months (I too was experiencing the issue when simply scrolling through grid view), but since following your nice clear instructions a couple of weeks ago, I haven't had any images mysteriously marked to republish. Such a relief!

johnrellis

Legend

Very much agreed.

S

Samoreen

Inspiring

Got it! Actually, it's a side effect of the bug reported here which is lasting since version 1 :

https://feedback.photoshop.com/photoshop_family/topics/wrong-timestamp-stored-in-lightroom-catalog-c...

I just remembered that I have been recently hit by this bug and I found myself with a lot of images for which the metadata status was wrong. So I used the write/read XMP method to fix the problem. Unfortunately, LR considers this as an editing operation although no setting has been actually changed.

Conclusion : bugs that are not timely handled are never fixed by themselves. They just generate more trouble with time. We have now version 6 and the time stamp bug is here since version 1. Time to do something.

--Patrick

johnrellis

Legend

"So I guess that something happened during the past week that caused a lot of images to be incorporated. This event probably spanned over several days, otherwise I wouldn't still have thousands of images in the collection."

I repeated the recipe I posted earlier for showing that the introduction of Guided Upright in CC 2015.6 caused photos to be marked for republishing spuriously: https://feedback.photoshop.com/photoshop_family/topics/modified-to-republish-problem?topic-reply-lis... In that situation, LR is adding new develop settings to the photo for Guided Upright whenever you first zoom in on the photo, fooling publish services into thinking the photo has changed.

But the "touchTime" and "touchCount" of these photos isn't changing when that happens. So I don't think Guided Upright / Zoom is the cause of spurious changes to Edit Date as viewed by smart collections.

johnrellis

Legend

I refreshed my understanding of SQLite's types. Columns are dynamically typed, and any type can be stored in any column. The type declarations of columns are hints ("affinities") about how values should preferably be stored. Adobe_images.touchTime is missing a type declaration:

CREATE TABLE Adobe_images (... touchTime NOT NULL DEFAULT 0)

so according to the documentation it should have type NUMERIC, where values are stored as integer or real if possible.

DB Browser for SQLite 3.9.1 is buggy and by default stores values in "touchTime" as text rather than numeric values. According to the documentation, that shouldn't matter because the text value will be converted to numeric in expressions that require numeric values. But likely there's some subtlety here that causes LR to treat text values in "touchTime" representing numbers differently than numeric values.

Most likely, SQLite Expert Personal 4 is doing something similar, storing the values you enter for "touchTime" as texts rather than numbers.

So I think any further experiments need to be done with "sqlite3".

S

Samoreen

Inspiring

Hi John,

I did all the data manipulations described above with SQLite Expert Personal 4. So, it may have yet another behavior when manipulating the touchTime field. If I look at the Design tab for the Adobe_images table in SQLite Expert, the touchTime field has no specified type. So I guess it's a string.

Anyway, this morning, my "Last 7 days edited images" collection has much less images in it. So I guess that something happened during the past week that caused a lot of images to be incorporated. This event probably spanned over several days, otherwise I wouldn't still have thousands of images in the collection.

--Patrick

johnrellis

Legend

My curiosity got the better of me and did some tests. After first, I observed the same thing you did -- changing "touchTime" of a photo didn't change the contents of an "Edited Today" smart collection.

I was making the change to "touchTime" using Database Browser For SQLite (Mac, 3.3.1). But when I started making the change with "sqlite3", it worked exactly as expected, with the value of "touchTime" corresponding exactly to "Edit Date" in smart collections.

Then I noticed that when I changed "touchTime" with Database Browser and then dumped the database with sqlite3's .dump command, the value would be quoted, e.g.

'509059250.086592'

But when I changed "touchTime" with "sqlite3" and dumped the database with .dump, the value was not quoted, e.g.

509059250.086592

My understanding was that SQLite represented everything internally as strings, so I'm confused as to what's happening with Database Browser. But using "sqlite3" confirms that "touchTime" really is "Edit Date" in smart collections and "lastEditTime" in the SDK API.

johnrellis

Legend

Mysterious. "touchTime" maps to "lastEditTime" in the API but not "Edit Date" in smart collections. We're clearly missing something.

Show more replies

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded