richardadams_3584895's profile

47 Messages

 • 

694 Points

Mon, Jun 7, 2021 11:46 PM

Closed

In progress

Lightroom Classic Book Module problems

Hello 

Someone was kind enough to alert me that the Adobe Support Community was not the place to post issues and concerns with Photoshop Lightroom Classic v 10.2. They suggested that if I wanted to let Adobe engineers know about issues with the software, I need to post here, so here I go...

Issue #1

I'm making a book in LrC 10.2 on a Mac Pro 10.15.7 (Catalina).

Some of the custom pages include a photo description cell and the filename is automatically included. When I highlight the cell and press delete, all is well, it deletes. However the next time I open LrC and go to the book module to continue working, the deleted photo description cell reappears. I am forced to go through the entire book and delete the photo descriptions all over again.

Issue #2

I am experiencing issues wherein the book module fails to refresh when I drag a new image into a photo cell. What happens is the cell or the page goes white and changing pages or zoom does not force a view reset. The view will refresh if I quit and restart.

 

In this screenshot, I dragged an image to the top, small, image cell on the right page, and all three cells when blank and unable to refresh.

Here is how the page looks after a quit and restart of LrC.

I took a break from making my book. I wanted to have a week away so that I could look at it with fresh eyes. When I came back to look at the multi-page view, most of my images were gone! I sunk into despair, there was so much work placed into this book creation and layout. Where did all my work go?

Well, after my heart attack, I resolved to start making my book all over again. Once I zoomed into the two-page view, low and behold, all my images were still there! So Adobe, thank you for the emotional roller coaster. Is there any way of improving the process by which the book module can consistently preview images and display work in progress properly? I would really appreciate it if the book module could get a little love.

Thank you very much and have a great day.

Also, I was told to include the first ten lines from my LrC system info, so here they are;

Lightroom Classic version: 10.2 [ 202103041821-226a1211 ]
License: Creative Cloud
Language setting: en-CA
Operating system: Mac OS 10
Version: 10.15.7 [19H1217]
Application architecture: x64
Logical processor count: 32
Processor speed: 3.2 GHz
SqLite Version: 3.34.0
Built-in memory: 98,304.0 MB
Real memory available to Lightroom: 98,304.0 MB
Real memory used by Lightroom: 2,804.1 MB (2.8%)
Virtual memory used by Lightroom: 32,006.0 MB
Memory cache size: 13,214.1MB
Internal Camera Raw version: 13.2 [ 738 ]
Maximum thread count used by Camera Raw: 5
Camera Raw SIMD optimization: SSE2,AVX,AVX2
Camera Raw virtual memory: 531MB / 49151MB (1%)
Camera Raw real memory: 534MB / 98304MB (0%)
Displays: 1) 5120x2160, 2) 3840x2160

Graphics Processor Info: 
Metal: AMD Radeon Pro W5700X

Adobe Administrator

 • 

10.9K Messages

 • 

143.5K Points

7 m ago

Richard, 

Lightroom Classic 10.3 was released today. Is it possible for you to confirm the issue is still there after updating?

47 Messages

 • 

694 Points

@Rikk Thank you for your reply. I checked my Creative Cloud and there are no upgrades currently showing for LrC. I will watch for one in the future. However, have these issues been previously identified and corrected in this next version? Have a great day.

35 Messages

 • 

530 Points

Have you checked your Adobe Creative Cloud icon. My system tells me there are updates available. 

(edited)

47 Messages

 • 

694 Points

Thank you. It did appear in CC about an hour ago and I am downloading it now. Let's hope v10.3 fixes everything!

80 Messages

 • 

1.3K Points

I just upgraded and the new native version seems very fast on the M1 mini! The white image problem is reduced but not eliminated.

47 Messages

 • 

694 Points

7 m ago

Hello

I spent the afternoon testing v10.3 for the errors I identified in my original post. 

Issue #1, continues to be a problem. After deleting the photo description text, it reappears after a restart. LrC does not remember my deletions. I need to go through a re-delete the text when reopening the photobook.

