P: Panorama Photo Merge not working (Windows - with Custom Scale Factor)

2 Votes
Community Beginner ,
Jun 11, 2019 Jun 11, 2019

Copy link to clipboard

Copied

I have been trying to create a panorama in lightroom desktop with 10 images, but it get's stuck in 'creating preview' for me and dosn't move. I have noticed that when I start the panorama, my CPU usage goes up, but then creeps down with no progress. However, it's been working perfectly in lightroom classic.

Bug Fixed
TOPICS
Windows

Views

8

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

Adobe Employee , Jun 20, 2019 Jun 20, 2019
Confirmed. With 130% scale factor, I see the same behavior. We'll be working on a fix for this.

Votes

Translate

Translate
30 Comments
Adobe Employee ,
Jun 11, 2019 Jun 11, 2019

Copy link to clipboard

Copied

Carlos, if you break down the merge into two merges of 5 does the merge complete?

If you could, please go to Help>System Info... and get us your installed Lightroom version number?
Rikk Flohr - Customer Advocacy: Adobe Photography Products

Votes

Translate

Translate

Report

Report
Community Beginner ,
Jun 11, 2019 Jun 11, 2019

Copy link to clipboard

Copied

Hi, I tried merging 5 images and also 3 images, both were stuck at creating preview and no panorama was created. I'm currently running Lightroom version 2.3.

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Jun 12, 2019 Jun 12, 2019

Copy link to clipboard

Copied

What is the source device that generated the files you are attempting to merge? Are the files raw, jpeg, something else? Were they shot on a tripod, handheld but stationary, moving while capturing?
Rikk Flohr - Customer Advocacy: Adobe Photography Products

Votes

Translate

Translate

Report

Report
Community Beginner ,
Jun 12, 2019 Jun 12, 2019

Copy link to clipboard

Copied

They are RAW files from a Canon EOS 7D. They were shot hand held, do keep in mind that I have already stitched the image in lightroom classic and it worked fine, but it's not working in lightroom desktop.

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Jun 12, 2019 Jun 12, 2019

Copy link to clipboard

Copied

Carlos,

Are you Mac or Windows?
What is your operating system version?
Do you have the ability to share the files with us so that we can test Merge with them?
Rikk Flohr - Customer Advocacy: Adobe Photography Products

Votes

Translate

Translate

Report

Report
Community Beginner ,
Jun 12, 2019 Jun 12, 2019

Copy link to clipboard

Copied

Hi, I'm running Windows 10 version 1803. I can upload the files to my ondrive and share the link to them, I just need to know where to send the link.

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Jun 13, 2019 Jun 13, 2019

Copy link to clipboard

Copied

RackMultipart201906131021951v3-87009b01-f7bc-47b0-8578-467939b6b844-2002343213.jpg
Rikk Flohr - Customer Advocacy: Adobe Photography Products

Votes

Translate

Translate

Report

Report
Community Beginner ,
Jun 13, 2019 Jun 13, 2019

Copy link to clipboard

Copied

I have sent a link to that address with the images. 

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Jun 13, 2019 Jun 13, 2019

Copy link to clipboard

Copied

I got the files Carlos and imported them into Lightroom Desktop 2.3.  They merged with no errors after about 60 seconds elapsed time. 
RackMultipart2019061311996510f-44c566d5-7bdb-4662-860c-217b59686965-1975859942.png

It is time to provide some system information:

System Specs?
OS Version?
Free Space on primary hard drive?
Rikk Flohr - Customer Advocacy: Adobe Photography Products

Votes

Translate

Translate

Report

Report
Community Beginner ,
Jun 13, 2019 Jun 13, 2019

Copy link to clipboard

Copied

Hi, 
I am running windows 10 Home 64-bit, version 1803.
CPU: Core i5-8600K @ 3.6GHz
RAM: 16 GB 2666MHz DDR4 
GPU: EVGA GTX SC 1070Ti Black edition
Primary hard drive: 512GB Samsung 970 Evo NVMe SSD (354GB free) - Used for program install
Secondary hard drive: 1TB Samsung 860 Evo SATA SSD (752GB free) - Pictures folder is here

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Jun 13, 2019 Jun 13, 2019

