Jump to content

Recommended Posts

Posted

KDP demands I make my front cover exactly  7.197 inches by 10.236 inches due to the page count and other book print factors. 

When I try to create this document size in Affinity Photo, it lets will let me do 7.197 x 10.234 in, or 7.198.

If I unclick the lock button, I thought I could choose any size, but though it will let me set any size, when I click "Resize," and then reopen the document resize panel again, I see that the document is still at 10.234 or 7.198.

How can I set the document size to what I need?

Screen Shot 2022-04-03 at 8.09.29 PM.png

Screen Shot 2022-04-03 at 8.09.18 PM.png

Posted

Can you give us a screen recording of this 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.4.1, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.4

Posted

FWIW, on my Mac when I set the decimal places for unit types for inches to 4 (in Preferences > User Interface), after setting the canvas size to 7.197 X 10.236 inches, & checking the size via Document > Resize Canvas I get this:

1860863782_ResizeCanvas.jpg.d4550b9d5a1a0c53e8f9c5e4f2d1caae.jpg

It doesn't matter if I change it there to 7.1970 X 10.2360; each time I open the resize dialog it reverts to 7.1967 X 10.2367 in. I get similar results using Document > Resize Document.

So my guess is this is caused by the actual document/canvas size being constrained to integer pixel values.

All 3 1.10.8, & all 3 V2.6 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

Posted
55 minutes ago, R C-R said:

So my guess is this is caused by the actual document/canvas size being constrained to integer pixel values.

I thought so too, but I hid the post, because in the first screenshot you can see that the pixel values are not integer.

Affinity Store (MSI/EXE): Affinity Suite (ADe, APh, APu) 2.5.7.2948 (Retail)
Dell OptiPlex 7060, i5-8500 3.00 GHz, 16 GB, Intel UHD Graphics 630, Dell P2417H 1920 x 1080, Windows 11 Pro, Version 24H2, Build 26100.2605.
Dell Latitude E5570, i5-6440HQ 2.60 GHz, 8 GB, Intel HD Graphics 530, 1920 x 1080, Windows 11 Pro, Version 24H2, Build 26100.2605.
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.

Posted
10 minutes ago, Pšenda said:

because in the first screenshot you can see that the pixel values are not integer.

The first screenshot doesn't show px values at all. It shows inches, with decimal places that are being rounded.

Can you explain about the non-integer pixel values a bit more?

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

Posted
5 minutes ago, walt.farrell said:

The first screenshot doesn't show px values at all.

image.png.1ab8f22e3e387e266f39f04727350cad.png

Affinity Store (MSI/EXE): Affinity Suite (ADe, APh, APu) 2.5.7.2948 (Retail)
Dell OptiPlex 7060, i5-8500 3.00 GHz, 16 GB, Intel UHD Graphics 630, Dell P2417H 1920 x 1080, Windows 11 Pro, Version 24H2, Build 26100.2605.
Dell Latitude E5570, i5-6440HQ 2.60 GHz, 8 GB, Intel HD Graphics 530, 1920 x 1080, Windows 11 Pro, Version 24H2, Build 26100.2605.
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.

Posted

Affinity lets you happily create documents with fractional pixel sizes (but >= 1 px).

Only if you export to a raster format like jpg png tiff etc it MUST export to integer pixel sizes, normally leading to rounding up and causing a thin light line by partial transparency on right and/or bottom edge.

 

PS: 

UI (on iPad) is slightly  inconsistent. 

  • create new insists of >= 1px
  • resize and crop allows any size, below 1.0
  • Crop allows 0, shows uneditable canvas (one bright pixel at any zoom level) and crashes if you try to resize again (after showing nan (not a number) for opposite axis in case of lock ratio)
  • Crop rounds up to integer px (even if snapping deactivated)
  • resize shows actual fractional px
  • Always happy to find new edge cases allowing to crash Photo 

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
53 minutes ago, NotMyFault said:

Affinity lets you happily create documents with fractional pixel sizes (but >= 1 px).

