Merge to HDR Pro: Result different than preview

Hi all,
at the moment I use Photomatix 3 Pro to create HDR images, but since Photoshop CS5 offers this functionality too, I wanted to try it out.
I selected my three differently exposed images in Mini Bridge and loaded them into Photoshop via "Merge to HDR Pro...". The preview window opened and I could adjust the settings, so far so good. I adjusted the settings until the preview image met my expectations and pressed OK, but the result looked pretty different to the preview image. Especially the saturation was way too high. Converting the photos to JPEG first or using the raw files makes practically no difference.
I followed a video tutorial, but there the preview and the result matched almost exactly.
In a different thread I read about a similar problem, but the only solution given there was checking the 32-bit view options. I am using the 8- or 16-bit mode only, so that wasn't helpful for me.
I hope someone can help me, otherwise I have to stick to Photomatix.
Two pictures to illustrate my problem (this is the german version of Photoshop, click on the image to see the original size):
This is how the preview looked right bevore clicking OK:
And this is how the generated image looked afterwards:

I can only guess you have some kind of color-management problem on your system, as I just did a test and didn't see any differences between the preview display in the Merge to HDR Pro dialog and the final result.
What color profile are you using for your input images?
Is it the same as your default working profile?
I shouldn't think it would matter what profiles you're using - Photoshop should handle them all properly - but clearly something's causing your saturation to be massively different, which is the kind of thing you might see if a narrow gamut image is being interpreted as though it has a wide gamut color profile (or displayed without color management on a wide gamut monitor). I do know that HDR processing converts images to your default working profile under some conditions.
Another possibility is that the display of the image in the HDR Pro dialog is misinterpreting (or neglecting to use) the image color profile.
That's a very pretty sunset shot, by the way.
-Noel

Similar Messages

There is no Merge to HDR Pro result

I tried to create a HDR photo, selected the input files and PS CS6 Extended did the task. However there was no output file/window.
I have no clue why the output lost. The only thing is I just changed the mainboard & cpu and Adobe asked me for the serial which I entered again.

I can only guess you have some kind of color-management problem on your system, as I just did a test and didn't see any differences between the preview display in the Merge to HDR Pro dialog and the final result.
What color profile are you using for your input images?
Is it the same as your default working profile?
I shouldn't think it would matter what profiles you're using - Photoshop should handle them all properly - but clearly something's causing your saturation to be massively different, which is the kind of thing you might see if a narrow gamut image is being interpreted as though it has a wide gamut color profile (or displayed without color management on a wide gamut monitor). I do know that HDR processing converts images to your default working profile under some conditions.
Another possibility is that the display of the image in the HDR Pro dialog is misinterpreting (or neglecting to use) the image color profile.
That's a very pretty sunset shot, by the way.
-Noel

Merge to HDR Pro preview and final result very different

I'm using CS5 and beginning to use HDR. When I merge to HDR pro and make adjustments to images the preview window is extremely different from the final image. I'm merging original camera raw images from a Nikon D200. Workflow in ACR is set to 16bit. Output from HDR pro is also 16bit. I adjust using the preview window, but after final processing the resulting image is grossly different, much more saturated and more vibrant among other differences.
Any clues about what I'm doing wrong?
Bob

After writing my comment here, I found something elsewhere on the forum that suggested that the problem was that color profile of the input files and the workspace in Photoshop are different. I found that to be true in my case. The RAW files in Lightroom 4 are probably being converted to TIFFs as they are sent to Merge to HDR Pro. In any case, they are being sent with the same color profile they had in Lightroom, which in my case is is ProPhoto RGB. When HDR Pro sends its results to Photoshop, it converts the output to the same color space that Photoshop is set to. I have Photoshop set to sRGB, because that is what most monitors and printers use, and I do my final work in Photoshop. As a result, I was seeing something quite different in Photoshop than what I say in HDR Pro. I found two ways to deal with this. First, set the color profile in Photoshop to be the same as the input files, or Lightroom if that is where they come from. The second method is to bring the files into Photoshop as TIFFs and convert them to the working color space that Photoshop uses and then from the File menu choose Automate and from the menu that pops up, choose Merge to HDR Pro. I have had good results using both methods.

LR3 - Questions regarding virtual copies with different exposures and Merge to HDR Pro in Photoshop

