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

P: 32bit TIFFs are no longer treated as raw files

Participant ,
Jan 03, 2023 Jan 03, 2023

Copy link to clipboard

Copied

Broken: LrC 12.1

Working: LrC 12.0.1

OS: Win11 22H2

GPU driver: Nvidia gameready 527.56 (disabling GPU acceleration does not resolve the issue)

 

32bit TIFF files (such as 3D renders, astro stacks, HDRs from third party tools, etc) are not being rendered correctly in Lightroom Classic 12.1. The bug is new in 12.1, 12.0.1 handles them correctly/as previous versions did.

 

Here's how 12.0.1 handles this file: autumn_bunker_20221116_autumn_bunker_camA_f000-2.jpgexpand image

 

Here's the same file, with the same develop settings and export settings, from 12.1:

autumn_bunker_20221116_autumn_bunker_camA_f000.jpgexpand image

 

The highlights and shadows adjustments simply flatten the contrast of the image. Additionally, in 12.1 the white balance slider is now relative(-100 to +100) instead of absolute (showing a kelvin temp). As if 32bit TIFFs are being treated as non-raw/non-linear files or something like that?

 

Here's a sample TIFF: https://drive.google.com/file/d/1WvqO09WhL3QtTVw4SEaCost6ChcwKJYX/view?usp=share_link

 

Steps to reproduce:

  1. Load any 32bit tiff, the sample file linked above will do
  2. Attempt to make some adjustments, particularly the highlights/shadows sliders
  3. Note that the result is not at all as expected. (also note the white balance slider is curiously not displaying a temp, but rather a relative value)
Bug Fixed
TOPICS
Windows

Views

3.7K
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 Pinned Reply

Adobe Employee , Feb 13, 2023 Feb 13, 2023

Greetings all,

 

Updates for Adobe Photography products have been released.  The February 2023  updates contain a fix for this issue. 

If you do not see the update in your Creative Cloud Application, you can refresh it by hitting [Ctrl/Cmd]+[Alt/Opt]+[ R ].

Note: It may take up to 24 hours for your update to be available in your Creative Cloud app.

 

Thank you for your patience.

Status Fixed

Votes

Translate
32 Comments
Adobe Employee ,
Nov 09, 2023 Nov 09, 2023

Copy link to clipboard

Copied

@SvenFlock 

Please note that while the behavior today is a departure from previous behavior(s), it is the as-designed behavior currently and was a deliberate change going forward. 

 

Rikk Flohr: Adobe Photography Org

Votes

Translate

Report

Report
Participant ,
Nov 09, 2023 Nov 09, 2023

Copy link to clipboard

Copied

Why was the decision made to treat TIFF-32 differently from Linear DNG, when they contain essentially the same data? Is there plans for an alternative file type to Linear DNG (such as OpenEXR) since so few tools support exporting Linear DNG? Lightroom has an excellent pipeline for handling scene-linear RGB images, but it's near unuseable if it only accepts Linear DNG as inputs for that pipeline.

Votes

Translate

Report

Report
Participant ,
Nov 09, 2023 Nov 09, 2023

Copy link to clipboard

Copied

Ok, follow up on this comment. After @Rikk Flohr: Photography stated this was an intentional change, I got curious about how editing in PS works for images with HDR enabled. It does indeed return them as...32bit TIFF! So it appears that the TIFF-32 importer has been repurposed from being a scene-referred loader (old behavior) to a display-referred HDR loader? That...at least kinda makes sense. It ensures PS edits return to LR exactly as they looked in PS (bringing the edited TIFF in as a scene-referred file and simply re-applying the same develop settings might produce signficantly different results)

 

Except this leaves LR 13.x with only Linear DNG for scene-referred input, and almost nothing supports writing that. Not even PS can write 32bit files to Linear DNG. If you have a scene-referred file from another application such as 3rd party HDR tools, astro stacking, 3D renders, etc, you're apparently out of luck unless you have an app that can convert TIFF-32/OpenEXR/Radiance to Linear DNG. Which btw, is not a functionality that exists in any Adobe product that I'm aware of. (it did in LrC 12.x, hillairiously enough, by importing a 32bit TIFF and converting it to DNG!)

 

tl:dr: Adobe, can we have OpenEXR import support now?

Votes

Translate

Report

Report
New Here ,
Nov 10, 2023 Nov 10, 2023

Copy link to clipboard

Copied

So Adobe silently decides to brake a long stabilished behaviour like it doesn't affect users and we are condemned to get stuck to version 12.0.1 forever?

Votes

Translate

Report

Report
Community Beginner ,
Nov 10, 2023 Nov 10, 2023

Copy link to clipboard

Copied

Further, even if it is intented to have TIFF file treated the new way starting with v13, it is still inconsistent to have the old behaviour on previous importet 32bit TIFF file in the even updated Lightroom Classic catalogue.

Votes

Translate

Report

Report
New Here ,
Nov 10, 2023 Nov 10, 2023

Copy link to clipboard

Copied

@SvenFlock 

 

For my albuns it doesn't have the old behaviour for previously imported 32bit tiff images. If I just open any old image in develop module or even just create a virtual copy, LR renders the image completely differently making impossible to export the images again to obtain the same previous results.

Votes

Translate

Report

Report
Participant ,
Nov 11, 2023 Nov 11, 2023

Copy link to clipboard

Copied

LATEST

@Tijolo3075623940hb Yeah, I'm seeing the same. I've got a number of things that I just can't export in their original form anymore. Only exceptions are the things I converted to DNG prior to updating to LrC 13

Votes

Translate

Report

Report