JoelOwens Posted February 14, 2021 Share Posted February 14, 2021 (edited) The resolution is calculated incorrectly for TIFF files that have cm as resolution unit Correct: Value in cm * 2.54 = Value in dpi To me it looks like the following is calculated: Affinity Photo Win: value in cm / 2.54 / 2 Affinity Photo Mac: Value in cm / 2.54 For example: The file specifies 118.1100038 pixels per cm. Correct would be 118.1100038 * 2.54 =299.9994097 dpi (300 dpi), Affinity Mac calculates 46 dpi, Affinity Windows 23 dpi. Edit: What I initially thought was a difference between Win and Mac may also have another cause (see examples below) Edited February 14, 2021 by JoelOwens Quote Link to comment Share on other sites More sharing options...
walt.farrell Posted February 14, 2021 Share Posted February 14, 2021 Can you share a TIFF file that shows the problem, please? Quote -- 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.4.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.4.1 Link to comment Share on other sites More sharing options...
JoelOwens Posted February 14, 2021 Author Share Posted February 14, 2021 (edited) Sure. Attached is the example file and a screenshot showing the resolution in Photoshop (pixel/cm), in GIMP (calculated in pixel/inch) and incorrectly calculated in Affinity. In addition an output of ExifTool for the example file. example_resolution_cm.tif Edited February 14, 2021 by JoelOwens walt.farrell 1 Quote Link to comment Share on other sites More sharing options...
JoelOwens Posted February 14, 2021 Author Share Posted February 14, 2021 (edited) Oh. Another related bug. Depending on how the image is saved (strips), Affinity calculates differently The screenshot shows the output of Affinity, now calculated as 23 dpi for the second test file attached here, together with the output of ExifTool. example-2_resolution_cm.tif Edited February 14, 2021 by JoelOwens Quote Link to comment Share on other sites More sharing options...
JoelOwens Posted February 14, 2021 Author Share Posted February 14, 2021 And it is also calculated differently when switching between 8 and 16 bit or grayscale and RGB. There must be something completely wrong. Quote Link to comment Share on other sites More sharing options...
walt.farrell Posted February 14, 2021 Share Posted February 14, 2021 I'm wondering if there's some issue with your 1x1px files. Perhaps try something that is more reasonably sized, and see if the same issues occur? Quote -- 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.4.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.4.1 Link to comment Share on other sites More sharing options...
JoelOwens Posted February 15, 2021 Author Share Posted February 15, 2021 No, the problem is completely independent of the document size. Of course, I noticed it in a larger file, but I can't upload it here. I have also tested it again in the Mac version, the error also occurs there. The error also exists before the current version. Quote Link to comment Share on other sites More sharing options...
Komatös Posted February 15, 2021 Share Posted February 15, 2021 Ich glaube, es ist weniger ein Fehler bei Affinity zu suchen, sondern beim Windows-Code vom exiftool. Quote AMD Ryzen 7 5700X | INTEL Arc A770 LE 16 GB | 32 GB DDR4 3200MHz | Windows 11 Pro 23H2 (22631.3296) AMD A10-9600P | dGPU R7 M340 (2 GB) | 8 GB DDR4 2133 MHz | Windows 10 Home 22H2 (1945.3803) Affinity Suite V 2.4 & Beta 2.(latest) Better translations with: https://www.deepl.com/translator Interested in a robust (selfhosted) PDF Solution? Have a look at Stirling PDF Life is too short to have meaningless discussions! Link to comment Share on other sites More sharing options...
JoelOwens Posted March 1, 2021 Author Share Posted March 1, 2021 Still buggy in version 1.9.1.979 Quote Link to comment Share on other sites More sharing options...
JoelOwens Posted March 31, 2021 Author Share Posted March 31, 2021 Still buggy in version 1.9.2.1035 Quote Link to comment Share on other sites More sharing options...
Staff Chris B Posted June 17, 2021 Staff Share Posted June 17, 2021 I'm still waiting for feedback on this one @JoelOwens Quote How to format a bug report | Learning Resources | List of V2 FAQs | YouTube Tutorials Link to comment Share on other sites More sharing options...
Recommended Posts
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.