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

Forum|Forum|9 years ago
September 4, 2016
66 replies
3803 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

dj_paige

Legend

Last night, I came home from work, edited 3 photos, and then tried to create a smart collection where the criteria was "Edit Date" is Today. Much to my surprise, 91 photos were in the smart collection. Now I suppose it is remotely possible that I accidentally selected and edited these 91 non-contiguous files, but I consider this extremely unlikely. Also, it is remotely possible that Auto Sync was on when I edited these three photos, but that would show up in the history of all of these 91 photos, and there is nothing in history to indicate Auto Sync was on, or that new edits had happened since these were published via a Publish Service that left it's date-time stamp in the history.

This morning, I woke up, launched Lightroom, and created the smart collection anew. Since I had not used Lightroom overnight (I was sleeping), and Lightroom was closed overnight, I assumed that the smart collection with criterion "Edit Date" is Today would produce zero photos (as no photos had been edited Today, a few had been edited yesterday). The same 91 photos appeared in the Smart Collection.

Possible causes:

Bug in Lightroom
I was sleepwalking overnight and re-edited the same 91 photos, but don't remember doing it
Space aliens

I think it's a bug.

robertd87722903

Participant

I have experienced this for several months now. I can reproduce the error at will.

If I browse my Flickr-collection, triggering preview-building, it WILL randomly kick photos into modified-to-re-publish. My collection contains nearly 3185 photos since 2007, therefore most of have had previews aged out. More to the point, I recently zapped all my previews (70Gb) due to disk swap. The random re-publish flagging then kicked into over-drive.

It only happens if I browse the Flickr collection (all markeed as up-to-date) in grid view. No selection necessary, just scrolling into a region of non-preview material will do the trick. Every thumbnail render does not trigger the flagging, only some. That is to say, it is not because previews do not exist, it is because they don't exist AND a sprinkling of voodoo.

Update: If I select all Flickr collection photos, then generate previews, the behavior occurs. For as long as preview build job takes to complete, i.e. in the background and without user interaction.

In summary
- When previews are rendered...
- ...and some unknown condition is met (only some, not all, photos)...
- ... metadata change occurs, sufficient to nudge the SmartCollection logic

Auto-XMP is disabled. Catalog is consistency-checked on a regular basis.

Regards,
Robert

Lightroom version: CC 2015.6.1 [ 1083169 ]
License: Creative Cloud
Operating system: Mac OS 10
Version: 10.11 [6]
Application architecture: x64
Logical processor count: 8
Processor speed: 2.5 GHz
Built-in memory: 16,384.0 MB
Real memory available to Lightroom: 16,384.0 MB
Real memory used by Lightroom: 466.7 MB (2.8%)
Virtual memory used by Lightroom: 7,833.8 MB
Memory cache size: 3,767.8 MB
Maximum thread count used by Camera Raw: 8
Camera Raw SIMD optimization: SSE2,AVX,AVX2
Displays: 1) 2880x1800, 2) 1680x1050

Graphics Processor Info:
AMD Radeon R9 M370X OpenGL Engine

Check OpenGL support: Passed
Vendor: ATI Technologies Inc.
Version: 4.1 ATI-1.42.15
Renderer: AMD Radeon R9 M370X OpenGL Engine
LanguageVersion: 4.10

Application folder: /Applications/Adobe Lightroom
Library Path: /Users/xy/Pictures/Cat2010_LR6.lrcat
Settings Folder: /Users/xy/Library/Application Support/Adobe/Lightroom

Installed Plugins:
1) Aperture/iPhoto Importer Plug-in
2) Canon Tether Plugin
3) DxO OpticsPro 10
4) DxO OpticsPro 10 Importer
5) Facebook
6) Flickr
7) HDR Efex Pro 2
😎 Leica Tether Plugin
9) Nikon Tether Plugin

Config.lua flags: None

