Jump to content

Recommended Posts

Posted

After loading 5 Tiff files into an HDR merge and tweaking the image looks great. I apply the changes and the image is loaded into the standard photo persona. 

However, when I export the image as either a .jpg or .tiff file, the highlights are completely messed up (see screen shots). 

Also, something weird I discovered while making this post: taking a screen shot of the open file in Affinity photo also renders the same issue. I had to snap a photo of the screen with my iPhone to show how the image should look like (it only affects the clouds in the photo). 

Affinity Photo 1.10.4

IMG_5833.HEICmacOS Monterey version 12.1

iMac Retina 4k, 21.5 inch 2019

3 GHz 6-Core Intel Core i5

Screen Shot 2022-05-28 at 9.28.06 AM.png

Posted

Welcome to the Serif Affinity forums.

An HDR Merge will, I believe, be an RGB-32 image file. 

JPG images are only RGB-8, and can't show the full range.

TIFF can support RGB-32, but the question then is what you're using to view the image once you export.

Your screenshot is also going to be an 8-bit format, and would have the same issue.

-- Walt
Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases
PC:
    Desktop:  Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 

    Laptop:  Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
    Laptop 2: Windows 11 Pro 24H2,  16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU
iPad:  iPad Pro M1, 12.9": iPadOS 18.5, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.5

Posted

Please activate 32 bit preview and check that “icc managed” is active.

next, check that no color values above 1.0 exists. You can raise the limit in histogram.

If both conditions are met, export to rgb/8 or rgb/16 will be almost matching.

If you have use “unmanaged”, you need to gamma correct the image with help of procedural texture filter.

In case of excess brightness, use tone map persona or levels to map excess brightness in the sdr range.

Affinity does not correctly support tiff/32. Don’t use it for export of RGB/32. 
There is actually no format to export RGB/32, and it is normally not required. Instead, export as RGB/16, using tiff or png.

Mac mini M1 A2348 | MBP M3 

Windows 11 - AMD Ryzen 9 5900x - 32 GB RAM - Nvidia GTX 1080

LG34WK950U-W, calibrated to DCI-P3 with LG Calibration Studio / Spider 5 | Dell 27“ 4K

iPad Air Gen 5 (2022) A2589

Special interest into procedural texture filter, edit alpha channel, RGB/16 and RGB/32 color formats, stacking, finding root causes for misbehaving files, finding creative solutions for unsolvable tasks, finding bugs in Apps.

I use iPad screenshots and videos even in the Desktop section of the forum when I expect no relevant difference.

 

Posted
21 minutes ago, walt.farrell said:

Welcome to the Serif Affinity forums.

An HDR Merge will, I believe, be an RGB-32 image file. 

JPG images are only RGB-8, and can't show the full range.

TIFF can support RGB-32, but the question then is what you're using to view the image once you export.

Your screenshot is also going to be an 8-bit format, and would have the same issue.

I have tried both Jpeg and tiff exports, 8bit and 16 bit. It should at least represent what I am seeing being previewed in the photo persona, but it's not even close. It looks like the highlight tonal compression is simply not rendering properly in the final export. More oddly is the fact that taking a screen shot does the same thing. 

Posted
9 minutes ago, NotMyFault said:

Please activate 32 bit preview and check that “icc managed” is active.

next, check that no color values above 1.0 exists. You can raise the limit in histogram.

If both conditions are met, export to rgb/8 or rgb/16 will be almost matching.

if not, use tone map persona or levels to map excess brightness in the sdr range.

Affinity does not correctly support tiff/32. 

Could you explain the second sentence? I am not sure where that is

Posted

https://affinity.help/photo/English.lproj/pages/Panels/histogramPanel.html
 

raise the “max” value to 2 or 4, and check if there are any pixels above 1.0

Mac mini M1 A2348 | MBP M3 

Windows 11 - AMD Ryzen 9 5900x - 32 GB RAM - Nvidia GTX 1080

LG34WK950U-W, calibrated to DCI-P3 with LG Calibration Studio / Spider 5 | Dell 27“ 4K

iPad Air Gen 5 (2022) A2589

Special interest into procedural texture filter, edit alpha channel, RGB/16 and RGB/32 color formats, stacking, finding root causes for misbehaving files, finding creative solutions for unsolvable tasks, finding bugs in Apps.

I use iPad screenshots and videos even in the Desktop section of the forum when I expect no relevant difference.

 

Posted (edited)

I think I found the issue: this issue only occurs when I save my settings as a preset in the tone mapping persona. I noticed this because the preview thumbnail for my preset shows the exact blown highlights that I am experiencing in the exports. 

If I chose a default preset or simply manually adjust some of the parameters then the export is fine ... I just can't save a usable preset :(

Edit: 

Actually, any changes I make to the preset will result in this issue

 

Edited by filmshootr
update

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.