Issue #2, persists. When viewing the book in multi-page view, many of the images do not appear in the pages, see below.

I will keep watch to see if dragging an image into the page causes the page to go blank, forcing a restart to see the image again. A few tests have not replicated the issue, but if I experience it again, I'll update this post with more details.

Here is my system information;

Lightroom Classic version: 10.3 [ 202105281559-8dc50eb4 ]
License: Creative Cloud
Language setting: en-CA
Operating system: Mac OS 10
Version: 10.15.7 [19H1217]
Application architecture: x64
Logical processor count: 32
Processor speed: 3.2GHz
SqLite Version: 3.34.0
Built-in memory: 98,304.0 MB
Real memory available to Lightroom: 98,304.0 MB
Real memory used by Lightroom: 10,838.3 MB (11.0%)
Virtual memory used by Lightroom: 23,675.8 MB
Memory cache size: 13,218.3MB
Internal Camera Raw version: 13.3 [ 807 ]
Maximum thread count used by Camera Raw: 5
Camera Raw SIMD optimization: SSE2,AVX,AVX2
Camera Raw virtual memory: 1023MB / 49151MB (2%)
Camera Raw real memory: 1025MB / 98304MB (1%)
Displays: 1) 5120x2160, 2) 3840x2160

Graphics Processor Info: 
Metal: AMD Radeon Pro W5700X

Thank you and have a great day.

47 Messages

 • 

694 Points

Update to Issue #1: I went to adjust the position of an image that previously had the photo description deleted (filename) and when I moved the image to the left within the photo cell, the photo description reappeared all on its own. It just popped up and I needed to delete it again. This is unusual behaviour on v10.3.

Adobe Administrator

 • 

10.9K Messages

 • 

143.5K Points

7 m ago

@richardadams_3584895 

I am suspicious there may be a problem with your catalog. 

If you select the collection holding all of the photos for your book and then select all and use the File>Export as a Catalog… option to create a test catalog, I am wondering if the test catalog behaves the same. If your book is a saved book, I believe it will come along for the ride in this process formatted as it was. It would allow you to test in any case to see whether this new smaller test catalog behaves the same as your production catalog?

If it does, then we have a small catalog to provide the developers for analysis. If it doesn't then we know the problem is in your production catalog. 

47 Messages

 • 

694 Points

@Rikk

@Rikk   Hello and thank you for your reply. I have done as you have asked. 

Issue #1 (Multi-page view does not display all images) In the new, exported catalogue created from my production catalogue, the issue persists. 


Issue #2 Photo Descriptions won't stay deleted. I open the new catalogue, deleted the descriptions, and closed the catalogue. Upon opening, the descriptions (not all) reappeared.

So exporting a new catalogue does not eliminate these problems.

Anyway, over to you, how do I send these catalogues to the developers?

Have a great day.

Adobe Administrator

 • 

10.9K Messages

 • 

143.5K Points

@richardadams_3584895  I've sent you an email with instructions. 

Adobe Photography Products

Quality Engineering - Customer Advocacy

47 Messages

 • 

694 Points

Hello 

I placed two files in my CC drive, one catalogue zip file for each issue (3.47GB and 3.31GB). They have been uploading for two days and still have not arrived in my folder where I can link these to you to show the developers.

In the meantime, I have continued to work on my books and all of these issues persist, even with the latest update. What else can I do to get help with this issue? Is there a support option associated with my Adobe All Apps subscription that I could access?

Anyway, I keep watching the sync wheel spin and let you know if these files ever get there.

Thank you and have a great day.

Adobe Administrator

 • 

10.9K Messages

 • 

143.5K Points

I will watch for them.  Days seems pretty long for the upload. How fast is your internet connections' upload? I have 20 mbs upload here and a 3 GB file takes under an hour normally.

Adobe Photography Products

Quality Engineering - Customer Advocacy

47 Messages

 • 

694 Points

Hello, as I mentioned to you before, I am not a techie. How do I determine my internet speed? I start the upload when I go to bed because it uses all the bandwidth I have. 12 hours later the wheel is still spinning. I press pause during the day while I work and start it again that night. It's been 24 hours of spinning and nothing, not even one of the files appears in my CC folder. I'll keep trying but there has to be a better way to do this. Thank you and have a nice day.

