Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
0

Merge to HDR simply doesn't work most of the time.

Participant ,
Oct 21, 2017 Oct 21, 2017

On a regular basis, I merge 5 bracketed shots from my drone.  In the older LR, this operation took about 1 minute or less.  I could "batch" 5 operations at a time and have them all done in about 3 minutes or less.

With the newer, faster, more awesome (and likely soon-to-be-deprecated) LR, it simply won't do anything.  I was lucky and had one HDR to work, but I've tried countless others (one for nearly two hours) and nothing happens.  The progress bar makes no progress.

I'm really worried that this important feature is simply victim of a bug.

Anyone else having issues?  Adobe, what's up with this??

111.jpg

Help?

909
Translate
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

LEGEND , Oct 22, 2017 Oct 22, 2017

A number of people have posted about very slow or stalled merges.  Please post a bug report in the official Adobe feedback forum: Lightroom Classic CC | Photoshop Family Customer Community . Adobe product developers don't participate in this forum.  By aggregating all the reports in one bug report, Adobe is more likely to notice sooner and fix it sooner.

Translate
Community Expert ,
Oct 22, 2017 Oct 22, 2017

Have you restarted Lightroom? (and the computer?)

I had the same symptoms with first use of Lr-Classic. A restart got it working- fast!!

Regards. My System: Windows-11, Lightroom-Classic 14.5.1, Photoshop 26.10, ACR 17.5, Lightroom 8.5, Lr-iOS 10.4.0, Bridge 15.1.1 .
Translate
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
Community Expert ,
Oct 22, 2017 Oct 22, 2017

I understand that there's an enhancement to the way that stacked HDR/Merges are managed with respect to CPU usage globally within the computer, i.e. the merge queues are held until CPU usage drops below a certain percentage (and no, I don't know what that figures is). But if you system is generally busy and the CPU usage is above that threshold, then the HDR merges will not run.

That might explain why wobertc​ saw his working after a restart when presumably his system wasn't initially so busy.

If that is the problem, it would perhaps be more practical to let the user set the threshold. That suggestion has already been made to Adobe.

Translate
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
Participant ,
Oct 22, 2017 Oct 22, 2017

Abambo , wobertc​, JimWilde​ - Yeah, I've rebooted a few times -- no change.  HDR just sits there and does nothing.  This was never a problem before.  Grrr

Translate
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
LEGEND ,
Oct 22, 2017 Oct 22, 2017
LATEST

A number of people have posted about very slow or stalled merges.  Please post a bug report in the official Adobe feedback forum: Lightroom Classic CC | Photoshop Family Customer Community . Adobe product developers don't participate in this forum.  By aggregating all the reports in one bug report, Adobe is more likely to notice sooner and fix it sooner.

Translate
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
Community Expert ,
Oct 22, 2017 Oct 22, 2017

I’ve done since Lr Classic CC quite a bunch of HDR files and they all went smoth and fast. I even could launch more then 13 HDR calculations at a time and contrary to Lr CC.2015 I did not have a blocking situation.

I suppose you have a configuration/local machine problem. Kind of scratch disk full or similar.

ABAMBO | Hard- and Software Engineer | Photographer
Translate
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