OK, but why does this happen on my iMac?

1. I created a new AP document with the same settings as shown in the OP's screen shot (7.197 inches X 10.236 inches at 400 DPI). (For testing purposes I created a preset to do that.)

408996461_KDPpreset.jpg.fc1f1aac72f7f804b106a2f81898ba5a.jpg

2. I opened Document > Resize Document 

3. I changed nothing & did not click Resize but it now shows this:

1182795931_resizecanvas.jpg.1093da3be4f9e4e8a50ce4eb3300a1e0.jpg

If I do nothing else other than change the document units popup to pixels, I get 2878 px X 4094 px for the Size: field (no fractional pixel values). Moreover, if I add a fill layer & rasterize it (not rasterize & trim), in the transform panel it shows the same 2878 px X 4094 px size.

However, if I add a rectangle snapped to the document spread, I get 2878.8 X 4094.4 px in the Transform panel.

The final result with both the rasterized fill & rectangle layer: What size canvas?.afphoto

But if after that I snap the now raster pixel layer to the document spread, it changes sizes to match the rectangle. So while the actual size of the document may include fractional pixel values, there is at least one bug in AP that 'prefers' whole pixels, so to speak.

All 3 1.10.8, & all 3 V2.6 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

Posted
6 hours ago, R C-R said:

OK, but why does this happen on my iMac?

Good question. I have no answer, will need to investigate deeper. As I updated my post later:

Affinity is full of UI quirks and inconsistencies, especially when it comes to those safety nets like

  • force pixel alignments (only for mouse input, not for numeric input in transform panel),
  • layer lock (locks movement  only)
  • or ensuring „not null“ (not checked when using crop + numeric input). 


Known issues:

  • grid on iPad in inches is wrong
  •  some unit conversions between inches and other units get wrong
     

So new document, resize, crop potentially all behave differently.

Maybe snapping has an impact? 

Tests to be done:

  • New document
  • Resize (resample on)
  • resize (resample off)
  • crop

To be run multiple times with variants:

  1. Numeric input by keyboard
  2. numeric input by mouse wheel
  3. mouse input, from low to high
  4. mouse input, from high to low
  5. snapping off
  6. snapping to whole pixels
  7. other snapping options

Then you can check again what happens at export (to raster files, as this enforces whole pixel, but the size given in preview maybe wrong)

Check if the size shown in UI is the actual size of the document after clicking apply.

 

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
10 hours ago, NotMyFault said:

Good question. I have no answer, will need to investigate deeper.

Please let me know if you get similar results for what I tried.

All 3 1.10.8, & all 3 V2.6 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

Posted
20 hours ago, R C-R said:

OK, but why does this happen on my iMac?

1. I created a new AP document with the same settings as shown in the OP's screen shot (7.197 inches X 10.236 inches at 400 DPI). (For testing purposes I created a preset to do that.)

408996461_KDPpreset.jpg.fc1f1aac72f7f804b106a2f81898ba5a.jpg

2. I opened Document > Resize Document 

3. I changed nothing & did not click Resize but it now shows this:

1182795931_resizecanvas.jpg.1093da3be4f9e4e8a50ce4eb3300a1e0.jpg

If I do nothing else other than change the document units popup to pixels, I get 2878 px X 4094 px for the Size: field (no fractional pixel values). Moreover, if I add a fill layer & rasterize it (not rasterize & trim), in the transform panel it shows the same 2878 px X 4094 px size.

However, if I add a rectangle snapped to the document spread, I get 2878.8 X 4094.4 px in the Transform panel.

The final result with both the rasterized fill & rectangle layer: What size canvas?.afphoto

But if after that I snap the now raster pixel layer to the document spread, it changes sizes to match the rectangle. So while the actual size of the document may include fractional pixel values, there is at least one bug in AP that 'prefers' whole pixels, so to speak.

Photo is lying, and simply cuts off any fractional digits in this UI box and all other places where the document size is displayed.

  • Activate snapping with snap to margins, draw a rectangle over the canvas, and see the dimensions on canvas and in transform panel.
  • When you open the same file in Designer, it shows the correct px dimensions including the fractional digits.