Copy link to clipboard

Copied

Ok. My first test was on Mac. I just tried the merge on a Windows laptop Win 10 (1809) and it merged fine within 90 seconds. 

Your free space on your hard drives looks fine so no issue there. Your Windows version is a little older and you might check Microsoft for an update. 

When I did the merge, I was using a Spherical Projection and had Boundary Warp set to 100.  What are your settings there?
Rikk Flohr - Customer Advocacy: Adobe Photography Products

Votes

Translate

Translate

Report

Report
Community Beginner ,
Jun 13, 2019 Jun 13, 2019

Copy link to clipboard

Copied

I am using the spherical projection as well, but boundary warp set to 0 (setting it to 100 makes no difference). I have just updated to windows version 1903, but that hasn't fixed the issue either.

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Jun 14, 2019 Jun 14, 2019

Copy link to clipboard

Copied

Next step Carlos will be to perform the following:

  1. Close Lightroom.
  2. Restart the computer.
  3. Open Lightroom.
  4. Attempt the merge
  5. When it fails, go to Preferences>Account and hold down the [A/t/Opt] Key and click the [Diagnostic Log] button.  
Send the log to me at:

RackMultipart2019061449151urv6-3a7f2036-5d4e-401e-b424-4aee97d63a55-1417027995.jpg
Rikk Flohr - Customer Advocacy: Adobe Photography Products

Votes

Translate

Translate

Report

Report
Community Beginner ,
Jun 14, 2019 Jun 14, 2019

Copy link to clipboard

Copied

I have sent the diagnostic log document to the adress.

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Jun 14, 2019 Jun 14, 2019

Copy link to clipboard

Copied

Got it. Thanks!
Rikk Flohr - Customer Advocacy: Adobe Photography Products

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Jun 20, 2019 Jun 20, 2019

Copy link to clipboard

Copied

Carlos, can you put the source images into an album, then choose 'Store Album Locally' for that album in the 3-dot menu in the grid header bar (when the album is selected)?

After that is done, the album should have a blue dot on it in the left side panel:

RackMultipart20190620843831r5z-8614c488-7769-4174-a9ab-d5508642c96f-1169647404.png

You'll see a dialog that informs you how much disk space will be consumed by the originals locally.

The idea with this is to establish whether the problem has to do with source file access during the merge operation.

Also, does the progress bar stop at the same percentage each time? If so, what percentage? If not, what's an example value that you've seen?

Thanks

Votes

Translate

Translate

Report

Report
Community Beginner ,
Jun 20, 2019 Jun 20, 2019

Copy link to clipboard

Copied

I did as you said and it didn't change the result. The progress always stops at 0% of creating the preview (it does not seem to start at all), I assume it's not actually processing the preview as the CPU usage drops to 0% after a couple of seconds of starting and stays there.RackMultipart201906201062721e0-a3f2dd69-8cc1-4635-b7dc-b5d76f2b1389-1099221463.png

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Jun 20, 2019 Jun 20, 2019

Copy link to clipboard

Copied

Which version of Lightroom Classic were you using when you successfully merged the images? I'm curious if Lightroom Classic 8.3 merges this image set successfully.

Votes

Translate

Translate

Report

Report
Community Beginner ,
Jun 20, 2019 Jun 20, 2019

Copy link to clipboard

Copied

I was running lightroom classic version 8.3.1. Classic does merge them successfully and pretty quickly I should add. RackMultipart2019062070803104x-64b57c00-96c4-4272-a836-f0315411f811-86856469.png

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Jun 20, 2019 Jun 20, 2019

Copy link to clipboard

Copied

Thanks. The next thing I can think of that might shed more light on what the root problem is is slightly involved. From https://forums.adobe.com/thread/925598, this should work for Lightroom Desktop as well:

To get Lightroom traceback info:

 