Hello,
I'm currently testing LR3. I have a master copy and 4 virtual copies with different exposures selected in LR3. I tought to myself that I could simply use the "Edit / In Merge to HDR Pro in Photoshop" option and tune the resulting HDR image in Photoshop but it seems that Photoshop doesn't take in consideration the exposure changes I've made on the virtual copies in LR3. The 5 images are identifical in the HDR Pro tool.
Is there something I can do to about it ? Maybe there is a step I've forgot in my workflow or something ?
Maybe I could simply export the master and virtual copies to JPEGs and then import these in the Photoshop HDR Pro tool but I don't think I would get the same results right ?
Thank you for your help.

Depending on the image ISO and overall content, you can get some pleasing DR pickup using this routine over simply hitting the fill light slider up and the exposure slider down. I never really liked the PS approach since it seemed to require too much tweaking inside PS. I have experimented with LR/Enfuse and Photomatix plug-ins and have settled on Photomatix for my HDR exposures (both "real" with multiple images and "fake" with a single image as you have described). I think LR/Enfuse is donation ware so you might want to start there. In both cases, the resultant image still needs a little adjusting back in LR after it is automatically imported into the Library.
Jeff

Merge to HDR pro is producing very washed out results. Resulting images look terrible and bleached.

I posted here before, but was directed to go through the help menu in Photoshop, which brought me back here!! Please Help Me!
Merge to HDR pro is producing very "bleached" and overexposed images.
Thank you,
Rob

Thank you for the reply, Ed. I've delved into the PS preferences as best I could but did not see anything related to this issue. I have ACR set to convert at 240 dpi with ProPhoto color space and have never encountered this problem under typical 16 bit conversions from RAW to psd. For some reason PS sets the document size of 32 bit images to 3.5' x 5' @ 72 dpi which results in an extra step to the already time consuming workflow when creating such images in PS.
Perhaps this is an issue Adobe can address in a future update? They did a good job addressing other issues such as the disappearing RGB data in the info pallette when adjusting images with curves. It appears that the Windows version of PS has too many non-fatal (but annoying) flaws that aren't present in the Mac version.

Bridge to PhotoshopCC merge to HDR Pro is failing

This seems to have occurred since the latest update had corrupted my CC and I needed to uninstall and reinstall all of my apps. This has been a very frustrating bit of work trying to get everything working again. Currently when I try to merge to HDR Pro in bridge (Camera raw) with three bracketed photos it starts and gets to the point where the HDR load screen would come up, but it just gives me a blank photoshop screen. Any suggestions?

I am looking forward to an anwer concerning the HDR preview-result-difference as well... Since some posts suggest to check out the color profile of the input files, i did so: they are both sRGB. And the immense change of saturation and brightness (in other examples even worse than below) couldn't be explained by a different profile anyway, IMHO.
working parameters:
Adobe Brigde CS6 (Tools/Photoshop/HDR PRO)
Adobe Photoshop CS6
sRGB both input and output...

IMovie video result different than original.

I purchased the app iMovie as I had 2 videos that I took with my iPad4, iOS7.0.4 and I wanted to combine them into 1 video. After I did this the resulting video looked as if I had taken it from a greater distance than the original videos in my camera roll. I took my videos with my iPad of my computer monitor screen. The resulting video after combining them showed the whole monitor with space around it. I just wanted the resulting video to have the same look as my original videos in my camera roll viewer. Any suggestions on how I can acheive this? Thank you.....

I can only guess you have some kind of color-management problem on your system, as I just did a test and didn't see any differences between the preview display in the Merge to HDR Pro dialog and the final result.
What color profile are you using for your input images?
Is it the same as your default working profile?
I shouldn't think it would matter what profiles you're using - Photoshop should handle them all properly - but clearly something's causing your saturation to be massively different, which is the kind of thing you might see if a narrow gamut image is being interpreted as though it has a wide gamut color profile (or displayed without color management on a wide gamut monitor). I do know that HDR processing converts images to your default working profile under some conditions.
Another possibility is that the display of the image in the HDR Pro dialog is misinterpreting (or neglecting to use) the image color profile.
That's a very pretty sunset shot, by the way.
-Noel

Color change after merging to HDR Pro, going back into Lightroom