This leads to issues when you export, as Photo then rounds up to the next higher pixel number, and you never know why.

So in my view this is a critical UI bug and maybe the cause of multiple older bug reports.

You have no way to accurately inspect the document dimensions (with fractional digits) in Photo, all display is wrongly rounded down:

  • Resize UI
  • hand tool, display at window bar
  • Exif Metadata

But you can proof the issue with help of rulers:385333057_Photofractionaldocumentissue.thumb.png.2ae4721fad2341dea12865aa85891155.png zoom in to insane levels, navigate to the bottom right corner, and see that there are fractional pixels

 

bug report filed.

 

Screenshot 2022-04-05 at 20.58.50.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

Ignore. I misunderstood something about this, leading to an erroneous comment.

All 3 1.10.8, & all 3 V2.6 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

Posted
Just now, R C-R said:

Does that include the EXIF size data? It looks like from your screenshots that the (real?) size of the document has no fractional pixel dimensions, which is what I would expect from a photo shot with a camera.

No, just the other way round.

  • The document has the dimensions of exactly (German "," as decimal separator)
  •  image.png.366332c9d74d8c1ed99a6e5c3faa3f58.png
  • Affinity uses the rounded down value and puts it into the metadata (it is no camera photo. it as a from scratch created file).
  • Open it with designer and you see the actual size correctly.
  • 388047794_Screenshot2022-04-05at21_24_49.png.a516b4483b31d763c6b1e7b65cf91e9d.png
  • Objects like rectangles snapped to the margins show the exact size in transform panel
  • 1056116003_Screenshot2022-04-05at21_26_19.thumb.png.ed482becf3e3e73a34c9dd48b6045700.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
Just now, NotMyFault said:

No, just the other way round.

Please refer to my now edited post.

All 3 1.10.8, & all 3 V2.6 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

Posted
On 4/4/2022 at 3:15 AM, AntiqueFlaneur said:

KDP demands I make my front cover exactly  7.197 inches by 10.236 inches due to the page count and other book print factors. 

When I try to create this document size in Affinity Photo, it lets will let me do 7.197 x 10.234 in, or 7.198.

If I unclick the lock button, I thought I could choose any size, but though it will let me set any size, when I click "Resize," and then reopen the document resize panel again, I see that the document is still at 10.234 or 7.198.

How can I set the document size to what I need?

Screen Shot 2022-04-03 at 8.09.29 PM.png

Screen Shot 2022-04-03 at 8.09.18 PM.png

To answer your question:

  • Affinity correctly sets the file size for the internal document
  • The display of the file size unfortunately is wrong. Internally in Photo, all values are rounded down to multiples of whole integer numbers (of pixels).
  • It seems the inch values displayed in the UI box are calculated wrongly, too.
  • The main question is in which format do you export the data. In case of a raster format like PNG JPG TIFF or PDF with rasterised content, the exported document adds 1 px for x and y axis if there are non-zero fractional digits.
  • In case of vector format, you should check what happens. I assume the "round down or up to whole pixels" is a Photo only issue. Designer gives the correct dimensions including decimal digits.

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
4 minutes ago, NotMyFault said:
12 minutes ago, R C-R said:

Please refer to my now edited post.

Again, no.

What are saying "no" to? As I tried to explain, I misunderstood something you said, so as soon as I realized that I had done that (less than 5 minutes after I posted it) I replaced the entire comment with "Ignore" & a brief explanation of why I did that.

All 3 1.10.8, & all 3 V2.6 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

Posted
39 minutes ago, R C-R said:

What are saying "no" to? As I tried to explain, I misunderstood something you said, so as soon as I realized that I had done that (less than 5 minutes after I posted it) I replaced the entire comment with "Ignore" & a brief explanation of why I did that.

sorry, my browser did not update. I still got a mix of your old and new post, without noticing. Please disregard / hide your post. I already removed my wrong post.

 

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.

 

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.