Lightroom/Camera Raw: Cannot merge panorama after updating to 10.14.6

  • 12
  • Problem
  • Updated 1 week ago
  • Solved
  • (Edited)
Since upgrading to OS 10.14.6, Lightroom Classic (8.3.1) cannot merge (21 frame) panoramic images. Just sits there forever and does nothing.
Photo of Ray Majoran

Ray Majoran

  • 16 Posts
  • 4 Reply Likes

Posted 1 month ago

  • 12
Photo of Ray Majoran

Ray Majoran

  • 16 Posts
  • 4 Reply Likes
Aright, so cancel my previous note about everything working again... I clearly did not try some of my larger panos. Back to status quo -- Lightroom is not merging my larger panos on 10.14.6. 

To help with the debugging of all this, I've recorded a video (and some curious CPU usage) showing which ones I can merge and which ones I can't... along with disk space, memory, etc. As I note in the video, it's almost like Lightroom loses interest at a certain point.

Here is a link to the video:

https://vimeo.com/353872509/7de2352614 

And here is my system info:

Lightroom Classic version: 8.3.1 [ 201905241238-dcd7e2de ]
License: Creative Cloud
Language setting: en-CA
Operating system: Mac OS 10
Version: 10.14.6 [18G87]
Application architecture: x64
Logical processor count: 8
Processor speed: 2.9 GHz
Built-in memory: 16,384.0 MB
Real memory available to Lightroom: 16,384.0 MB
Real memory used by Lightroom: 4,096.9 MB (25.0%)
Virtual memory used by Lightroom: 12,471.9 MB
Memory cache size: 397.7MB
Internal Camera Raw version: 11.3 [ 197 ]
Maximum thread count used by Camera Raw: 5
Camera Raw SIMD optimization: SSE2,AVX,AVX2
Camera Raw virtual memory: 4811MB / 8191MB (58%)
Camera Raw real memory: 4845MB / 16384MB (29%)
Displays: 1) 3840x2400, 2) 1920x1080, 3) 1920x1080

Graphics Processor Info: 
Metal: AMD Radeon Pro 460



Application folder: /Applications/Adobe Lightroom Classic
Library Path: /Users/rmajoran/Desktop/_Photos/2019-08-06 Coldstream Sunset Drone/Lightroom/Lightroom.lrcat
Settings Folder: /Users/rmajoran/Library/Application Support/Adobe/Lightroom

Installed Plugins: 
1) AdobeStock
2) Aperture/iPhoto Importer Plug-in
3) Canon Print Studio Pro
4) Export to Autopano Giga 4.2
5) Export to Autopano Giga 4.4
6) Facebook
7) Flickr
8) HDR Efex Pro 2
9) Luminar 3
10) Luminar Flex
11) Nikon Tether Plugin

Config.lua flags: None

AudioDeviceIOBlockSize: 512
AudioDeviceName: AirPods - Ray
AudioDeviceNumberOfChannels: 2
AudioDeviceSampleRate: 48000
Build: 12.1x4
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 Pro 460 OpenGL Engine
GL_SHADING_LANGUAGE_VERSION: 1.20
GL_STENCIL_BITS: 8
GL_VENDOR: ATI Technologies Inc.
GL_VERSION: 2.1 ATI-2.11.20
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
Photo of Andre Schuster

Andre Schuster

  • 19 Posts
  • 3 Reply Likes
Exporting TIFs based on CR2 uses also only one CPU-core... it works but it takes much more time than usual. Maybe not only a DNG-problem...
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 5882 Posts
  • 1290 Reply Likes
Need an additional piece of information. Is this failure on only 360 degree panos or all panos?
Photo of James Goodacre

James Goodacre

  • 40 Posts
  • 9 Reply Likes
Hi Rikk, it’s all Pano’s.
Photo of Ray Majoran

Ray Majoran

  • 16 Posts
  • 4 Reply Likes
Rikk, feel free to watch the video link I provided on Page 2 of this thread. I give samples, CPU readings, etc.
(Edited)
Photo of Carlos Cardona

Carlos Cardona

  • 499 Posts
  • 104 Reply Likes
Rikk: does it seem to you that the common factors are Mac laptops/Mojave/LR 8.4 users? Or did I miss a post?
Photo of Andre Schuster

