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

P: Merge To HDR Pro in 32 bit fails

Community Beginner ,
Apr 13, 2017 Apr 13, 2017

Copy link to clipboard

Copied

This is not just an annoyance - it is a show stopper. When trying to use "Merge to HDR Pro" from Lightroom, it aborts in Photoshop with "Camera Raw Filter is not available" after "Open anyway" was chosen in Lightroom. The same happens when "Camera Raw Filter" is chosen from the filter menu in Photoshop. Photoshop shows Camera Raw is 9.10.0.739 so that's the latest but there's obviously a bug where this is not being recognised as the latest. How do I revert to the previous version of Lightroom and Camera Raw because the use of the Camera Raw filter is part of my normal workflow many times a day.Note: This conversation was created from a reply on: Lightroom Edit in Photoshop warning message since update.

Bug Won't fix
TOPICS
macOS , Windows

Views

197

Translate

Translate

Report

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

Adobe Employee , Apr 20, 2017 Apr 20, 2017
Here is a Help Document that describes the reasons for the change and the alternate workflows. 
https://helpx.adobe.com/photoshop/kb/command-camera-raw-filter-not-available-merge-hdr-pro.html

Votes

Translate

Translate
16 Comments
Adobe Employee ,
Apr 13, 2017 Apr 13, 2017

Copy link to clipboard

Copied

That I can duplicate, Tarun. Please stand by while I check with engineering.  

Note: this only occurs when 32 Bit and ACR Tone Mapping are selected. 
Rikk Flohr - Customer Advocacy: Adobe Photography Products

Votes

Translate

Translate

Report

Report
LEGEND ,
Apr 14, 2017 Apr 14, 2017

Copy link to clipboard

Copied



After the latest update I am no longer able to open 32 bit .EXR files in the camera raw filter. Part of my job is to work with and edit 32 bit renderings - and opening these images in the camera raw filter has been part of my normal workflow for the past year. It worked yesterday before I updated, and does not work today.

Anyone else having an issue?
Thanks for taking the time to read.

OS: Windows 10 x64
PS Version: 20170309.r.207

Votes

Translate

Translate

Report

Report
LEGEND ,
Apr 14, 2017 Apr 14, 2017

Copy link to clipboard

Copied

Same problem...

Votes

Translate

Translate

Report

Report
LEGEND ,
Apr 15, 2017 Apr 15, 2017

Copy link to clipboard

Copied

Same problem. Is it possible revert updates Camera Raw-Ligtroom to previous versions?

Votes

Translate

Translate

Report

Report
Engaged ,
Apr 15, 2017 Apr 15, 2017

Copy link to clipboard

Copied

Same here.

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Apr 20, 2017 Apr 20, 2017

Copy link to clipboard

Copied

Here is a Help Document that describes the reasons for the change and the alternate workflows. 
https://helpx.adobe.com/photoshop/kb/command-camera-raw-filter-not-available-merge-hdr-pro.html
Rikk Flohr - Customer Advocacy: Adobe Photography Products

Votes

Translate

Translate

Report

Report
New Here ,
Jun 06, 2017 Jun 06, 2017

Copy link to clipboard

Copied

best solution ever. instead of fix 32 bits  mismatches simply delete the whole option. it is like if I buy a car and then the manufacture one night will put a faloimitator to the drivers chair... and say we decided this is very convenient.

Votes

Translate

Translate

Report

Report
Participant ,
Jul 10, 2017 Jul 10, 2017

Copy link to clipboard

Copied

I'm with you all on this.  I had to revert to acr 9.9 and am unable to update unless this is changed back to how it was - simply giving us the choice of which way to work on our 32 bit images.  The workaround and reasons why the change was made are not sufficient - the workaround pretty much destroys my workflow and creates a ton more work for me and makes some things impossible (transferring whole acr filters to a different document retaining all adjustments including local/gradient/brush adjustments).  
If Adobe wants to put a little warning box about possible color mismatches up that you can hit accept to, fine - but I was aware of the "visual mismatches" (mostly seemed to vary slightly from computer to computer) - but they weren't significant enough to disrupt my workflow or cause any problems of significance.  The option of which way we want to proceed on our 32 bit images, as before, seems like it's getting enough attention that this should be seriously considered to change back.  It's either that or I never get to update again and forever rely on the additional step of converting newer raw files to dng so that I may work.

Votes

Translate

Translate

Report

Report
Participant ,
Jul 10, 2017 Jul 10, 2017

Copy link to clipboard

Copied

