Skip to main content
Inspiring
October 17, 2018
Answered

New HDR Panorama feature

  • October 17, 2018
  • 8 replies
  • 4917 views

I haven't been able to make this work... yet!

I produce lots of 3 image panoramas from images produces from 24mm TSE II lens (Three shifts of the lens which normally merge perfectly with "merge to panorama")

Many images I shoot would be vertical shifts of architectural interiors, and a bracketed HDR Panorama would be great.

I haven't been able to make this work with any existing images - I get this message... "Unable to detect HDR exposure bracket size. Merge to non-HDR panorama instead?"

All I can think of is that the method I use for bracketing isn't correct for this feature... I normally make 3 same exposures (shift up, middle, down) then change exposure and do same again.

In the Adobe instructional video <Merge to HDR Panorama in Adobe Camera Raw - YouTube> I can see that each image has been bracketed before moving on to the next shift... is this the secret?

BTW I reordered and re numbered images so that they appear to be sequentially bracketed - that didn't work either - perhaps a slight pixel mis-match is the problem???

I am about to do an interiors job today and will try bracketing as per video... but would like a comment from someone in Adobe who might know?

Peter

This topic has been closed for replies.
Correct answer gary_sc

Hi P Moloney & James,

When I say two stops apart, I mean from each shot to the next. That is -2, 0 +2. A total of four stops. Unfortunately while LR and ACR can create an HDR from lower stops, it does balk on HDR-Panos where the stops are less than 2 stops between shots.

Yeah, strange, but that's the way it works (and doesn't work).

Here's the deal: I've been doing HDR for about 12 years and I've made all of the mistakes that just about anyone can make. With that in mind, one of the things that I've always strived for was creating the view so that it looked like what your eye saw, not the limitations of the camera, nor the harsh over-saturated view that was so common some 12 years ago. I look at those and it makes my teeth hurt.

Here's an extra tip: if you are talking jpg images, you do need -2, 0, +2. But, if you are taking raw images, than all you really need is -2, +2. That's it.

and here's a bit of extra information: bunches of years ago I did a test: I took the following stops: -2, -1.5, -1, -.5, 0, +.5, +1, +1.5, +2 and I ran them together in three different ways:

-2, -1.5, -1, -.5, 0, +.5, +1, +1.5, +2

-2, -1, 0, +1, +2

-2, 0, +2

I had the EXACT same settings for each test. At the end there was no discernible difference between any of the settings. Why is this so? It's simple really, Think about a pano. When you shoot a pano with a 50mm lens (think of that 50mm lens as a jpg image), you may need three shots to cover the full range of the image including 1/4 overlap of the image. You could have 1/2 or even 3/4 overlap but it would make NO DIFFERENCE to the final panoramic image. If now you take a 25mm lens (think of this as a raw image), you will probably only need two images to capture the same panoramic image because it's capturing a wider amount of the view. This is just as a raw image captures a greater range of the image's view because most raw images are anywhere from 12-14 bit image as opposed to jpeg's 8 bit image limitation.

Let me know if this makes sense or not and if this helps you solve the problems you've had.

8 replies

Known Participant
November 10, 2018

I have been experiencing the same problem. I'm pretty sure I know what is happening.

Photo Merge -> HDR Panorama does not recognize stacks!

Photo Merge -> HDR does recognize stacks. But if I try to use collapsed stacks, HDR Panorama only selects the top image in each stack.

If I expand the stacks and select each image, HDR Panorama works.

This is clearly a bug.

Rod

Chuck Uebele
Community Expert
Community Expert
October 26, 2018

Just got word that the logic behind determining the exposures has been fixed. Hopefully it will be out in the next release of ACR.

Participating Frequently
October 26, 2018

Hi Chuck

Thanks for info, looking forward to it being available.

Any timeframe ?

Cheers

DaveM

Chuck Uebele
Community Expert
Community Expert
October 26, 2018

No idea when. However updates to ACR come out fairly often due to all the new cameras that need to be incorporated so that PS can read the files.

Chuck Uebele
Community Expert
Community Expert
October 26, 2018

I did find out that the 2 stop difference was not intentional, and might be a bug. You should be able to do the HDR pano with less of a spread. What is critical is that the spread be exactly the same, so using auto bracketing should help eliminate any variance.

Participating Frequently
October 26, 2018

Hi Chuck

I think the testing I did yesterday has covered the "spread myth". I can merge 3 sets at +/-1 and two sets at +/- 0.3. Therefore I don't think trying to merge to HDR Panorama with images taken with AEB less than +/- 2 is the issue that causes the "Unable to detect..." message. But I could be wrong :-(   Or are you saying that it is "guarenteed" to work at +/- 2 and above, but the code is "buggy" with less than +/- 2 ? In which case I refer you back to my first post on 24th Oct where I was having problems with images taken using AEB +/- 2.