Andre Schuster

  • 19 Posts
  • 3 Reply Likes
I'm not using LR on a MBP but on a Mac Mini, same problems. Common factor is maybe i7?
Photo of Victoria Bampton - Lightroom Queen

Victoria Bampton - Lightroom Queen, Champion

  • 5103 Posts
  • 1995 Reply Likes
> does it seem to you that the common factors are Mac laptops/Mojave/LR 8.4 users? Or did I miss a post?

Carlos, it's not new to 8.4, happens with previous too. It's specific to 10.14.6, didn't happen in 10.14.5. Tricky bit is it doesn't affect everyone on 10.14.6. My suspicion right now is onboard graphics (MacBooks/Mini's) or high memory usage.

@Rikk, merge of that test set completes on my iMac (unlike my 13" MBP) but the LR RAM usage remains at 16GB after it completes. Shouldn't that drop back down? Or have I just not noticed it before?
Photo of Robert Somrak

Robert Somrak, Champion

  • 387 Posts
  • 130 Reply Likes
Victoria,

I reported earlier I wasn't having issues with my 2015 iMac but today the merge stopped on a 11 set pano I merged 2 days ago. It sat for over an hour and I canceled the pano.  Then other panos would not merge, even 4 photos.  A restart of Lr didn't help.  I had to restart the computer to get the pano function going again.  Lr 8.4. MacOS 10.14.6
(Edited)
Photo of Ray Majoran

Ray Majoran

  • 16 Posts
  • 4 Reply Likes
Rikk,

Just wondering if you had any update on this issue? Might there by an 8.4.1 patch coming soon that would resolve this issue? I would be happy to be on a beta list if it meant getting the patch early, as it's really debilitated my workflow for both large panos and large HDR's. Thanks in advance.
Photo of Ray Majoran

Ray Majoran

  • 16 Posts
  • 4 Reply Likes
Rikk,

Just wondering if you had any update on this issue? Might there by an 8.4.1 patch coming soon that would resolve this issue? I would be happy to be on a beta list if it meant getting the patch early, as it's really debilitated my workflow for both large panos and large HDR's. Thanks in advance.
Photo of James Goodacre

James Goodacre

  • 40 Posts
  • 9 Reply Likes
Just adding to this. Would also be happy to help out with beta testing. Alternatively I have to jump ship to a different toolset at 80% of what I shoot is now unprocessable.
Photo of Johan Elzenga

Johan Elzenga, Champion

  • 2185 Posts
  • 901 Reply Likes
I see this too on my MacBook Pro 13”, but not on my MacMini 2018. The most obvious difference between the two machines is that I use a BlackMagic eGPU to feed the two 4K displays on my MacMini, while on the laptop I see it when I use the laptop without any extra hardware. That could point to the Intel GPU on the laptop. Turning on/off GPU acceleration on the laptop does not make a difference, though.
Photo of Andre Schuster

Andre Schuster

  • 19 Posts
  • 3 Reply Likes
all panos.
Photo of bry2k

bry2k

  • 3 Posts
  • 1 Reply Like
Hey Ray, in Activity Monitor, while the Pano is stalled, select Lightroom in the list of processes, then click the little gear icon and choose "Sample". That will generate a process sample showing what Lightroom is doing. Then post it for Adobe. It can help them trace where in the code things are hanging up. Also you can double click Lightroom in Activity Monitor, a window will open, then click on the "open files and ports" tab and there will be a list of every file Lightroom is currently utilizing. Lots of it doesn't matter, but it will also show if there are files open related to caches etc that may be part of the issue.
Photo of David Yang

David Yang

  • 2 Posts
  • 0 Reply Likes
I've the same issue and contact Adobe support, YES, they knew the problems and only told me the support team are working on it. the only thing that I can do now is waiting, such a annoying answer 
Photo of Michael

Michael

  • 2 Posts
  • 0 Reply Likes
Just found this and to chime in as well. I to have this issue. I have tried deleting cache, scrubbing Adobe from my Macbook and reinstalling, fresh installing Mojave and Lightoom, trying different cameras and file names, creating a new Lightroom catalog, not allowing GPU acceleration, Changing raw cache size, changing how much ram Adobe can take, changing how Lightroom changes Raw files, Used Raw and JPEG files, Turned off Automatically writing changes to XMPs, turned off develop settings inside metadata, turned off address lookup and face detection (mostly because it says pause and thought it might be trying to do two things at once), tried all kinds of things for creating previews and smart previews (incase it was catching on making the preview for Lightroom). I am sure I have done other things and forgotten them. I spent days so far trying to troubleshoot it. All this didn't seem to make a difference. occasionally, and very randomly, a panorama would finish. But this was very infrequent. Both HDR and Panoramas stall. Yesterday I couldn't get a HDR to finish. 

The only thing that worked was downgrading to High Sierra and an older version of Lightroom using Timemachine. As soon as I reinstalled Mojave though, which I need, and updating Lightroom it stalled again. 

I am running a 2017 Macbook pro 15" 

Lightroom Classic version: 8.4 [ 201908011719-03751b60 ]
License: Creative Cloud
Language setting: en-US
Operating system: Mac OS 10
Version: 10.14.6 [18G87]
Application architecture: x64
Logical processor count: 8
Processor speed: 3.1 GHz
Built-in memory: 16,384.0 MB
Real memory available to Lightroom: 16,384.0 MB
Real memory used by Lightroom: 1,327.7 MB (8.1%)
Virtual memory used by Lightroom: 4,321.7 MB
Memory cache size: 15.3MB
Internal Camera Raw version: 11.4 [ 273 ]
Maximum thread count used by Camera Raw: 5
Camera Raw SIMD optimization: SSE2,AVX,AVX2
Camera Raw virtual memory: 489MB / 8191MB (5%)
Camera Raw real memory: 498MB / 16384MB (3%)
Displays: 1) 3360x2100

Graphics Processor Info: 
Metal: AMD Radeon Pro 560

Also had a post up on the forums about it. 
https://forums.adobe.com/message/11202289#11202289
Photo of Victoria Bampton - Lightroom Queen

Victoria Bampton - Lightroom Queen, Champion

  • 5103 Posts
  • 1996 Reply Likes
For reference, this appears to be the same issue reported on Cloudy: https://feedback.photoshop.com/photoshop_family/topics/merging-dng-images-into-hdr-causes-high-memor...
Photo of Ray Majoran

Ray Majoran

  • 16 Posts
  • 4 Reply Likes
Anyone heard of any updates? I know Adobe will be testing/patching/etc., and that it does take some time. If there is a pre-release beta (once a patch has been applied), I would love to get my hands on it. This is debilitated my workflow.
(Edited)
Photo of Brano J. Svac

Brano J. Svac

  • 1 Post
  • 0 Reply Likes
I think I can pretty much confirm the above conclusions. I tried to stitch HDR panorama consisting of 30 DNG files of 45MP each, with the below results:

MacBook Pro (Retina, 15-inch, Mid 2015)
macOS Mojave 10.14.6
Lightroom Classic 8.4
Canceled after not even seeing a preview after 3 hours

MacBook Pro (13-inch, Early 2011)
macOS High Sierra 10.13.6
Lightroom Classic 8.4
Didn't exactly time it but it didn't take longer than 20 minutes (preview and stitching to final DNG panorama file)
Photo of Conrad Chavez

Conrad Chavez

  • 9 Posts
  • 2 Reply Likes
I just ran into this today. I hope the following wrinkles will help isolate this:
  • macOS 10.14.6
  • Panasonic raw files (DMC-G85)
  • 15-image 2D grid, 3 rows of 5 images, not 360.
  • Perspective projection
  • Panorama merge preview displayed as quickly as expected. I liked the preview so I clicked Merge.
  • After clicking Merge, progress bar moves quickly toward halfway and then hangs there forever, or at least I canceled the panorama process after about half an hour.
But later I successfully completed the merge this way:
  • I imported the same images into another existing catalog. Neither catalog is new.
  • It merged in two minutes. Resulting panorama is over 300 megapixels.
  • The catalog where they merged successfully is much smaller than the one where they merged unsuccessfully.
So maybe it's affected by some aspect of the database.

At no point did Lightroom Classic appear to be low on RAM in either case, it was using about 9GB out of 16GB RAM. When the merge hangs, CPU is around 100% on a quad core (400%) CPU.
(Edited)
Photo of David Golding

David Golding

  • 78 Posts
  • 4 Reply Likes
One concern with test. Does the second go round with the same set of frames take advantage of what is in CACHE? How about purging CACHE before trying..

And, as for something in RAM, perhaps a cold boot.
(Edited)
Photo of Wojtek Nagrodzki

Wojtek Nagrodzki

  • 5 Posts
  • 0 Reply Likes
This reply was created from a merged topic originally titled Lightroom: Merging DNG images into HDR causes high memory consumption and crash.

Hi,

I noticed memory leaks during in HDR merging. Memory consumption goes so high that app stops responding and has to be killed. Issue is 100% reproducible.

Steps to reproduce:
1. Get 4 set of images for HDR merging (each set containing 3 DNG images, 6000 × 4000 pix, ~30MB)
2. Perform first HDR merge, observe RAM consumption
3. Perform next merge

App stops during third merge on my MacBook Air. I would expect memory to go down after processing the first set.

I can provide the DNG files if needed.



System info...
Lightroom version: 2.4 MAS [ 20190802-0905-45e6444 ] (Aug  2 2019)NGL Version: 1.10.0.4
Operating system: macOS
OS Version: 10.14 [6]
Application architecture: x64
Computer model: MacBookAir8,2 / Intel(R) Core(TM) i5-8210Y CPU @ 1.60GHz
Logical processor count: 4
Processor speed: 1,6 GHz
Built-in memory: 8 192,0 MB
Real memory available to Lightroom: 8 192,0 MB
Real memory used by Lightroom: 226,2 MB (2,7%)
Virtual memory used by Lightroom: 5 444,3 MB
Memory cache size: 580,1 MB
Internal Camera Raw version: 11.4 [ 274 ]
Maximum thread count used by Camera Raw: 3
Camera Raw SIMD optimization: SSE2,AVX,AVX2
Camera Raw virtual memory: 3655MB / 4095MB (89%)
Camera Raw real memory: 3652MB / 8192MB (44%)
Displays: 1) 2880x1800