I'm with you all on this.  I had to revert to acr 9.9 and am unable to update unless this is changed back to how it was - simply giving us the choice of which way to work on our 32 bit images.  The workaround and reasons why the change was made are not sufficient - the workaround pretty much destroys my workflow and creates a ton more work for me and makes some things impossible (transferring whole acr filters to a different document retaining all adjustments including local/gradient/brush adjustments).  
If Adobe wants to put a little warning box about possible color mismatches up that you can hit accept to, fine - but I was aware of the "visual mismatches" (mostly seemed to vary slightly from computer to computer) - but they weren't significant enough to disrupt my workflow or cause any problems of significance.  The option of which way we want to proceed on our 32 bit images, as before, seems like it's getting enough attention that this should be seriously considered to change back.  It's either that or I never get to update again and forever rely on the additional step of converting newer raw files to dng so that I may work.

Votes

Translate

Translate

Report

Report
LEGEND ,
Jul 12, 2017 Jul 12, 2017

Copy link to clipboard

Copied

I am very frustrated to know that. Coming from a background of processing 3D renders in photoshop i like to save full 32bit files and color correct/expose them properly in photoshop.

This is a huge tool and removing it because of an inconsistency is so sad. 😞

please evaluate bringing it back. I believe many 3D users who retouch renders in photoshop might be running on this issue as well.

for now I'll just keep using a downgraded version.

Votes

Translate

Translate

Report

Report
LEGEND ,
Aug 07, 2017 Aug 07, 2017

Copy link to clipboard

Copied

Hoping for a change as well. I shoot HDR all the time, often with moving people/trees/etc and need Remove Ghosting, which is crap in ACR compared to Photoshop. Workarounds are insufficient for me. I'm having to do manual exposure blending until there's a fix...takes too much time...

Votes

Translate

Translate

Report

Report
LEGEND ,
Aug 07, 2017 Aug 07, 2017

Copy link to clipboard

Copied

For me, this change was an epic fail for Photoshop.

Votes

Translate

Translate

Report

Report
LEGEND ,
Aug 07, 2017 Aug 07, 2017

Copy link to clipboard

Copied

Really? Because of mismatches in color you disable a whole feature that plays a big part on professional use of Photoshop? The ability to edit in 32 bits is shameful and the only useful tool you had in there (camera raw editing 32bits), you guys take it off? Are you even listening to your public before making these changes? Seriously, you need some consulting on professional use of Photoshop. You guys are focusing too much on mobile. Sorry I'm pissed! I will have to downgrade my Photoshop because of this.

Votes

Translate

Translate

Report

Report
Community Beginner ,
Jan 08, 2018 Jan 08, 2018

Copy link to clipboard

Copied



"In Adobe Camera Raw 9.10, directly applying the Camera Raw Filter to a 32-bit Photoshop document has now been disabled to prevent unexpected visual mismatches between Camera Raw and Photoshop"
Please bring back the option to edit 32 bit in Camera Raw. 

The raw-converter in Photoshop can no longer edit 32-bit EXR files rendered from 3D-programs. Camera Raw can only edit 16 bit raw and this really limits workflow. The benefit of using 32-bit color depth is that these files have a higher definition range for the colors. This is crucial in order to adjust the renders to optimal capacity. Rendering or converting to 16 bit reduces the color gamut way too much. 

Installing the older Camera Raw version 9.1.1.461 (Using CC 14.0) brings back the option to edit 32 bit raw, but then some updated features in the raw editor will not be working. (Latest version of raw is currently 10.1). Both Photoshop CC 19 and CC 14.0 uses the same folder for the Camera Raw 8BI File, so it is only possible to use the currently installed version for both CC19 and CC 14. I also tried using CS6 but here there is no UI for editing Camera Raw. 

For anyone working with 3D-renders and EXR files the workarounds presented in the forums are not really a valid option. Please bring back the option to edit 32 bit in Camera Raw. 

Votes

Translate

Translate

Report

Report
Community Beginner ,
Jan 08, 2018 Jan 08, 2018

Copy link to clipboard

Copied

Bruce replied to my post in my topic "bring back 32 bit..." 

I open EXRs with the ProEXR plugin in Photoshop, do my 32-bit business and then convert to 16/8bit as needed. Is this helpful?

http://www.fnordware.com/ProEXR/

    This sure is helpful. I also tried using the EXR-IO plugin http://www.exr-io.com/
    However, with these plugins I cannot use the hundreds of Camera Raw settings I have saved as .xmp files, so a lot of work will need to be redone if start using these plugins. Also for the EXR-IO it requires VRay for Unreal and our media department is using Lightmass  for Unreal.

    The benefit of using Camera Raw is therefore that is saves a ton of rework.

    Votes

    Translate

    Translate

    Report

    Report
    Community Beginner ,
    Jan 10, 2018 Jan 10, 2018

    Copy link to clipboard

    Copied

    LATEST
    Why is my post merged with "Merge to HDR" from Lightroom? It is not the same issue. I was chatting with customer service and wanted to add a feature wishhlist for a future version of Photoshop. He told me to go to www.adobe.com/products/wishform.html 

    Instead I had to make a bug report and now it is merged with this post. Bummer.

    Votes

    Translate

    Translate

    Report

    Report