I recently updated Lightroom and now when I "merge to HDR Pro in PS" the photo then comes back into lightroom with highly elevated contrast. I have set the color options to ProPhotoRGB in Lightroom and Photoshop. and the image looks fine when going from LR to PS, and it looks fine in "preview" after saving the image as a TIFF. But once that TIFF gets imported back into LR it has all those weird color changes. I'm not sure what to do, and I never had this problem until I recently updated photoshop and lightroom. Any help you would be appreciated. thanks!

The image will look different in PS than in LR. PS uses the embedded preview and LR uses the actual 32 bit image data. You need to apply the LR Develop module Basic panel Tone settings to the 32 bit HDR TIFF.

Uncaught Javascript Exception during create file phase of Merge to HDR Pro.

Provide a descriptive title that includes your OS information:
I am trying to create an HDR file from several large merged panoramas, and everything seems to go very well whichever options I select until the point comes when photoshop tries to create the final file. The individual layers of the HDR are 40188x6848 and saved as PSB files, when loaded they fill the entire 8Gb of memory in my machine.
I am using Windows Vista 64, my graphics card is unsupported and so turned off, I have photoshop setup to use 3 scratch disks, and it appears to be using around 40Gb on the first one and none on others.
Provide concise, step-by-step details on how to reproduce the issue you are seeing.
Select File > Automate > Merge to HDR Pro
Select the 5 HDR layer files, check attempt to automatically align layers
Make a cup of tea, you're in for a wait.
Set the EV levels of the files
Select any options you want from the next panel, I've tried most of them by now.
Sit back and wait for the following screen:
Provide a description of the "Expected Result":
Photoshop should have brought up a file containing the merged images, which I could then save to disk.
Provide your System Info from Photoshop:
Adobe Photoshop Version: 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00) x64
Operating System: Windows Vista 64-bit
Version: 6.0 Service Pack 2
System architecture: AMD CPU Family:15, Model:15, Stepping:2 with MMX, SSE Integer, SSE FP, SSE2, SSE3
Physical processor count: 1
Processor speed: 1808 MHz
Built-in memory: 8062 MB
Free memory: 1083 MB
Memory available to Photoshop: 7149 MB
Memory used by Photoshop: 72 %
Image tile size: 132K
Image cache levels: 4
OpenGL Drawing: Disabled.
OpenGL Drawing Mode: Basic
OpenGL Allow Normal Mode: False.
OpenGL Allow Advanced Mode: False.
OpenGL Allow Old GPUs: Not Detected.
Video Card Vendor: NVIDIA Corporation
Video Card Renderer: GeForce 6150SE nForce 430/PCI/SSE2
Display: 1
Display Bounds:= top: 0, left: 0, bottom: 1024, right: 1280
Video Card Number: 1
Video Card: NVIDIA GeForce 6150SE nForce 430
OpenCL Unavailable
Driver Version: 8.17.12.7533
Driver Date: 20110521050100.000000-000
Video Card Driver: nvd3dumx.dll,nvd3dum
Video Mode: 1280 x 1024 x 4294967296 colors
Video Card Caption: NVIDIA GeForce 6150SE nForce 430
Video Card Memory: 128 MB
Video Rect Texture Size: 4096
Serial number: Tryout Version
Application folder: C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\
Temporary file path: C:\Users\MARTIN~1\AppData\Local\Temp\
Photoshop scratch has async I/O enabled
Scratch volume(s):
H:\, 279.5G, 57.9G free
D:\, 149.0G, 121.9G free
E:\, 74.5G, 13.9G free
Required Plug-ins folder: C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\Required\
Primary Plug-ins folder: C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\Plug-ins\
Additional Plug-ins folder: not set
Installed components:
   A3DLIBS.dll   A3DLIB Dynamic Link Library   9.2.0.112
   ACE.dll   ACE 2012/01/18-15:07:40   66.492997   66.492997
   adbeape.dll   Adobe APE 2012/01/25-10:04:55   66.1025012   66.1025012
   AdobeLinguistic.dll   Adobe Linguisitc Library   6.0.0
   AdobeOwl.dll   Adobe Owl 2012/02/09-16:00:02   4.0.93   66.496052
   AdobePDFL.dll   PDFL 2011/12/12-16:12:37   66.419471   66.419471
   AdobePIP.dll   Adobe Product Improvement Program   6.0.0.1642
   AdobeXMP.dll   Adobe XMP Core 2012/02/06-14:56:27   66.145661   66.145661
   AdobeXMPFiles.dll   Adobe XMP Files 2012/02/06-14:56:27   66.145661   66.145661
   AdobeXMPScript.dll   Adobe XMP Script 2012/02/06-14:56:27   66.145661   66.145661
   adobe_caps.dll   Adobe CAPS   5,0,10,0
   AGM.dll   AGM 2012/01/18-15:07:40   66.492997   66.492997
   ahclient.dll    AdobeHelp Dynamic Link Library   1,7,0,56
   aif_core.dll   AIF   3.0   62.490293
   aif_ocl.dll   AIF   3.0   62.490293
   aif_ogl.dll   AIF   3.0   62.490293
   amtlib.dll   AMTLib (64 Bit)   6.0.0.75 (BuildVersion: 6.0; BuildDate: Mon Jan 16 2012 18:00:00)   1.000000
   ARE.dll   ARE 2012/01/18-15:07:40   66.492997   66.492997
   AXE8SharedExpat.dll   AXE8SharedExpat 2011/12/16-15:10:49   66.26830   66.26830
   AXEDOMCore.dll   AXEDOMCore 2011/12/16-15:10:49   66.26830   66.26830
   Bib.dll   BIB 2012/01/18-15:07:40   66.492997   66.492997
   BIBUtils.dll   BIBUtils 2012/01/18-15:07:40   66.492997   66.492997
   boost_date_time.dll   DVA Product   6.0.0
   boost_signals.dll   DVA Product   6.0.0
   boost_system.dll   DVA Product   6.0.0
   boost_threads.dll   DVA Product   6.0.0
   cg.dll   NVIDIA Cg Runtime   3.0.00007
   cgGL.dll   NVIDIA Cg Runtime   3.0.00007
   CIT.dll   Adobe CIT   2.0.5.19287   2.0.5.19287
   CoolType.dll   CoolType 2012/01/18-15:07:40   66.492997   66.492997
   data_flow.dll   AIF   3.0   62.490293
   dvaaudiodevice.dll   DVA Product   6.0.0
   dvacore.dll   DVA Product   6.0.0
   dvamarshal.dll   DVA Product   6.0.0
   dvamediatypes.dll   DVA Product   6.0.0
   dvaplayer.dll   DVA Product   6.0.0
   dvatransport.dll   DVA Product   6.0.0
   dvaunittesting.dll   DVA Product   6.0.0
   dynamiclink.dll   DVA Product   6.0.0
   ExtendScript.dll   ExtendScript 2011/12/14-15:08:46   66.490082   66.490082
   FileInfo.dll   Adobe XMP FileInfo 2012/01/17-15:11:19   66.145433   66.145433
   filter_graph.dll   AIF   3.0   62.490293
   hydra_filters.dll   AIF   3.0   62.490293
   icucnv40.dll   International Components for Unicode 2011/11/15-16:30:22    Build gtlib_3.0.16615
   icudt40.dll   International Components for Unicode 2011/11/15-16:30:22    Build gtlib_3.0.16615
   image_compiler.dll   AIF   3.0   62.490293
   image_flow.dll   AIF   3.0   62.490293
   image_runtime.dll   AIF   3.0   62.490293
   JP2KLib.dll   JP2KLib 2011/12/12-16:12:37   66.236923   66.236923
   libifcoremd.dll   Intel(r) Visual Fortran Compiler   10.0 (Update A)
   libmmd.dll   Intel(r) C Compiler, Intel(r) C++ Compiler, Intel(r) Fortran Compiler   10.0
   LogSession.dll   LogSession   2.1.2.1640
   mediacoreif.dll   DVA Product   6.0.0
   MPS.dll   MPS 2012/02/03-10:33:13   66.495174   66.495174
   msvcm80.dll   Microsoft® Visual Studio® 2005   8.00.50727.6195
   msvcm90.dll   Microsoft® Visual Studio® 2008   9.00.30729.1
   msvcp100.dll   Microsoft® Visual Studio® 2010   10.00.40219.1
   msvcp80.dll   Microsoft® Visual Studio® 2005   8.00.50727.6195
   msvcp90.dll   Microsoft® Visual Studio® 2008   9.00.30729.1
   msvcr100.dll   Microsoft® Visual Studio® 2010   10.00.40219.1
   msvcr80.dll   Microsoft® Visual Studio® 2005   8.00.50727.6195
   msvcr90.dll   Microsoft® Visual Studio® 2008   9.00.30729.1
   pdfsettings.dll   Adobe PDFSettings   1.04
   Photoshop.dll   Adobe Photoshop CS6   CS6
   Plugin.dll   Adobe Photoshop CS6   CS6
   PlugPlug.dll   Adobe(R) CSXS PlugPlug Standard Dll (64 bit)   3.0.0.383
   PSArt.dll   Adobe Photoshop CS6   CS6
   PSViews.dll   Adobe Photoshop CS6   CS6
   SCCore.dll   ScCore 2011/12/14-15:08:46   66.490082   66.490082
   ScriptUIFlex.dll   ScriptUIFlex 2011/12/14-15:08:46   66.490082   66.490082
   tbb.dll   Intel(R) Threading Building Blocks for Windows   3, 0, 2010, 0406
   tbbmalloc.dll   Intel(R) Threading Building Blocks for Windows   3, 0, 2010, 0406
   TfFontMgr.dll   FontMgr   9.3.0.113
   TfKernel.dll   Kernel   9.3.0.113
   TFKGEOM.dll   Kernel Geom   9.3.0.113
   TFUGEOM.dll   Adobe, UGeom©   9.3.0.113
   updaternotifications.dll   Adobe Updater Notifications Library   6.0.0.24 (BuildVersion: 1.0; BuildDate: BUILDDATETIME)   6.0.0.24
   WRServices.dll   WRServices Friday January 27 2012 13:22:12   Build 0.17112   0.17112
   wu3d.dll   U3D Writer   9.3.0.113