AudioDeviceIOBlockSize: 512
AudioDeviceName: Built-in Output
AudioDeviceNumberOfChannels: 2
AudioDeviceSampleRate: 44100
Build: LR5x102
CoreImage: true
GL_ACCUM_ALPHA_BITS: 0
GL_ACCUM_BLUE_BITS: 0
GL_ACCUM_GREEN_BITS: 0
GL_ACCUM_RED_BITS: 0
GL_ALPHA_BITS: 8
GL_BLUE_BITS: 8
GL_DEPTH_BITS: 24
GL_GREEN_BITS: 8
GL_MAX_3D_TEXTURE_SIZE: 16384
GL_MAX_TEXTURE_SIZE: 16384
GL_MAX_TEXTURE_UNITS: 8
GL_MAX_VIEWPORT_DIMS: 16384,16384
GL_RED_BITS: 8
GL_RENDERER: AMD Radeon R9 M370X OpenGL Engine
GL_SHADING_LANGUAGE_VERSION: 1.20
GL_STENCIL_BITS: 8
GL_VENDOR: ATI Technologies Inc.
GL_VERSION: 2.1 ATI-1.42.15
OGLEnabled: true
GL_EXTENSIONS: GL_ARB_color_buffer_float GL_ARB_depth_buffer_float GL_ARB_depth_clamp GL_ARB_depth_texture GL_ARB_draw_buffers GL_ARB_draw_elements_base_vertex GL_ARB_draw_instanced GL_ARB_fragment_program GL_ARB_fragment_program_shadow GL_ARB_fragment_shader GL_ARB_framebuffer_object GL_ARB_framebuffer_sRGB GL_ARB_half_float_pixel GL_ARB_half_float_vertex GL_ARB_imaging GL_ARB_instanced_arrays GL_ARB_multisample GL_ARB_multitexture GL_ARB_occlusion_query GL_ARB_pixel_buffer_object GL_ARB_point_parameters GL_ARB_point_sprite GL_ARB_provoking_vertex GL_ARB_seamless_cube_map GL_ARB_shader_objects GL_ARB_shader_texture_lod GL_ARB_shading_language_100 GL_ARB_shadow GL_ARB_shadow_ambient GL_ARB_sync GL_ARB_texture_border_clamp GL_ARB_texture_compression GL_ARB_texture_compression_rgtc GL_ARB_texture_cube_map GL_ARB_texture_env_add GL_ARB_texture_env_combine GL_ARB_texture_env_crossbar GL_ARB_texture_env_dot3 GL_ARB_texture_float GL_ARB_texture_mirrored_repeat GL_ARB_texture_non_power_of_two GL_ARB_texture_rectangle GL_ARB_texture_rg GL_ARB_transpose_matrix GL_ARB_vertex_array_bgra GL_ARB_vertex_blend GL_ARB_vertex_buffer_object GL_ARB_vertex_program GL_ARB_vertex_shader GL_ARB_window_pos GL_EXT_abgr GL_EXT_bgra GL_EXT_bindable_uniform GL_EXT_blend_color GL_EXT_blend_equation_separate GL_EXT_blend_func_separate GL_EXT_blend_minmax GL_EXT_blend_subtract GL_EXT_clip_volume_hint GL_EXT_debug_label GL_EXT_debug_marker GL_EXT_depth_bounds_test GL_EXT_draw_buffers2 GL_EXT_draw_range_elements GL_EXT_fog_coord GL_EXT_framebuffer_blit GL_EXT_framebuffer_multisample GL_EXT_framebuffer_object GL_EXT_framebuffer_sRGB GL_EXT_geometry_shader4 GL_EXT_gpu_program_parameters GL_EXT_gpu_shader4 GL_EXT_multi_draw_arrays GL_EXT_packed_depth_stencil GL_EXT_packed_float GL_EXT_provoking_vertex GL_EXT_rescale_normal GL_EXT_secondary_color GL_EXT_separate_specular_color GL_EXT_shadow_funcs GL_EXT_stencil_two_side GL_EXT_stencil_wrap GL_EXT_texture_array GL_EXT_texture_compression_dxt1 GL_EXT_texture_compression_s3tc GL_EXT_texture_env_add GL_EXT_texture_filter_anisotropic GL_EXT_texture_integer GL_EXT_texture_lod_bias GL_EXT_texture_mirror_clamp GL_EXT_texture_rectangle GL_EXT_texture_shared_exponent GL_EXT_texture_sRGB GL_EXT_texture_sRGB_decode GL_EXT_timer_query GL_EXT_transform_feedback GL_EXT_vertex_array_bgra GL_APPLE_aux_depth_stencil GL_APPLE_client_storage GL_APPLE_element_array GL_APPLE_fence GL_APPLE_float_pixels GL_APPLE_flush_buffer_range GL_APPLE_flush_render GL_APPLE_object_purgeable GL_APPLE_packed_pixels GL_APPLE_pixel_buffer GL_APPLE_rgb_422 GL_APPLE_row_bytes GL_APPLE_specular_vector GL_APPLE_texture_range GL_APPLE_transform_hint GL_APPLE_vertex_array_object GL_APPLE_vertex_array_range GL_APPLE_vertex_point_size GL_APPLE_vertex_program_evaluators GL_APPLE_ycbcr_422 GL_ATI_blend_equation_separate GL_ATI_blend_weighted_minmax GL_ATI_separate_stencil GL_ATI_texture_compression_3dc GL_ATI_texture_env_combine3 GL_ATI_texture_float GL_ATI_texture_mirror_once GL_IBM_rasterpos_clip GL_NV_blend_square GL_NV_conditional_render GL_NV_depth_clamp GL_NV_fog_distance GL_NV_light_max_exponent GL_NV_texgen_reflection GL_NV_texture_barrier GL_SGI_color_matrix GL_SGIS_generate_mipmap GL_SGIS_texture_edge_clamp GL_SGIS_texture_lod