Graphics Processor Info: Metal: Intel(R) UHD Graphics 617

Application folder: /Applications
Settings Folder: /Users/wojtek/Library/Containers/com.adobe.mas.lightroomCC/Data/Library/Application Support/Adobe/Lightroom CC
Photo of Daulton Venglar

Daulton Venglar

  • 2 Posts
  • 0 Reply Likes
This reply was created from a merged topic originally titled merging HDR and panorama grinds to a halt.

Ever since updating to the latest version of Lightroom Classic, the thermal throttling is insane. Once my computer heats up, it becomes impossible to merge an HDR or panorama. Worked just fine in the previous version of the software. 
Photo of Tod Poirier

Tod Poirier

  • 8 Posts
  • 1 Reply Like
I am also running into this issue.  I'm working with .raw Nikon files on a construction project I've been documenting for the last 2 years.  Merges that wouldn't have been a problem a month ago are stalling Lightroom, but only Lightroom.  I'm running on a 27" iMac.  I haven't done anything yet to try to solve it other than a cursory look at prefs and finding a couple posts like this to follow.
Lightroom Classic version: 8.4 [ 201908011719-03751b60 ]

License: Creative Cloud
Language setting: en-US
Operating system: Mac OS 10
Version: 10.14.6 [18G87]
Application architecture: x64
Logical processor count: 4
Processor speed: 3.5 GHz
Built-in memory: 24,576.0 MB
Real memory available to Lightroom: 24,576.0 MB
Real memory used by Lightroom: 3,675.1 MB (14.9%)
Virtual memory used by Lightroom: 14,967.5 MB
Memory cache size: 104.4MB
Internal Camera Raw version: 11.4 [ 273 ]
Maximum thread count used by Camera Raw: 3
Camera Raw SIMD optimization: SSE2,AVX,AVX2
Camera Raw virtual memory: 8082MB / 12287MB (65%)
Camera Raw real memory: 8101MB / 24576MB (32%)
Displays: 1) 5120x2880, 2) 1920x1200