Required plug-ins:
   3D Studio 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Accented Edges 13.0
   Adaptive Wide Angle 13.0
   ADM 3.11x01
   Angled Strokes 13.0
   Average 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Bas Relief 13.0
   BMP 13.0
   Camera Raw 7.0
   Chalk & Charcoal 13.0
   Charcoal 13.0
   Chrome 13.0
   Cineon 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Clouds 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Collada 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Color Halftone 13.0
   Colored Pencil 13.0
   CompuServe GIF 13.0
   Conté Crayon 13.0
   Craquelure 13.0
   Crop and Straighten Photos 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Crop and Straighten Photos Filter 13.0
   Crosshatch 13.0
   Crystallize 13.0
   Cutout 13.0
   Dark Strokes 13.0
   De-Interlace 13.0
   Dicom 13.0
   Difference Clouds 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Diffuse Glow 13.0
   Displace 13.0
   Dry Brush 13.0
   Eazel Acquire 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Embed Watermark 4.0
   Entropy 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Extrude 13.0
   FastCore Routines 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Fibers 13.0
   Film Grain 13.0
   Filter Gallery 13.0
   Flash 3D 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Fresco 13.0
   Glass 13.0
   Glowing Edges 13.0
   Google Earth 4 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Grain 13.0
   Graphic Pen 13.0
   Halftone Pattern 13.0
   HDRMergeUI 13.0
   IFF Format 13.0
   Ink Outlines 13.0
   JPEG 2000 13.0
   Kurtosis 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Lens Blur 13.0
   Lens Correction 13.0
   Lens Flare 13.0
   Liquify 13.0
   Matlab Operation 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Maximum 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Mean 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Measurement Core 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Median 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Mezzotint 13.0
   Minimum 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   MMXCore Routines 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Mosaic Tiles 13.0
   Multiprocessor Support 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Neon Glow 13.0
   Note Paper 13.0
   NTSC Colors 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Ocean Ripple 13.0
   Oil Paint 13.0
   OpenEXR 13.0
   Paint Daubs 13.0
   Palette Knife 13.0
   Patchwork 13.0
   Paths to Illustrator 13.0
   PCX 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Photocopy 13.0
   Photoshop 3D Engine 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Picture Package Filter 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Pinch 13.0
   Pixar 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Plaster 13.0
   Plastic Wrap 13.0
   PNG 13.0
   Pointillize 13.0
   Polar Coordinates 13.0
   Portable Bit Map 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Poster Edges 13.0
   Radial Blur 13.0
   Radiance 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Range 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Read Watermark 4.0
   Reticulation 13.0
   Ripple 13.0
   Rough Pastels 13.0
   Save for Web 13.0
   ScriptingSupport 13.0
   Shear 13.0
   Skewness 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Smart Blur 13.0
   Smudge Stick 13.0
   Solarize 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Spatter 13.0
   Spherize 13.0
   Sponge 13.0
   Sprayed Strokes 13.0
   Stained Glass 13.0
   Stamp 13.0
   Standard Deviation 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Sumi-e 13.0
   Summation 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Targa 13.0
   Texturizer 13.0
   Tiles 13.0
   Torn Edges 13.0
   Twirl 13.0
   U3D 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Underpainting 13.0
   Vanishing Point 13.0
   Variance 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Variations 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Water Paper 13.0
   Watercolor 13.0
   Wave 13.0
   Wavefront|OBJ 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   WIA Support 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Wind 13.0
   Wireless Bitmap 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   ZigZag 13.0
