Photoshop: Merge to HDR "The operation could not be completed" in PS CS6

  • 2
  • Problem
  • Updated 4 years ago
  • Solved
  • (Edited)
For several months now I have not been able to merge files to HDR in CS6. I'm running Win 7 64-bit.

It doesn't work in 64- or 32-bit.

I have removed or reset the preferences file.

I have deactivated, reinstalled, and reactivated CS6.

I have run updates.

I have 32 GB of memory with over 100 GB scratch on an SSD (went up to 3 TB with platter drives, didn't help).

I've updated the 660 Ti drivers to the most recent.

I've tried with and without enabling graphics acceleration.

I've swung cache levels from low to high, memory options all the way from 1 GB to 20 GB, and VRAM from 3 to 2 GB.

Process to failure: I use File > Automate > Merge, select three TIFFs (about 60 MB each), and tell it OK. PS loads the images and appears to 'go through the motions' of creating the merged output, then fails with the topical message. The merge fails with or without align. With or without tabular documents. Basically, I've exhausted all the help I've found (the most comprehensive of which was posted by a Meredith).

All I'm left with is a cryptic Windows error message with no useful troubleshooting information.
Photo of leviathor

leviathor

  • 4 Posts
  • 1 Reply Like

Posted 4 years ago

  • 2
Photo of leviathor

leviathor

  • 4 Posts
  • 1 Reply Like
Operation fails when merged via Bridge, too.
Photo of leviathor

leviathor

  • 4 Posts
  • 1 Reply Like
Solved.

Photoshop CS6 does not support the colorspace of the 1Ds3 when merging to HDR. I exported a series in ProPhoto and found that they would merge just fine.
Photo of Meredith Payne Stotzner

Meredith Payne Stotzner, Employee

  • 65 Posts
  • 8 Reply Likes
Hi,
Thanks for the update.
What led you to the conclusion it was the color space?
How are the TIFFs you're using being created? (From what I can tell, the camera only outputs JPG and CR2 files.)
I'd be interested in talking a look at your problematic TIFFs if you are willing to share.
Thanks!
Meredith
Photo of leviathor

leviathor

  • 4 Posts
  • 1 Reply Like
Hey Meredith,

The color space solution just sort of came on a whim. I used to start my workflow in ProPhoto, but since moving to CaptureOne as a raw processor I've processed RAW to TIFF embedding the native camera color space. For grins, and with a slight inkling, I decided to output in ProPhoto, and voilĂ , success.

While the camera does output two file types, the native interpretation from C1 for RAW is along the lines of "1DsMarkIII-Generic." While this may be the same as AdobeRGB (I guess it ought to be? (since that's one of two color spaces available)), C1 labels it differently. I wonder now if there's any byte-level difference between the color information of a "camera" TIFF and an AdobeRGB TIFF--another experiment for another day, I guess.

And thanks to you if you're the Meredith who posted those original exhaustive lists with possible solutions.
Photo of Meredith Payne Stotzner

Meredith Payne Stotzner, Employee

  • 65 Posts
  • 8 Reply Likes
I'm glad you liked the possible-solutions list. I'm sorry none of them worked for you. I'll follow up on this issue and get back to you if we find a better solution or have some questions.
Thanks!
Meredith
Photo of Jeff T Robinson

Jeff T Robinson

  • 1 Post
  • 0 Reply Likes
Thanks. This fix worked for me as well: I also export from Capture One and had the camera color space embedded. Changing to the ProPhoto RGB colorspace for my 16-bit tiffs also eliminated this error for me.