To be clear ALL the testing I did yesterday (and in fact with any HDR sets I take out in the field) are with AEB set - its the right tool for the job, besides which trying to do it manually is just too messy in my opinion.

And yes, I agree using AEB should help eliminate any variance.

So.... be a hero and explain why the following three sets won't merge :-)

All taken with constant ISO 100 and constant F4, the only thing changing is the shutter speed via AEB

Set 1 - normal 1/80th, dark 1/100th, light 1/60th

Set 2 - normal 1/80th, dark 1/100th, light 1/60th

Set 3 - normal 1/80th, dark 1/100th, light 1/60th

There does not appear to be much(!) variance there. And yet selecting all 9 shots will get thrown out by ACR with the "Unable to detect HDR bracket size" message.

And yet selecting any two of the three sets will allow ACR to detect the bracket size and start creating the HDR pano - thats just plain nuts.

Logic says ACR is looking at the EXIF data (ISO, Aperture, Shutter speed) to determine the bracket size and if all are constant then proceed .... and yet...

Further logic says if it borks on three identical sets, then it can't be using (just?) EXIF data. So if its not using EXIF, what else is it using to determine bracket size ?

Just trying to figure out what the ACR code logic is here that causes the problem, because once you understand what causes the problem when the three sets are identical, it allows you to figure out what to do when taking HDR panos out in the field with the knowledge that ACR will ALWAYS process them without throwing out the "Unable to detect..." message.

Cheers

DaveM

Chuck Uebele
Community Expert
Community Expert
October 26, 2018

I'm not sure why it doesn't work well when manually set. Perhaps something in the metadata when using auto bracketing. As far as the spread, I just heard that the spread isn't suppose to matter, but for some people it does. I believe Adobe is looking into this. It shouldn't be limited to 2 stops and above.

Participating Frequently
October 24, 2018

I have the same issue in Lightroom cc classic trying to Photo Merge to create an HDR panorama.

I have 12 canon raw images taken with a 30D. I used AEB to take 4 sets of 3 images with 2 stops between each image. I was in Aperture priority mode - so ISO 100 and aperture f8 remain constant - and the only variable was shutter speed. I have named the files 1.1, 1.2, 1.3, 2.1, 2.2 etc where x.1 is the darkest image, x.2 is the normal image and x.3 is the lightest image for each set.

I cannot create an HDR panorama with all 4 sets.

I can create an HDR panorama with the first 3 sets.

I can also create an HDR panorama with sets 3 and 4 ! (and sets 2 & 3 but NOT 2, 3 & 4)

I have checked the shutter speeds of each image within each set and they are definitely 2 stops apart.

However, because aperture  priority was used the shutter speeds used for each set varies. For the darkest images the shutter speeds the camera selected were

1.1 1/1000th

2.1 1/1600th

3.1 1/1000th

4.1 1/800th

So I would take a (wild) guess that Adobe are not only checking the stops between images in a set, they are also checking the stops between sets, with some degree of acceptance, which will allow the sets 1, 2 and 3 to be merged and sets 3 & 4 to be merged, but will not allow selections which include sets 2 & 4 because 1/1600 to 1/800 is deemed to great a spread ?

On the other hand I could be talking a load of nonsense :-)

Would be interested if any body else using Aperture priority (or I guess Shutter priority) has had the same issue.

Would be even more interesting if anybody shooting with manual mode (so all image sets will see the same set of shutter speeds) has been unable to create an HDR Panorama using this photo merge feature.

Thanks

DaveM

P MoloneyAuthor
Inspiring
October 24, 2018

Hi Dave,

I'm just working on a job I shot earlier today...

Two of the images are HDR Panoramas, I shot these using AEB on manual with a 5DsR

3 exposure only -2 0 +2 (this seems to be the only way I can make this work - but it does work)

As it happens the exposures were 0.8sec 1/5 and 1/20

I really don't know how ACR knows what exposure is used other than metadata / exif, but unless you have a two stop gap it won't work!

Thats as much as I know - thanks to gary_sc!!!

Peter

Participating Frequently
October 24, 2018

Hi Peter

So how many sets of 3 exposures are in each panorama ? And to be clear do all sets in each panorama have the same shutter speeds of 0.8 1/5 and 1/20th - with constant aperture and ISO across all shots ? If so, that kind of agrees with my thoughts for it to work.

I guess this can be achieved if light is constant across a panorama - ie room with no windows just constant artificial lighting (or not a problem for windows to be blown out) or a landscape with the sun directly behind you (or a very cloudy day) ?

I had assumed that Adobe must be using metadata/exif as its the only(?) source of info, unless they are doing some subjective analysis of each individual image to work out the overall brightness/darkness and back engineering the relative exposure between shots in a set - which just seems far too complicated given metadata/exif is available :-) 