Graphics Processor Info: 
Metal: AMD Radeon Pro 575



Application folder: /Applications/Adobe Lightroom Classic
Library Path: /Volumes/Lazy Acres 2018/Greg's project/Greg's Project/Greg's Project-2.lrcat
Settings Folder: /Users/todpoirier/Library/Application Support/Adobe/Lightroom

Installed Plugins: 
1) Export to Photomatix Pro
2) Facebook
3) HDR Efex Pro 2
4) ShootProof

Config.lua flags: None

AudioDeviceIOBlockSize: 512
AudioDeviceName: Built-in Output
AudioDeviceNumberOfChannels: 2
AudioDeviceSampleRate: 44100
Build: 12.1x4
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 Pro 575 OpenGL Engine
GL_SHADING_LANGUAGE_VERSION: 1.20
GL_STENCIL_BITS: 8
GL_VENDOR: ATI Technologies Inc.
GL_VERSION: 2.1 ATI-2.11.20
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 
Photo of Jamie Overland

Jamie Overland

  • 3 Posts
  • 2 Reply Likes
This reply was created from a merged topic originally titled Panorama merge hanging at about 50% - Lightroom Classic 8.4.

Twice now I've tried a simple 5 image panorama but it keeps hanging at about 50% progress. The preview worked fine. I've left it now for an hour and still hanging
I've not had any problems before? Any suggestions?

