Jump to content
You must now use your email address to sign in [click for more info] ×
Our response time is longer than usual currently. We're working to answer users as quickly as possible and thank you for your continued patience.

tiff and all other formats: image does not match the display in-app


Recommended Posts

Bildschirmfoto2024-07-10um16_46_20.thumb.png.abc0307033104f77bacb501cac915866.png

 

Every image I want to export does not look like it does in the app. No matter whether tiff, jpg, psd or others. Entire colour areas are missing. Most of them are much lighter.

 

 

Link to comment
Share on other sites

As you're working in HDR (RGBA-32) you may need to use a significantly different workflow if you want to export to RGB-8 as you are doing.

If those are RAW images you're working with, you might want to change your Affinity Photo Settings >  Assistant > Develop Assistant to develop to RGB-16 instead, which will allow a simpler workflow:

image.png.40dccd20c5c0f7a35d3abdfb054938f1.png

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

    Laptop:  Windows 11 Pro, version 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
iPad:  iPad Pro M1, 12.9": iPadOS 17.5, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.5

Link to comment
Share on other sites

Thank you, the development assistant for developing according to RGB-16 was already set for me.

I have tried it, it doesn't matter whether I set export in 8, 16 or 32 bit. The image is clearly different from in-app view.

Bildschirmfoto2024-07-10um17_20_15.thumb.png.671abbb594e060be0d861c043910c460.pngBildschirmfoto2024-07-10um17_21_37.thumb.png.6161aa236c15292a6f4560bf32887158.png

 

Link to comment
Share on other sites

In the top image, you are still working in a Linear 32-bit working space, then converting to a 16-bit TIFF. All those adjustments are done in a linear space and are treated differently than a gamma encoded color space (like your TIFF).

When you change those develop settings in the Assistant, they do NOT take place immediately. You have to close, then re-Develop the RAW file AFTER changing those settings for them to take place. You can see your second screenshot is still 32-bit Linear.

So, try changing your Develop Settings, THEN open your RAW file. See if that works for you.

2017 15" MacBook Pro, 16 MB RAM, Ventura v13.6.7, Affinity Photo/Designer/Publisher v1 & v2, Adobe CS6 Extended, LightRoom v6, Blender, InkScape, Dell 30" Monitor, Canon PRO-100 Printer, i1 Spectrophotometer, i1Publish

Link to comment
Share on other sites

@Markus3 If you don't want to re-Develop this image, try flattening the document, or do a Merge Visible, leaving the merged pixel layer at the top of the layer stack. This will hide all underlying layers and adjustments. Then, try exporting to TIFF 16 bit. I'm not absolutely certain that will work, but it may.

I've used 32 bit a number of times, but I try to avoid it unless I run into a rare RAW image that is extremely difficult to process effectively in any other way. I can usually get a good result in 16 bit. If regular 16 bit doesn't work, I will try 16 bit and disabling the tone curve (Take No Action) using the Assistant. This delivers a flatter image to Photo (Gamma is applied, but no Tone Curve) and is less likely to blow out highlights or muddy up the shadows. But again, changes in the Development mode must be done BEFORE opening the RAW image for processing. If the RAW image is already opened, changing settings will not take effect, whether you in the Develop or Photo Personas. 

2017 15" MacBook Pro, 16 MB RAM, Ventura v13.6.7, Affinity Photo/Designer/Publisher v1 & v2, Adobe CS6 Extended, LightRoom v6, Blender, InkScape, Dell 30" Monitor, Canon PRO-100 Printer, i1 Spectrophotometer, i1Publish

Link to comment
Share on other sites

@Markus3 I did some additional experimentation, but not in great depth.

I opened a RAW DNG file in the Develop Persona and brought it into Photo as 32 bit Linear and ROMM RGB (same as ProPhoto RGB). I then added a bunch of adjustment layers and filters in Photo while the image was still in a 32 bit linear ROMM RGB space.

I exported the 32 bit file to 8 bit JPG, Display P3 profile, 85% quality. It looks the same as my 32 bit linear file as displayed in Photo. I tried exporting with all layers intact, also flattened, with a Merge Visible Layer on top, and also with EDR enabled on my MacBook Pro. All files look the same when EXPORTED to JPG, whether flattened first or not.

However, if I CONVERT the file from 32 bit Linear ROMM RGB to 16 bit Display P3 with all adjustment layers and filters showing, the appearance changes (brightens considerably). This tells me that those adjustment layers and filters are treated much differently with different gammas. If I flatten the image or Merge Visible before Converting the file, the converted file looks the same as my 32 bit file. The same thing happens when converting files from 1..8 gamma to 2.2 gamma, Lab, etc. Those additional layers are composited using the currently active gamma curve, so a different gamma results in a shift.

I suspect Affinity first flattens the file (in the background) when exporting the file to JPG and probably also with TIFF, PNG, etc. This locks the colors and tones into a single pixel layer, so the exported file looks the same. So, from my very limited testing, you can work in 32 bit and EXPORT to other flattened file formats while preserving appearance. But, if you want to CONVERT to another color space with a different gamma within Photo, you need to flatten or merge visible first. 

More testing might change my conclusions, but that's what I've found so far. 

2017 15" MacBook Pro, 16 MB RAM, Ventura v13.6.7, Affinity Photo/Designer/Publisher v1 & v2, Adobe CS6 Extended, LightRoom v6, Blender, InkScape, Dell 30" Monitor, Canon PRO-100 Printer, i1 Spectrophotometer, i1Publish

Link to comment
Share on other sites

Have you tried developing to 16-bit, yet, rather than 32-bit? That's usually recommended except for some specialist workflows.

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

    Laptop:  Windows 11 Pro, version 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
iPad:  iPad Pro M1, 12.9": iPadOS 17.5, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.5

Link to comment
Share on other sites

@walt.farrell 

2 minutes ago, walt.farrell said:

Have you tried developing to 16-bit, yet, rather than 32-bit? That's usually recommended except for some specialist workflows.

Definitely agree!

2017 15" MacBook Pro, 16 MB RAM, Ventura v13.6.7, Affinity Photo/Designer/Publisher v1 & v2, Adobe CS6 Extended, LightRoom v6, Blender, InkScape, Dell 30" Monitor, Canon PRO-100 Printer, i1 Spectrophotometer, i1Publish

Link to comment
Share on other sites

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.