I will try and do a bit more testing tomorrow to see if I can prove/disprove what does/doesn't work - will let you know if i can get less than 2 stops to work on the 30D (old technology!).

Thanks

DaveM

Randy Hufford
Community Expert
Community Expert
October 20, 2018

Are you using a tripod head to allow for

What is the No Parallex Point?

What is the No Parallex Point? - YouTube

I use a Nodal Ninja Head holding camera in a vertical position using this feature. These images have to many close and far away points for each image to line up. Whats video to understand.

Chuck Uebele
Community Expert
Community Expert
October 19, 2018

It's odd what going on here. I've had some issue with the feature, but it was more due to the number of different views. It stitched a normal pano with the large number, but not with the HDR combined. Gary thinks I had too much overlap, which might have been the case. Will have to try more, but the feature does seem very finicky right now. Hopefully it can be improved.

Just out of curiosity, do you have another camera that you could try it on? just wondering if it might be something with that particular Canon's metadata.

P MoloneyAuthor
Inspiring
October 18, 2018

So... another job today!

Today I bracketed in stops (-1 0 +1) That's two stops between lightest & darkest!

Didn't work....    "Error unable to merge selected images"

Tried with various number of brackets... Didn't work

And.. Just in case there is any doubt about the merging side of things there is a screen shot of a fully merged but not bracketed shot!

Come on Adobe please explain how this should work - and why it doesn't for me?

gary_sc
Community Expert
gary_scCommunity ExpertCorrect answer
Community Expert
October 18, 2018

Hi P Moloney & James,

When I say two stops apart, I mean from each shot to the next. That is -2, 0 +2. A total of four stops. Unfortunately while LR and ACR can create an HDR from lower stops, it does balk on HDR-Panos where the stops are less than 2 stops between shots.

Yeah, strange, but that's the way it works (and doesn't work).

Here's the deal: I've been doing HDR for about 12 years and I've made all of the mistakes that just about anyone can make. With that in mind, one of the things that I've always strived for was creating the view so that it looked like what your eye saw, not the limitations of the camera, nor the harsh over-saturated view that was so common some 12 years ago. I look at those and it makes my teeth hurt.

Here's an extra tip: if you are talking jpg images, you do need -2, 0, +2. But, if you are taking raw images, than all you really need is -2, +2. That's it.

and here's a bit of extra information: bunches of years ago I did a test: I took the following stops: -2, -1.5, -1, -.5, 0, +.5, +1, +1.5, +2 and I ran them together in three different ways:

-2, -1.5, -1, -.5, 0, +.5, +1, +1.5, +2

-2, -1, 0, +1, +2

-2, 0, +2

I had the EXACT same settings for each test. At the end there was no discernible difference between any of the settings. Why is this so? It's simple really, Think about a pano. When you shoot a pano with a 50mm lens (think of that 50mm lens as a jpg image), you may need three shots to cover the full range of the image including 1/4 overlap of the image. You could have 1/2 or even 3/4 overlap but it would make NO DIFFERENCE to the final panoramic image. If now you take a 25mm lens (think of this as a raw image), you will probably only need two images to capture the same panoramic image because it's capturing a wider amount of the view. This is just as a raw image captures a greater range of the image's view because most raw images are anywhere from 12-14 bit image as opposed to jpeg's 8 bit image limitation.

Let me know if this makes sense or not and if this helps you solve the problems you've had.

P MoloneyAuthor
Inspiring
October 18, 2018

Hi Gary,

Thanks for this - a great deal of information here. I will indeed try the +2 0 -2 option tomorrow along with a trial of +2 -2 and I'll report back.

I note that none of the information you have supplied seems to be available anywhere else.

Until tomorrow!

Peter

gary_sc
Community Expert
Community Expert
October 17, 2018

Yes, it is MUCH MUCH better to take your three shot then move- repeat.

Also, be sure each shot is two stops between shots.

Let it us know if this works

jamesl29291690
Participant
October 17, 2018

It didn't for me. I am getting the same message. I was taking each shot with a 3 frame 2 stop bracket. If I just to a regular HDR with one bracketed image, no problem, but as soon as I add a second bracketed image, it's a no go. Too bad, I was looking forward to trying this new feature.

gary_sc
Community Expert
Community Expert
October 17, 2018

Hi James,

just out out of curiosity, what is your process?

You state that you take three shots for each image at two stops each but when you do your panorama actions, how much overlap do you maintain? I try for about 1/3 - 1/4 of each image overlaps the previous image. Also, if you‘re doing a beach area over looking water it’s almost impossible for any application to stitch things together when there’s nothing to link the images together.

Dies this help?