Optional and third party plug-ins: NONE
Plug-ins that failed to load: NONE
Flash:
   Mini Bridge
   Kuler
Installed TWAIN devices: NONE
If anyone wants the source images let me know and I'll upload them somewhere, though that process will take a couple of days because they're not small.

Hi Martin,
Per my private message, the "uncaught JavaScript" exception is something we've seen and have yet to determine a cause or solution.
Would you please try the following.
• Do you have following Preferences > Interface settings ON? If they're OFF, does it work if you turn them on?
   - Open Documents as Tabs
   - Enable Floating Document Window Docking
• Does Merge to HDR work for you at all with smaller files (such as those in the sample set inside the application folder for CS5)?
• Do other scripts work for you, specifically...
   - File > Scripts > Load Files into Stack... ?
   - File > Automate > Photomerge...?
• Have you tried restarting with deleted preferences? http://help.adobe.com/en_US/photoshop/cs/using/WSfd1234e1c4b69f30ea53e41001031ab64-74aaa.h tml
The HDR screen image preview going black is a known issue related to low-system memory conditions that we have been working on a solution for.
In the meantime, the workaround would be to lower Photoshop's memory usage from your current (72%) down to as low as (50%).
Purging memory may help: http://help.adobe.com/en_US/photoshop/cs/using/WSfd1234e1c4b69f30ea53e41001031ab64-748aa.h tml
What was the "entirely new error message"? And is the Uncaught Exception the "standard" message?
Thank,
Meredith

