Steps Posted December 5, 2018 Share Posted December 5, 2018 EDIT: Nevermind. I read the other topic again more carefully and figured out that this is already a known bug to the devs. --- I have an image which is saved by Photoshop with 301 DPI. This is properly written to the EXIF which I can see with both exifutil and windows file info. If I drag that image into Publisher 1.7.0 192 (Win 10) or use the "File" -> "Place..." option that image is imported as 72 DPI. The document itself is also 301 DPI. The image is the pages background and I would not expect to have it resized. Is there a setting that fixes all images at 72 DPI or is Publisher just not reading metadata? EDIT: This may be the same as this topic, but that got a bittle long and confusing. So please make it short: Is this working as intented or is it considered to be a bug? Windows 10 Pro x64 (1903). Intel Core i7-9700K @ 3.60GHz, 32 GB memory, NVidia RTX 2080 Affinity Photo 1.7.2.471, Affinity Designer 1.7.2.471, Affinity Publisher 1.7.2.471 Link to comment Share on other sites More sharing options...
Steps Posted December 5, 2018 Author Share Posted December 5, 2018 And a related question: Is there an option to set a target DPI for scaling the image by that? Windows 10 Pro x64 (1903). Intel Core i7-9700K @ 3.60GHz, 32 GB memory, NVidia RTX 2080 Affinity Photo 1.7.2.471, Affinity Designer 1.7.2.471, Affinity Publisher 1.7.2.471 Link to comment Share on other sites More sharing options...
Staff Sean P Posted December 7, 2018 Staff Share Posted December 7, 2018 Hi Steps, Thanks for letting us know! As you said this is a known issue with development, so should hopefully be sorted soon! With regards to setting a target DPI for scaling the image, that is not currently possible. It is possible to place a TIFF files using it's DPI with the Image Placement Tool by just clicking instead of dragging out, however this is currently broken for JPGs so I will get that bumped with development! Thanks again! Steps 1 Link to comment Share on other sites More sharing options...
Steps Posted December 13, 2018 Author Share Posted December 13, 2018 Still broken in 1.7.0.206 Windows 10 Pro x64 (1903). Intel Core i7-9700K @ 3.60GHz, 32 GB memory, NVidia RTX 2080 Affinity Photo 1.7.2.471, Affinity Designer 1.7.2.471, Affinity Publisher 1.7.2.471 Link to comment Share on other sites More sharing options...
walt.farrell Posted December 13, 2018 Share Posted December 13, 2018 If the release notes did not indicate something was fixed, it's a reasonable guess/assumption that it wasn't -- 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.1.2, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.1.1 Link to comment Share on other sites More sharing options...
Steps Posted December 13, 2018 Author Share Posted December 13, 2018 3 minutes ago, walt.farrell said: If the release notes did not indicate something was fixed, it's a reasonable guess/assumption that it wasn't Yes, I know, but sometimes things get fixed without mention and as I explicitely tested this again I wanted to bump it. Not that they forget about it. Windows 10 Pro x64 (1903). Intel Core i7-9700K @ 3.60GHz, 32 GB memory, NVidia RTX 2080 Affinity Photo 1.7.2.471, Affinity Designer 1.7.2.471, Affinity Publisher 1.7.2.471 Link to comment Share on other sites More sharing options...
Recommended Posts