I'm running a iMac with Mojave V10.14.6
Photo of Ray Majoran

Ray Majoran

  • 16 Posts
  • 4 Reply Likes
Hey Jamie, We are all in the same boat. Adobe is aware of the issue and hopefully will be releasing a patch very soon. *fingers crossed*. It’s destroying the work flow of many of us.
Photo of Jamie Overland

Jamie Overland

  • 3 Posts
  • 2 Reply Likes
Thanks Ray, at least I'm not alone...some comfort taken! I've noticed that it does complete some but not all. The ones its does complete take ages! The example I posted actually did complete, 1hr 30mins later!!
Photo of James Goodacre

James Goodacre

  • 40 Posts
  • 9 Reply Likes
Fingers crossed indeed. This issue is entirely preventing me processing any panorama images on any of the adobe products.
Photo of Jeffrey Tranberry

Jeffrey Tranberry, Sr. Product Manager, Digital Imaging

  • 15586 Posts
  • 2345 Reply Likes
Official Response
Please update macOS. Go to System Preferences > Software Update and install the following update:

macOS Mojave 10.14.6 Supplemental Update   –– Restart Required
This update contains bug fixes that improve the stability, performance, and security of your Mac, and is recommended for all users.

This update:


  • Resolves an issue that may cause certain Mac notebooks to shut down during sleep

  • Fixes an issue that may degrade performance when working with very large files

  • Addresses an issue that may prevent Pages, Keynote, Numbers, iMovie, and GarageBand from updating

For more detailed information about this update, please visit: https://support.apple.com/kb/HT209149

For detailed information about the security content of this update, please visit: https://support.apple.com/kb/HT201222
(Edited)
Photo of Robert Somrak

Robert Somrak, Champion

  • 387 Posts
  • 130 Reply Likes
I just did  11 shot and 12 shot panos that I quit the merges before the Apple update as they seemed to be stuck and they merged after the update.   Time will tell.
Photo of James Goodacre

James Goodacre

  • 40 Posts
  • 9 Reply Likes
Jeffrey, thank you to you and the teams on both sides that worked on this issue.
Photo of Simon Bierwald

Simon Bierwald

  • 1 Post
  • 1 Reply Like
Problem Solved. Thanks a lot! 
Photo of Gavin Hayhurst

Gavin Hayhurst

  • 1 Post
  • 1 Reply Like
Been really struggling to stitch pano's from my holiday after not having done it for a few months, they were taking ages and many looked like they had hung. This morning I let a 25 RAW image HDR pano build run and it took over 4 hours but it did eventually complete. Stumbled across this thread, updated my OS and built the same pano in under 2 minutes. Things look back to how they used to be. Thanks to everyone who helped sort it.
Photo of Ray Majoran

Ray Majoran

  • 16 Posts
  • 4 Reply Likes