Merge to HDR Pro - how to make it work?

The 'Automate -> Merge to HDR' feature worked fine during the first few weeks of my Ps CS5 trial but now doesn't work. Photoshop gets through the Merge to HDR Pro dialog but throws the attached error when returning to Ps.
If Merge to HDR Pro is chosen on DNG images from Lightroom 2.7 or Bridge CS5, Photoshop again gets through the Merge to HDR Pro dialog but when creating the HDR image and returning to Ps seems to throw it away with no resulting error. Photoshop just stares blankly with no image open.
I experienced the same error with CS4 and was excited when the Merge to HDR Pro feature on my CS5 trial worked fine, yet with 5 days left in the trial the HDR feature now refuses to cooperate. It previously was working OK from the Automate menu, from Lr 2.7, and from Bridge. What exactly I did to upset Photohop is a mystery.
I've tried resetting preferences and removing all plugins and extenstions to no avail. Any ideas on how to make Merge to HDR Pro functional?

There has been a long and continuous thread regarding CS5 having problems when one tries to save images that have been combined in Merge to HDR Pro. I have exactly the same problem. I have been shooting 3 images bracketed -1, 0, +1 or -2, 0, +2. When I select 3 images in Bridge. Go to Tools>Ph otoshop>Merge to HDR Pro the computer does its work and produces an image of a combination of the 3. I can see the image, and in the Layers Panel I see 3 Layers plus one Layer that is entitled Merge to HDR Pro(layer is devoid of image. When I try to Save As Photoshop freezes up. I have 11 Screenshots to illustrate. Also Select 3 in BridgeI have tried many different sets of images. Screenshots:Select 3 images in Bridge CS5Go to Tools>Photoshop>Merge to HDR ProSave as 32 bit image; have tried 16 bit and 8 bit too- still freezes at endSave as BEF 32 bitSaving -Computer is Processing32 bit image saved on screenSave as bef to proper locationPutting in File TitleSelecting 1PHOTOSHOP FROZEN- anything I click on no responsePhotoshop Running but not responding- Frozen; Task Manager says all running here, but no responseHave to end process with task manager. Thanks, Sam

Setting a fixed and consistent exposure level with merge to HDR Pro?

I do panoramas with sets of bracketed HDR images. From LR I select my stack and then merge to HDR pro in CC. CC then produces a screen with a white point preview slider or the option to tone in ACR. Since I want to tone in LR I have tried to set the white point consistently for each HDR output in the panorama set, but I cannot get consistent exposure levels. I then try to adjust them all the same in LR, but sometimes differences result in undesirable effects in the panorama stitched output.
How can I get a 32bit HDR from PS CC back to LR and have each stack come back in with exactly the same exposure without me trying to guess with a slider?
I task all the images for the panorama with identical settings. Same brackets, fstop , shutter speed, ISO, etc. I should be able to get them all processed into 32bit HDRs and looking the same without manual adjustment guesses.
Thanks.

I'll tell you my workflow for panoramas such as this. Starting from bracketed stacks of images.
1. I select all images, go into Develop and turn on auto-sync. Turn on "Remove Chromatic Aberration". Do not turn on "Enable Profile Corrections". Set a custom white balance to make sure all images are WB'ed the same and optimize sharpening and noise reduction. Basically you want all images to be developed exactly the same and fairly conservative at that.
2. Export all images to 16-bit tiff in prophotoRGB or adobeRGB (depending on how colorful they are)
3. At this point one can add a logo to the nadir shot or do it at the end using the workflow I described above.
4. Load all images into hugin. Generate control points. Optimize positions - first just positions, then positions and view. Level the panorama in the GL preview and make sure the projection is set to equirectangular and the view to 360x180, then optimize view, barrel and positions and finally "everything without translation". During all these steps remove errant control points by going into the control point list and deleting the ones with the largest deviation, which are usually bad control points on clouds or other moving things. Also make sure the pano stays correctly leveled.
5. Mask the tripod out of the images that have it in them using the mask tools in hugin. Mask feet and stuff out of the nadir shot.
6. Do a photometric optimization with high dynamic range, fixed exposure.
7. Go to stitcher, set the optimum canvas size, uncheck "exposure corrected, low dynamic range", Check A. "exposure fused from any arrangement", B. "High dynamic range->tiff", or C. "blended layers of similar exposure, without exposure correction" depending on what you want to do.
8. Stitch
If you did A. You will get a tone mapped image that you can work up further in Lightroom or Photoshop. That image will be tone mapped respecting the wraparound on all sides so it won't have weird seams in a spherical projection. If you did B. you get a 32-bit tiff that will work great in Lightroom and as long as you don't use highlights, shadows, clarity and such will remain good. If you did C. you can load the multiple panorama layers you get into a HDR Pro in Photoshop, and load that into Lightroom.

Auto-align Layers and Merge to HDR Pro crashes

Hi,
Has anybody else experienced crashes with Merge to HDR Pro or Auto-align Layers? I was trying to use Merge to HDR Pro from Lightroom and was experiencing crashes every time after it had opened all of the images and merged them into a single document (but before the HDR Pro dialog box had come up).
I've tested this further with opening each image individually and then trying to merge them as well as via Bridge and always get the same result.
I had then decided to try layering the images and blend them to create my HDR image and that's when I found that Auto-align Layers was crashing as well. This leads me to believe that it's actually the auto-align functionality that's causing the crash rather than Merge to HDR Pro as I'm pretty sure that the merge functionality performs an auto-align as part of its steps.
Any suggestions on how to fix this? I'm wondering if I may have to completely remove Photoshop. I can do this if necessary but if there's some other way to fix this I'd rather try that first.

Okay, solved my own problem. I bit the bullet and did do a reinstall. I'd remembered that one of the previous Photoshop upgrades had failed (either 12.0.1 or 12.0.2) and I'd never gotten around to fixing it. Looking into that suggested reinstalling as the solution so I figured I should try uninstalling and reinstalling then apply all the upgrades and then try it again.
This time the upgrades did go through properly and I was just able to do a merge to HDR pro successfully so it looks like that's fixed the issue.

Merge to HDR pro is producing very "bleached" and overexposed images.

I don't know why this isn't working, but every single time I attempt to use merge to HDR pro, the result is an ugly bleached out photo, and editing in raw does nothing to help. I have tried using TIFFs, Jpegs, RAW files (all at different exposures from very dark to very light, to capture the entire range, usually 5 separate images), but whenever I select File>>Automate>>merge to HDR Pro, and select the files to use, the result is always really horrible.
Why isn't this working for me? Here's a typical result:
Please, any suggestions. The reason I bought photosop was for the HDR capability, and compatibility with lightroom. Honestly I get better results just blending images using GIMP, or just processing a single RAW file in Lightroom.
It will also sometime go through its process of aligning the pictures and thinking for a few minutes, then just leave me with a blank dark gray workspace, without opning the HDR pro window after working with the images.
Very frustrated. Any suggestions much appreciated.
Thanks,
Rob

First this site for Adobe Product user there are forum and sub topic forum for Adobe suite of applications. Members here are not Adobe employees though some help Adobe employee do drop by. If you think you have a bug you can follow the an other Links in Photoshop menu Help>Photoshop Support Center... web page. It will take you to the right place Photoshop Family Customer Community

Merge to HDR Pro: What you see is not what you get?

I am using PSCC on an iMac (Mavericks). When I bring bracketed shots into PSCC's Merge to HDR Pro, I can work the settings and/or presets to get an image that looks OK. However, when I exit from HDR Pro by clicking OK, the image displayed in PSCC is very different from what I was just looking at in HDR Pro. The screenshots here show just one example, working in 16-bit mode. Other images show even greater differences. Working in 32-bit mode makes it even worse. This did not use to happen in my earlier versions of PS (perpetual license). Am I missing something or doing something wrong?
Image in HDR Pro:
Image in PSCC after clicking OK:

Trevor.Dennis wrote:
Yes I realised that. There are now quite a few applications for processing HDR, and IMO Photomatix has always been the best of them, and certainly did a better job than Photoshop. My point was that the old 'Merge to HDR Pro' workflow is now redundant if you have Photoshop CC, and that using Camera RAW as outlined by Julianne Kost, has suddenly leapfrogged all the competition by an order of magnitude.
So I strongly urge you to take Mr Prengel's advice. Output the image in 32bit, and use ACR to process it. Did you watch the video tutorial I linked to?
You certainly shouldn't get all pixel-peeper about how the 32bit image looks on your screen. It is not possible to show the tonal width of a 32 bit image on a computer screen, so you are seeing a 'representation' of how it might look after processing.
FWIIW I have taught HDR (and Photoshop) to some of the best photographers in the world at two PSNZ National Conventions back in 2010 and 2011, so I kind of have strong opinions about it. Not that I use it excessively, but it is a very handy tool to keep in your photographic skills repertoire.
Trevor,
I am sorry if I misunderstood your post. I am actually using the same workflow as Julianne Kost in her video (which I had watched prior to posting here). And, as I posted above, I do agree with Mr. Prengel that I should just take the 32 bit image into Camera Raw and do the toning there. As a matter of fact, that is what I have been doing in Photoshop CC (sending the pictures from Lightroom, same as Julianne Kosts does), and I can do a very good job, if I say so myself.
So the question I had was merely one of puzzlement at seeing the difference between the image just before exiting HDR Pro and what shows up in Camera Raw. In the examples I provided, and in many other cases, it clearly went beyond pixel-peeping: they were two very different images. But I think I understand now why this is, which you kindly pointed out: it is not possible to show the tonal width of a 32 bit image on a computer monitor. I had not considered that and I thank you for mentioning it.
It may be that in some cases (as in Julianne Kosts's video) the representation in HDR Pro is actually pretty close to the initial view in Camera Raw, but in other cases (my examples) it is not. Not really an issue, I agree.

How does the "Manually Set EV"dialog box in "Merge to HDR Pro" work?

What is the "Manually Set EV"dialog box in "Merge to HDR Pro" for?
Do these values affect the HDR results?
Since the source images are chosen in the first dialog of "Merge to HDR Pro"
why do we need to set EV manually here?
Besides, after I tried different values to compare the results
the "Manually Set EV"dialog box has disappeared how can I get it back?
THANKS

If the files you are merging don't have metadata giving their exposure values (time, aperture, ISO), then MergeToHDR prompts you for the relative exposure values.
If your files have the metadata, then there is no need to enter the values manually.

Merge to HDR Pro: Result different than preview

Similar Messages

Maybe you are looking for