Steven Settlemyre

Participant

I am also having this issue. I created a series of new Smart Collections that simply write out JPEGs to folders on my hard drive. I "Publish" the Smart Collection using the Publish button, and randomly, after a photo is really published, it immediately appears in the "Modified Photos to Re-Publish" section. This is a huge inconvenience and an unacceptable bug that will kill many peoples' workflow.

Adobe Lightroom CC - 2015.6.1 build 1083169
Macbook Pro - Mac OSX El Capitan 10.11.6

FeedbackCommunityMember

Inspiring

I'm having the same problem-

I'll go to a publish collection and while I'm looking at the published photos, they will suddenly appear as Modified Photos to Republish without any input from me. This can happen one at a time or all at once. I can mark them as Up to Date and clear them from republish status and then more will appear as Modified Photos to Republish!

FeedbackCommunityMember

Inspiring

This is at least the third post on this topic in the last couple of months. It clearly started with the 6.6.1 update. I'm only publishing to my HDD and pretty sure my hard drive / OS is not updating image metadata. Does anyone from Adobe read these forums?

Califdan2

Inspiring

Yeah! It's not obvious what LR decides is a "Change". Obviously things like star ratings, titles, captions, exportable keywords or anything you do in the develop module cause it to go to Modified, but other more subtle activities can also do it. I don't know what else causes it to "jump" as you say, but it could be something as mundane as just opening the image in the Develop module or syncing with a mobile device or even publishing in an entirely different publish service. I'm not saying that I know any of these 'changes' cause it to jump, but something does and it's not always clear what it was. You may want to check what other plugin's you have active as sometimes work they do in the background could trigger LR to mark the image as having been changed. One thing the gets me a lot is if I move a KW from one parent to another or fix a spelling error on a KW or any of its parents, or add/remove a synonym.

I've also seen situations where the act of publishing an images caused it to be marked as changed and have it pop right back to modified. I think the issue here was the inability to turn off the cross transfer of comments. So you have an image and publish it which sends it to the service. Then LR asks the service for comments and the service replies with "none" or returns a new comment which in turn marks the image as modified when the comment is added to the metadata. Circular logic.

It doesn't 100% solve the problem, but some 3rd party Publish Service plugin's, such as those from jfriedl, have a panel in Publish Service set up where you can check off the things you want to be considered a "Change" or un-check them so they won't be considered a change. For example in his Facebook Publish Service plug-in you can check or un-check any of: caption, copyright, creator info, GPS location, instructions, job identifier, exportable Keywords, label, provider, rating, source, title, image date. when I switched from LR's Facebook plug in to JFriedl's and unchecked all but caption, Keywords and Title it reduced the problem you describe by over 90%.

Dan

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