Luminous Landscape Forum

Raw & Post Processing, Printing => Adobe Lightroom Q&A => Topic started by: Robert-Peter Westphal on April 06, 2016, 02:55:34 am

Title: cannot process files straight from a stack
Post by: Robert-Peter Westphal on April 06, 2016, 02:55:34 am

Hallo,

I'm experiencing a strange problem with Lr CC latest version on Windows 10.
When I try to create an HDR or panorama from a set of pictures which are stacked, I'll receive an unknown error from the HDR or panorama module. When I open the stack and select all of it's members, it will be fine and the HDR / panorama is produced well.

I remember that with one of the former versions of Lr it was ok to select just the stack and then create the HDR or pano. Does anyone else have the same issue ?

In Germany we have a saying : They build up anything with their hands and than they crash it with their butt'

Best wishes Robert

Title: Re: campt process files straight from a staple
Post by: stingray on April 06, 2016, 12:33:10 pm

Quote

it was ok to select just the staple

I presume you mean "Stack".

Title: Re: campt process files straight from a staple
Post by: Robert-Peter Westphal on April 06, 2016, 02:08:59 pm

Quote from: stingray on April 06, 2016, 12:33:10 pm

I presume you mean "Stack".

Sorry - you are surely right, I mean for sure mean stack.

Thanks for the info !

Robert

Title: Re: cannot process files straight from a stack
Post by: Paul2660 on April 06, 2016, 02:57:45 pm

Anything like this error?

http://forum.luminous-landscape.com/index.php?topic=108748.0

Hopefully will be fixed in the next release maybe.

Paul C

Title: Re: cannot process files straight from a stack
Post by: fdisilvestro on April 06, 2016, 03:45:10 pm

It does not look as the same error as the warning of the resulting file damaged.

This issue will not even let you create the HDR or Panorama from stacked images. I cannot tell if this worked with previous 6.x versions.

The funny thing is that if you select "Edit -> Merge to HDR Pro in Photoshop" then it works as expected, so it looks definetly as a bug