80 Messages

 • 

1.3K Points

7 m ago

I exported a small catalog (3000 photos) from my Windows PC so that I could work on a photo book on my new Mac M1 Mini. (By the way it was not clear from the Adobe help if this was going to be a move or copy operation. Third party sites reassured me that it was a copy.)

Not only do I see the white photo cells in multi-page view, but sometimes they flash! Sometimes the preview pane flashes too. When they are flashing, Activity Monitor says LRC 10.3 is using 96% of the CPU.

I can stop the flashing by shifting to two-page view, whereupon the CPU usage goes down to 2%. Oh, I just noticed that when white cells are visible in multi-page view the CPU is at 99%.

When in multi-page view, scrolling or hitting the Tab key will change whether and which photo cells exhibit these behaviours. If no white or flashing cells are visible, then CPU usage drops back to 8%.

I originally ran LRC 10.2. I assume that the Creative Cloud updater correctly removed Rosetta when upgrading to 10.3

Lightroom Classic version: 10.3 [ 202105281559-8dc50eb4 ]
License: Creative Cloud
Language setting: en-GB
Operating system: Mac OS 11
Version: 11.4.0 [20F71]
Application architecture: arm64
Logical processor count: 8
Processor speed: NA
SqLite Version: 3.34.0
Built-in memory: 16,384.0 MB
Real memory available to Lightroom: 4,096.0 MB
Real memory used by Lightroom: 4,277.8 MB (104.4%)
Virtual memory used by Lightroom: 407,143.1 MB
Memory cache size: 293.7MB
Internal Camera Raw version: 13.3 [ 807 ]
Maximum thread count used by Camera Raw: 5
Camera Raw SIMD optimization: SSE2
Camera Raw virtual memory: 1928MB / 8191MB (23%)
Camera Raw real memory: 1924MB / 4096MB (46%)
Displays: 1) 4096x2160

Graphics Processor Info: 
Metal: Apple M1

Application folder: /Applications/Adobe Lightroom Classic
Library Path: /Users/erichschlaikjer/Pictures/Lightroom/Lightroom Catalog.lrcat
Settings Folder: /Users/erichschlaikjer/Library/Application Support/Adobe/Lightroom

Installed Plugins: 
1) AdobeStock
2) Aperture/iPhoto Importer Plug-in
3) Facebook
4) Flickr
5) Nikon Tether Plugin

Config.lua flags: None

AudioDeviceIOBlockSize: 512
AudioDeviceName: $$$/dvaaudiodevice/SystemDefaultAndEffectiveDeviceName=System Default - Mac mini Speakers#{comment}DVAAU-4201250: Open the audio hardware preferences page.
AudioDeviceNumberOfChannels: 2
AudioDeviceSampleRate: 48000
Build: LR5x24
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: 32
GL_GREEN_BITS: 8
GL_MAX_3D_TEXTURE_SIZE: 2048
GL_MAX_TEXTURE_SIZE: 16384
GL_MAX_TEXTURE_UNITS: 8
GL_MAX_VIEWPORT_DIMS: 16384,16384
GL_RED_BITS: 8
GL_RENDERER: Apple M1
GL_SHADING_LANGUAGE_VERSION: 1.20
GL_STENCIL_BITS: 8
GL_VENDOR: Apple
GL_VERSION: 2.1 Metal - 71.6.4
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_draw_buffers2 GL_EXT_draw_range_elements GL_EXT_fog_coord GL_EXT_framebuffer_blit GL_EXT_framebuffer_multisample GL_EXT_framebuffer_multisample_blit_scaled 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_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_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_point_size GL_APPLE_vertex_program_evaluators GL_APPLE_ycbcr_422 GL_ATI_separate_stencil GL_ATI_texture_env_combine3 GL_ATI_texture_float GL_IBM_rasterpos_clip GL_NV_blend_square GL_NV_conditional_render GL_NV_depth_clamp GL_NV_fog_distance GL_NV_fragment_program_option GL_NV_fragment_program2 GL_NV_light_max_exponent GL_NV_texgen_reflection GL_NV_texture_barrier GL_NV_vertex_program2_option GL_NV_vertex_program3 GL_SGI_color_matrix GL_SGIS_generate_mipmap GL_SGIS_texture_edge_clamp GL_SGIS_texture_lod 

