Jump to content

Affinity Publisher Original DPI Shows Incorrect


Recommended Posts

Hello, I have just started using Affinity Publisher and am loving it. I'm just curious why the original dpi is showing incorrectly in the resource manager? It shows as 72dpi when clearly my image is 300dpi. Attached screenshots from AfPub vs Photoshop.

 

Thank you!

 

E43F17FC-3177-4268-9CF5-12C773C5D697.png

1C443402-4557-4D97-A26E-AE871DD18F01.png

Edited by Mojo1313
Updated screenshots
Link to comment
Share on other sites

How did you get your original image into APublisher? Copy/Paste over Clipboard? Use Place Image Tool or Picture Frame.

Affinity Store (MSI/EXE): Affinity Suite (ADe, APh, APu) 2.5.5.2636 (Retail)
Dell OptiPlex 7060, i5-8500 3.00 GHz, 16 GB, Intel UHD Graphics 630, Dell P2417H 1920 x 1080, Windows 11 Pro, Version 23H2, Build 22631.4317.
Dell Latitude E5570, i5-6440HQ 2.60 GHz, 8 GB, Intel HD Graphics 530, 1920 x 1080, Windows 11 Pro, Version 23H2, Build 22631.4317.
Intel NUC5PGYH, Pentium N3700 2.40 GHz, 8 GB, Intel HD Graphics, EIZO EV2456 1920 x 1200, Windows 10 Pro, Version 21H1, Build 19043.2130.

Link to comment
Share on other sites

In addition to the above questions, check your document DPI setting.
If you place a 300 DPI image into a 72 DPI document the image will be shown as 72 DPI.
In other words, the placed image – not drag-placed, just click to place – takes on the DPI of the document.
See attached image.

Screenshot 2021-06-05 124530.png

Link to comment
Share on other sites

4 hours ago, Lagarto said:

I am not sure if this is a bug but a JPG file that has nominal resolution marked as e.g. 300dpi {...} will always be shown having 72dpi as original DPI in the Resource Manager, disregarding the document DPI.

This does not seem to be happening in the Mac version, at least according to a very quick test I just did. I created a simple test document @300DPI in AP & exported it to JPEG. I then placed it into a 72DPI APub doc via a single click, so it came in at a nominal 72 DPI. However, the Resource Manager shows its Original DPI at 300.

Confusingly though, if I select the placed image, resize it, & then from the context toolbar use the popup button "Original Size" it reverts to 72 DPI.

300DPI test.zip includes the JPEG & APub documents I used. 

All 3 1.10.8, & all 3 V2.5.5 Mac apps; 2020 iMac 27"; 3.8GHz i7, Radeon Pro 5700, 32GB RAM; macOS 10.15.7
A
ll 3 V2 apps for iPad; 6th Generation iPad 32 GB; Apple Pencil; iPadOS 15.7

Link to comment
Share on other sites

5 hours ago, Lagarto said:

I am not sure if this is a bug but a JPG file that has nominal resolution marked as e.g. 300dpi will always be shown having 72dpi as original DPI in the Resource Manager, disregarding the document DPI.

Not for me, on Windows:

image.png.f435ad73ddecacb31a9e83cd31605bad.png

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

Link to comment
Share on other sites

4 minutes ago, Lagarto said:

I noticed that if the JPG is exported by Affinity Photo, Affinity Publisher Resource Manager reads the DPI correctly, so obviously the resolution data can be written in multiple ways. However on Windows the system does read "original DPI" saved by Photoshop correctly. It reads the same data correctly also from a JPG file saved by Affinity Photo, as does Photoshop (both versions CS6 and 2021). It seems that Affiniity apps cannot read this alternative method of saving "original DPI" in a JPG file.

Please share your file.

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

Link to comment
Share on other sites

1 hour ago, Lagarto said:

Anyway, here goes (zipped):

FWIW, if I open your 300dpi.jpg in AD & export it back to a renamed JPEG file, APub's Resource Manager correctly identifies its original DPI as 300. Placing your file directly in APub shows its original DPI as 72.

The only thing I can see that is different between them using Preview.app's Inspector is the AD export includes JFIF density data:

673227169_JFIFdata.jpg.67e5be1a0e859d272703ce786febf810.jpg

Your original does not show a JFIF info category, so my guess is that is what APub is looking for.

All 3 1.10.8, & all 3 V2.5.5 Mac apps; 2020 iMac 27"; 3.8GHz i7, Radeon Pro 5700, 32GB RAM; macOS 10.15.7
A
ll 3 V2 apps for iPad; 6th Generation iPad 32 GB; Apple Pencil; iPadOS 15.7

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.