Jump to content

Recommended Posts

Posted

With Affinity 2.2.1 on flattening a document or saving in any format, tiff, png or jpeg there is  a slight loss of sharpening. There is also a slight but definite change in the colours, particularly blues. Has anybody else noticed this? It is very frustrating and I am at a loss to know what is happening. This loss of sharpening was also a problem with some versions of Affinity 1 although to a somewhat greater degree. I cannot remember what resolved the problem at that time but it did eventually stop happening. I would welcome any suggestions and comments. I have been puzzled at my dissatisfaction with my processed pictures since last upgrading Affinity 2 but only spotted the problem today.

Posted

It would be helpful to have a copy of a sample document before it is flattened, so we can see the details of the document and see the loss of sharpness happening.

 

-- 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.3.1, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1

Posted
33 minutes ago, pthompso said:

With Affinity 2.2.1 on flattening a document or saving in any format, tiff, png or jpeg there is  a slight loss of sharpening. There is also a slight but definite change in the colours, particularly blues. Has anybody else noticed this? It is very frustrating and I am at a loss to know what is happening. This loss of sharpening was also a problem with some versions of Affinity 1 although to a somewhat greater degree. I cannot remember what resolved the problem at that time but it did eventually stop happening. I would welcome any suggestions and comments. I have been puzzled at my dissatisfaction with my processed pictures since last upgrading Affinity 2 but only spotted the problem today.

The symptoms you are describing have been reported before. 
in most cases, it was caused by:

  • inspecting files at zoom level different from 100%. This affects sharpness / noise filters mostly, but can lead to color shifts depending on content.

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

Thanks for your replies. Images posted in this reply.

The difference in sharpness is very evident here in the drummer (Bones). Flatten this pic and it immediately looks exactly like the jpeg or any other format it exported in. This happens at the same screen size and resolution etc. and makes accurate sharpening impossible. 

 

P9010019 2.jpg

P9010019 2.afphoto

Posted

Cannot spot any visual or numerical difference with multiple methods:

  • merge visible on top. Set blend mode to difference. Add levels with white level set to zero. Not a single pixel differs.
  • export as PNG uncompressed. Not a single pixel differs.
  • jpeg shows expected compression artifacts.

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

Which os / gpu do you use?

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

As you document is RGB/16 some color differences are expected exporting to jpg (8 bit only).

other differences may be caused by preview apps and (lack of) support for color profiles 

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

I apologise for my ineptness here. I have never used a forum before and don't yet understand how it works.

I have spent the afternoon finding that this happens with EVERY afphoto when I flatten it or export it. I do not understand why there should be any visible change to the image at all when I flatten it. It should appear to be EXACTLY the same.

Thanks for your help but I remain baffled by what is happening.

Mac mini M2 Pro.

Posted

Mac mini M2 Pro. Sonoma 14.0

I do not understand why flattening an afphoto should result in any visible onscreen changes. It means I can never view a processed picture exactly as I have processed it except within the Affinity editor. This is not at all satisfactory.

Posted

Normally it doesn’t.

as a cannot reproduce this issue on my M1 Mac, others with same hardware may steps in and try to reproduce.

 

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

Left: Image open in Photo.

Right: Export to JPG, 85% quality.

identical except jpeg compression artefacts

Screenshot 2023-10-24 at 21.11.07.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
2 hours ago, pthompso said:

The difference in sharpness is very evident here in the drummer (Bones). Flatten this pic and it immediately looks exactly like the jpeg or any other format it exported in. This happens at the same screen size and resolution etc. and makes accurate sharpening impossible. 

 

1 hour ago, pthompso said:

I do not understand why flattening an afphoto should result in any visible onscreen changes. It means I can never view a processed picture exactly as I have processed it except within the Affinity editor. This is not at all satisfactory.

You must evaluate all sharpening operations (such as your multiple Live Unsharp Mask filters) at 100% Zoom. You cannot accurately determine how they will look if you are zoomed out, e.g.,  to the 28% Zoom that is needed to see all the image on my screen with my studio layout. This is because of the way that Affinity uses MipMaps technology to speed up the screen display.

Flattening (during Export or manually while editing) will also give you a true view of the amount of sharpening you've applied, which you can do non-destructively using Merge Visible. @NotMyFault mentioned using that to examine your document and to verify that the export was correct. You could also use that while editing:

  1. Set the sharpening parameters.
  2. Merge visible, so you can see how it truly looks even though you're zoomed out.
  3. If it's not good, delete that layer, and readjust the sharpening parameters again.

But the way the application is designed, to really see what the Unsharp Mask is doing while you're adjusting it, you need to be at 100% and panning around the image if you need to see its effects in different areas.

So, rather than applying the filter and evaluating how it looks with the entire image visible:
image.png.1a9ad625896b352e4ec5e4bc53b145e7.png

you need to get to 100% Zoom and view it this way:

image.png.67d776327979cceff166de77cf81ad58.png

and pan to see the other areas of the image.

-- 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.3.1, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1

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.