Adobe Administrator

 • 

10.9K Messages

 • 

143.5K Points

7 m ago

For clarity:

Do you see this issue on Windows and your Apple Silicon Machine or only on the M1?

80 Messages

 • 

1.3K Points

It is happening on my M1 Mini (synonymous with Apple Silicon).

I went back to my Windows machine and scrolled around really fast in multi-page view. No problem.
Then I shrank the thumbnails and did the same. It was fine for a while, but I did manage to get it to a point where it seemed to reproduce the problem. See picture.
Many cells were white, and the CPU was at 100%. Also that black "Standard Landscape" rectangle came and went repeatedly in the upper left corner (normally those words are on a transparent background).
But then after maybe 30 or 40 seconds Lightroom became responsive again and all the white cells got filled in OK.
At this point Task Manager reports that LRC is using 6.5 GB of memory.

Ooh, I have provoked the bug again now. So far three real minutes have passed and five cpu minutes, and Lightroom's display is still not fixed.
I was able to switch LR back to Library view and the cpu usage stopped. Task manager now shows LR using 7 GB of memory.

80 Messages

 • 

1.3K Points

So, to be really clear, the problem occurs on both Windows and MacOS. It seems like shrinking the thumbnail size helps to trigger it.

80 Messages

 • 

1.3K Points

I note that Richard Adams's image shows the thumbnail slider all the way to the left, so smallest thumbnails and maximum number of book pages on view at once. It seems really easy to reproduce the bug this way for me, on two different machines and OS's.

On the other hand, this bug is not crippling as LR remains fairly responsive and you can often stop the behaviour by increasing thumbnail size or doing something else to resize the view, like hitting tab.

80 Messages

 • 

1.3K Points

7 m ago

This bug is not a huge deal for me since it is easy to stop.

 

Still, I got to wondering about it while jogging. It looks like a paint loop. For example, if a program, while processing the WM_PAINT message somehow invalidates the window, it will paint again and again. For example, causing the window to resize during the paint message could cause a loop, especially if the size does not converge. My experience of this current bug is that sometimes the paint loop stops, but as you shrink the thumbnails, the loops looks effectively eternal.

 

So I had a look in Spy++. There is one window holding all the thumbnails. (The thumbnails are not themselves windows, which is good.) This window is of class AfxWnd140u with the title “ (Bridge View)” with a leading space. It has no child windows. Its parent is called “ClipView”, with parent “Scroll View” with parent “View” with parent “Panel Host (LayoutPanels)” with parent “Main Switcher View” with parent “Top/Bottom Panel Host” with parent “” (AfxFrameOrView), with parent “Lightroom Catalog-2-v10 - Adobe Photoshop Lightroom Classic – Book”.

 

If I spy on messages to “ (Bridge View)” during the buggy behavior, it sure enough gets one WM_PAINT message after another. Why? There might be a good reason, although I cannot think of one offhand. It could be painting one partial region at a time, although I cannot tell from the parameters. There is no smoking gun of a corresponding WM_SIZE message, at least not to this window. Perhaps other windows are resizing or repositioning, causing the Bridge View to repaint. Its parent is also repeatedly getting a User-defined WM_USER+104 message of unknown purpose.

 

Presumably another window, probably a parent, is invalidating the Bridge View window. I spied on all the LR process windows and was inundated in messages. Still, one suspect stood out. This is the “Bezel” top level window, which contains one of its own “ (Bridge View)” windows, plus static text windows for “Standard Landscape”, “10 x 8 in (25 x 20 cm)”, and “264 pages – US $104.79”. As I remarked earlier, this window keeps flashing. And it gets a lot of messages about repositioning itself. It might be part of the paint loop.

 

That’s as far as I got.