BAM! Just created my first 21-stitch Pano from Lightroom in weeks. Thank you! Update did the trick.
Photo of David Yang

David Yang

  • 2 Posts
  • 0 Reply Likes
Wow, finally, it works perfectly fine after the above suggested update of Mac OS, thanks for your kindly help and wish more people who have the same issues can see this post! Thank you so much for your efforts on this. 
Photo of Andre Schuster

Andre Schuster

  • 19 Posts
  • 3 Reply Likes
Am I the only one who feels that (although working) it's still slower than before?
Photo of James Goodacre

James Goodacre

  • 32 Posts
  • 8 Reply Likes
Tbh in my case I think it’s now back to normal.
Photo of Michael

Michael

  • 2 Posts
  • 0 Reply Likes
I can tell you that batch processing a few files a couple of them took way longer than others. I don't know the reason behind it. The files are roughly the same size and number of photos in a pano are the same, but I have had some panos take much longer than others. I figure it will take them another update to even everything out, at least it works again. 
Photo of James Goodacre

James Goodacre

  • 40 Posts
  • 9 Reply Likes
57 uncompressed raw file (85MB each) hdr pano just completed. Used 107GBof scratch space during merge (1.1GB output file) which is in line with expectations. Great to have my system back working again.
Photo of Tod Poirier

Tod Poirier

  • 8 Posts
  • 1 Reply Like
This has made it possible to work again, but it seems I can only do 5-7 HDR pano merges before the merge freezes up and I have to restart Lightroom.
Photo of James Goodacre

James Goodacre

  • 40 Posts
  • 9 Reply Likes
I was going to post something similar.
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 5850 Posts
  • 1280 Reply Likes
Not related to previous problem - creating new thread.

Please reference the new conversation here: Lightroom needs restarted after 5-7 Pano Merges
Photo of James Goodacre

James Goodacre

  • 40 Posts
  • 9 Reply Likes
FYI, I have found that although a merge is now working (even with very large file sets), it is not possible to merge 2 separate panoramas in a row without restarting Lightroom.
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 5882 Posts
  • 1290 Reply Likes
Not related to previous issue.

Please reference the new conversation here: Lightroom needs to restart between pano merges
Photo of Robert Somrak

Robert Somrak, Champion

  • 388 Posts
  • 130 Reply Likes
Rikk
The new conversation is not open to comments
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 5882 Posts
  • 1290 Reply Likes
That is because it is merged with the post immediately above.... It is open to additional comments. 
Photo of Robert Somrak

Robert Somrak, Champion

  • 388 Posts
  • 130 Reply Likes
Sorry. I was confused with the “not related to previous issue” comment
Photo of Koro

Koro

  • 28 Posts
  • 6 Reply Likes
Good morning everyone,

This thread concerning difficulties with merging panoramas began about a month ago. At that time I posted a comment offering a 'solution' which suggested changing the file names of the images going into the merge process. A lot of highly technical discussion followed on most of which was of no particular value to me but it seemed to lead to solutions for at least some people. All good.

My purpose with this post is simply to place into the record another instance of the merge function failing until the file names were changed. By 'failing' I mean: on invoking the menu command, nothing happened. That is, the system behaved as if there had been no interaction whatsoever. I did it again (right-click/Photo Merge/Panorama). Same result: nothing, not even a flicker on the screen.

The images came from an iPhone5 and were imported directly from the phone so the original file names were of the form "IMG_1234.JPG". The renamed files have file names like this: DIG yyyy.mm.dd-seqno.JPG, e.g.: "DIG 2019.09.10-001.JPG" .

I'm running a MAC, macOS Mojave V10.14.6, Lightroom Classic version: 8.4 [ 201908011719-03751b60 ].

When I wrote my first post and this one I deliberately placed the word 'solution' in scare quotes because my suggestion seemed very much like a not-solution, more like a goofy, blue-sky coincidence. How the file name could influence the behaviour of the merge function is, I readily accept, in the realm of the weird.

But empirical evidence at this office suggests there is a connection. I have observed this behaviour now 4 or 5 -- perhaps more -- times. Once again, I'm not looking for some kind of solution, I'm just reporting behaviour that I observe at this installation.

Cheers,
Koro