Windows 
1. Right click the Lightroom icon you use to launch on the desktop and choose Copy from the menu. 
2. Right click the Desktop and choose Paste from the menu. 
3. Right click the new icon and choose Properties... from the menu. 
4. In the Target field of the properties dialog append -tracebacks (separated from the path by a space): 
(It will look like this at the end when you're done (leave the rest of the path alone): lightroom.exe" -tracebacks) 
5. In the general tab, you might also want to change the name so you can easily visually distinguish this new icon from the original (we'll delete it when we're done). 
6. Go to this site in your browser: https://docs.microsoft.com/en-us/sysinternals/downloads/debugview
7. On the right hand side of the page, click the "Run DebugView" link (it's safe – it's just a debug output viewer from Microsoft) 
8. Click through the Eula if necessary. 
9. With DebugView running, double click the new icon we created in steps 1-5. 
10. Repeat the steps in Lightroom that cause the error message or hang that you are seeing. 
11. Save the output. You can either highlight and copy/paste or choose "Save as..." from the menu to save the output to a file.
 
Mac 
1. In Finder, navigate to the Utilities subfolder of the Applications folder (Command + Shift + U). 
2. Double Click Terminal.app 
3. Paste the following text: '/Applications/Adobe Lightroom 3.app/Contents/MacOS/Adobe Lightroom 3' -tracebacks 
(Note that this may be different for some versions of LR, like RC/Beta releases, etc) 
4. Press enter to start. 
5. Repeat the steps in Lightroom that cause the error message or hang that you are seeing. 
6. Use the Shell -> Export Text As... menu item (Command + S) to save the output to a file (or select it for copy and paste).
 
Note that the output this produces requires the exact build number of LR that emitted it to be translated into a stack trace with source file names and line numbers.

Votes

Translate

Translate

Report

Report
Community Beginner ,
Jun 20, 2019 Jun 20, 2019

Copy link to clipboard

Copied

I have done that now and got the following after only running the app and starting the panoramic:

00000001 0.00000000 [2948] L:
00000002 0.00002120 [2948] expected integer, got 1333.3333333333
00000003 0.00002120 [2948]     0: method   setPreviewLongSide             - C
00000004 0.00002120 [2948]     1: upvalue  ?                              - 1010062699:2900+104
00000005 0.00002120 [2948]     2: upvalue  ?                              - 1010062699:882+5
00000006 0.00002120 [2948]     3: upvalue  ?                              - 1010062699:919+50
00000007 0.00002120 [2948]     4: upvalue  ?                              - 1010062699:891+27
00000008 0.00002120 [2948]     5:          [unnamed]                      - 1010062699:2135+85
00000009 0.00002120 [2948]     6:          [unnamed]                      - 179812414:2024+12
00000010 0.00002120 [2948] ---------------------------------
00000011 0.00003990 [2948] 
00000012 39.41481781 [12140] PPLE [Informational] LIFECYCLE: OnResuming
00000013 49.17985535 [12140] PPLE [Informational] LIFECYCLE: OnSuspending
00000014 58.96399307 [14632] Shutting down daemon

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Jun 20, 2019 Jun 20, 2019

Copy link to clipboard

Copied

Thanks, that's a pretty solid lead on what causes the 'hang'. Now to try and figure out how we got into that situation 🙂

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Jun 20, 2019 Jun 20, 2019

Copy link to clipboard

Copied

What do your display settings look like?

Mine look like this:

RackMultipart2019062025308wjrn-86138104-60a2-49b4-b3d4-4b49dd4bf238-1929734757.png

Votes

Translate

Translate

Report

Report
Community Beginner ,
Jun 20, 2019 Jun 20, 2019

Copy link to clipboard

Copied

Here are my display settings, I'm using a Dell 4K (3840 x 2160) display with 130% custom scaling.

RackMultipart2019062086311t81v-f729f981-c8e8-449a-99bf-dcd09b2185bf-337151259.png

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Jun 20, 2019 Jun 20, 2019

Copy link to clipboard

Copied

I suspect your custom scale factor triggers the problem. Trying to see if I can get it to happen here.

Votes

Translate

Translate

Report

Report