Jump to content
You must now use your email address to sign in [click for more info] ×

Pixel misalignment in Publisher


Recommended Posts

Hi, based on an similar bug report form @DM1 I found that Publisher creates pixel layers that are misaligned by a fraction, despite transform panel states it is perfectly aligned (6 decimal digits chosen in preferences). 

The issue becomes visible when you switch to view mode pixel, or switch to Photo (Studio Link) which is always using pixel view mode.

Obviously, the grid (show grid) is slightly mis-placed when working with pixel art.

On desktop (create DIN A4 document, double-sided) it shows mis-alignment

on first page, to x axis.

on page 2+3, to y-axis (Continues on all later pages)

 

Affects MacOS and iPad. Can't test on windows.

 

Screenshot 2023-01-13 at 12.10.33.png

Screenshot 2023-01-13 at 12.11.29.png

misalignment.afpub

Edited by NotMyFault
Corrected which pages get affected

Mac mini M1 A2348 | Windows 10 - AMD Ryzen 9 5900x - 32 GB RAM - Nvidia GTX 1080

LG34WK950U-W, calibrated to DCI-P3 with LG Calibration Studio / Spider 5

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.

 

Link to comment
Share on other sites

My Math chops are not up to checking the Procedural texture you have there so I will only say that I think that the formula may be misleading you.

Mac Pro (Late 2013) Mac OS 12.7.4 
Affinity Designer 2.4.0 | Affinity Photo 2.4.0 | Affinity Publisher 2.4.0 | Beta versions as they appear.

I have never mastered color management, period, so I cannot help with that.

Link to comment
Share on other sites

13 minutes ago, Old Bruce said:

My Math chops are not up to checking the Procedural texture you have there so I will only say that I think that the formula may be misleading you.

You can spot the same issue even without PT filter, just use black rectangle on white background. PT filter helps to make this better visible. Just deactivate the filter in the file - same result.

Further tests show that the misalignment is mostly 1/3 or 2/3 of a pixel. Not exact 1/3, only almost.

 

Image below shows:

  • grid in red with 1/3px 
  • selected black rectangle, bounding box active in blue, perfectly pixel aligned
  • transform panel: perfectly pixel aligned
  • Document is 64x64 px, no bleed, no margin
  • 990476243_Screenshot2023-01-13at17_51_43.thumb.png.7b24ed7e11ca7f162922e8c60dab1001.png

 

 

 

 

Mac mini M1 A2348 | Windows 10 - AMD Ryzen 9 5900x - 32 GB RAM - Nvidia GTX 1080

LG34WK950U-W, calibrated to DCI-P3 with LG Calibration Studio / Spider 5

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.

 

Link to comment
Share on other sites

I am not seeing any misalignment. I did of course use a 1 pixel grid to check. The only way I can get anything like your screenshot is to have Pixels turned on as the View Mode  from the Designer Persona.

Mac Pro (Late 2013) Mac OS 12.7.4 
Affinity Designer 2.4.0 | Affinity Photo 2.4.0 | Affinity Publisher 2.4.0 | Beta versions as they appear.

I have never mastered color management, period, so I cannot help with that.

Link to comment
Share on other sites

1 hour ago, Old Bruce said:

I am not seeing any misalignment. I did of course use a 1 pixel grid to check. The only way I can get anything like your screenshot is to have Pixels turned on as the View Mode  from the Designer Persona.

Yeah, that is the essential precondition.

Mac mini M1 A2348 | Windows 10 - AMD Ryzen 9 5900x - 32 GB RAM - Nvidia GTX 1080

LG34WK950U-W, calibrated to DCI-P3 with LG Calibration Studio / Spider 5

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.

 

Link to comment
Share on other sites

Does it export the same way?

Microsoft Windows 10 Home (Build 19045)
AMD Ryzen 7 5800X @ 3.8Ghz (-30 all core +200mhz PBO); Mobo: Asus X470 Prime Pro
32GB DDR4 (3600Mhz); EVGA NVIDIA GeForce GTX 3080 X3C Ultra 12GB
Monitor 1 4K @ 125% due to a bug
Monitor 2 4K @ 150%
Monitor 3 (as needed) 1080p @ 100%

WACOM Intuos4 Large; X-rite i1Display Pro; NIKON D5600 DSLR

Link to comment
Share on other sites

On 1/13/2023 at 12:14 PM, NotMyFault said:

misalignment.afpub

It's the bleed.
The bleed must have an integer pixel value on document creation.
It doesn't even help if you change the bleed later, the pixel grid will remain offset.

Since the standard bleed is 3 mm, make it a habit to create every new document with 36 px bleed. Don't change it to non-integer values later, otherwise it will be off again.

See also 

 

MacBookAir 15": MacOS Ventura > Affinity v1, v2, v2 beta // MacBookPro 15" mid-2012: MacOS El Capitan > Affinity v1 / MacOS Catalina > Affinity v1, v2, v2 beta // iPad 8th: iPadOS 16 > Affinity v2

Link to comment
Share on other sites

26 minutes ago, loukash said:

It's the bleed.
The bleed must have an integer pixel value on document creation.
It doesn't even help if you change the bleed later, the pixel grid will remain offset.

Since the standard bleed is 3 mm, make it a habit to create every new document with 36 px bleed. Don't change it to non-integer values later, otherwise it will be off again.

See also 

 

I zeroed out bleed while creating the document (not later), the misalignment happens anyways.

Next, the misalignment is only on certain pages (namely facing pages, excluding first and last), whereas bleed is on all pages.

Mac mini M1 A2348 | Windows 10 - AMD Ryzen 9 5900x - 32 GB RAM - Nvidia GTX 1080

LG34WK950U-W, calibrated to DCI-P3 with LG Calibration Studio / Spider 5

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.

 

Link to comment
Share on other sites

Just now, NotMyFault said:

I zeroed out bleed while creating the document (not later), the misalignment happens anyways.

Hm, worked for me: Created an RGB A4 doc with 36 px bleed, copied your two rectangles, aligned them to integer pixels as well, and all is perfect.

apu2_misalignment_recreated_fixed.afpub

MacBookAir 15": MacOS Ventura > Affinity v1, v2, v2 beta // MacBookPro 15" mid-2012: MacOS El Capitan > Affinity v1 / MacOS Catalina > Affinity v1, v2, v2 beta // iPad 8th: iPadOS 16 > Affinity v2

Link to comment
Share on other sites

I will try again with 36 instead of 3.

Mac mini M1 A2348 | Windows 10 - AMD Ryzen 9 5900x - 32 GB RAM - Nvidia GTX 1080

LG34WK950U-W, calibrated to DCI-P3 with LG Calibration Studio / Spider 5

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.

 

Link to comment
Share on other sites

Same result. The misalignment is about 1/3px. So the first and every 3rd double-page is almost aligned, the next off by 1/3, the next off by 2/3. To be repeated.

No matter if bleed is 0 or 36px.

I put a rectangle into the master page.

bleed 36.afpub

Mac mini M1 A2348 | Windows 10 - AMD Ryzen 9 5900x - 32 GB RAM - Nvidia GTX 1080

LG34WK950U-W, calibrated to DCI-P3 with LG Calibration Studio / Spider 5

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.

 

Link to comment
Share on other sites

side bug: Publisher forgets to update the "Window" Menu with given name after save as.

 

Screenshot 2023-01-14 at 23.29.49.png

and with Photo persona:

145143147_Screenshot2023-01-14at23_31_17.thumb.png.3d70aa7bec1986818c2b4a57939c59b3.png

Mac mini M1 A2348 | Windows 10 - AMD Ryzen 9 5900x - 32 GB RAM - Nvidia GTX 1080

LG34WK950U-W, calibrated to DCI-P3 with LG Calibration Studio / Spider 5

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.

 

Link to comment
Share on other sites

In any case, this bleed pixel grid offset is a serious bug that needs to be fixed a.s.a.p.!

Similar (same?) bug also affects afpub docs with pages with multiple sizes. If you have an A4 page and you add an A5 page, the latter will be off the pixel grid because its absolute origin is at the left-hand side of the A4 page… :/ 

That all was already in APu v1.

Ideally, each page should have its own "absolute" pixel grid starting at the page origin, not at the bleed origin.

MacBookAir 15": MacOS Ventura > Affinity v1, v2, v2 beta // MacBookPro 15" mid-2012: MacOS El Capitan > Affinity v1 / MacOS Catalina > Affinity v1, v2, v2 beta // iPad 8th: iPadOS 16 > Affinity v2

Link to comment
Share on other sites

I have an idea what could cause all this.

In Designer, when you add artbosrds, you can place them on fractional positions. But the grid shows relative positions to the dartboard origin, so pixel alignments gets off.

Interestingly, only in y-axis.

But if you switch to pixel view, you see the misalignment damage in both axis.

 

Pages and Artboards are twins in may aspects, similar like symbols, groups and Layer layers.

 

Something is totally messed up with Pages, Artboards and grid.

 

1445961040_Screenshot2023-01-14at23_35_38.thumb.png.56b8c3471843633895917148e5638b59.png

1375743097_Screenshot2023-01-14at23_35_44.thumb.png.c06e588caf61955212011fefc4c930f5.png

1090631320_Screenshot2023-01-14at23_41_13.thumb.png.13125612a9ae55a702bfcdb61cf80c03.png

Mac mini M1 A2348 | Windows 10 - AMD Ryzen 9 5900x - 32 GB RAM - Nvidia GTX 1080

LG34WK950U-W, calibrated to DCI-P3 with LG Calibration Studio / Spider 5

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.

 

Link to comment
Share on other sites

6 minutes ago, NotMyFault said:

bleed 36.afpub

Aha!
Now I see it: The misalignment starts on page 2!
There is a vertical misalignment between spreads!

My in the meantime three-quarter-educated guess is that the pixel grid origin is on spread 1, but the vertical gap between spreads is not an integer pixel value.
Same in APu v1.

WTF?

MacBookAir 15": MacOS Ventura > Affinity v1, v2, v2 beta // MacBookPro 15" mid-2012: MacOS El Capitan > Affinity v1 / MacOS Catalina > Affinity v1, v2, v2 beta // iPad 8th: iPadOS 16 > Affinity v2

Link to comment
Share on other sites

And here's your "not exact 1/3, only almost" offset:
The vertical gap between spreads is exactly 354.330709 px = exactly 30 mm @300dpi… :86_crying_cat_face:

MacBookAir 15": MacOS Ventura > Affinity v1, v2, v2 beta // MacBookPro 15" mid-2012: MacOS El Capitan > Affinity v1 / MacOS Catalina > Affinity v1, v2, v2 beta // iPad 8th: iPadOS 16 > Affinity v2

Link to comment
Share on other sites

So… to align your objects to pixel grid on all pages:

  • always round your page sizes, bleeds and margins to integer pixels: A4@300 dpi = 2480×3508 px
  • on page 2, your spread origin must be y=0.669291 px to align, then use integer values in Transform panel
  • on page 3, your spread origin must be… er, what's the math…? O.o 3508-0.669291+354.330709=3861.661418 … uhh… 1-0.661418  = y=0.338582 px
  • on page 3, your spread origin must be…

Nurse! Nurse!!! My brain hurts! Nuuuuurse!!!

MacBookAir 15": MacOS Ventura > Affinity v1, v2, v2 beta // MacBookPro 15" mid-2012: MacOS El Capitan > Affinity v1 / MacOS Catalina > Affinity v1, v2, v2 beta // iPad 8th: iPadOS 16 > Affinity v2

Link to comment
Share on other sites

Either that nutty math above, or this deranged one:

h = initial page height in mm
s = distance from spread 1 top to spread 2 top in pixel
o = page offset in pixel
y = new page height aligned to pixel grid in mm

s = ( h + 30 ) / 25.4 * dpi
o = frac(s)
y = h - o
[px]

Perhaps someone more math savvy than me can translate it into a proper equation.

I need sleep… :86_crying_cat_face:

Edited by loukash
en.wikipedia.org/wiki/Fractional_part to the rescue

MacBookAir 15": MacOS Ventura > Affinity v1, v2, v2 beta // MacBookPro 15" mid-2012: MacOS El Capitan > Affinity v1 / MacOS Catalina > Affinity v1, v2, v2 beta // iPad 8th: iPadOS 16 > Affinity v2

Link to comment
Share on other sites

That's not a real surprise since "misalignment" of Artboards in Designer cause the same problems with pixel layouts. I'd say it's an issue with pixel preview as I have a few accuracy issues with it on my current build, however, I checked export and though hard to see with the first file, it also effects output. So I guess pages have unseen document-wide positioning relative to the pixel grid... similar to artboards.

Microsoft Windows 10 Home (Build 19045)
AMD Ryzen 7 5800X @ 3.8Ghz (-30 all core +200mhz PBO); Mobo: Asus X470 Prime Pro
32GB DDR4 (3600Mhz); EVGA NVIDIA GeForce GTX 3080 X3C Ultra 12GB
Monitor 1 4K @ 125% due to a bug
Monitor 2 4K @ 150%
Monitor 3 (as needed) 1080p @ 100%

WACOM Intuos4 Large; X-rite i1Display Pro; NIKON D5600 DSLR

Link to comment
Share on other sites

25 minutes ago, loukash said:

someone more math savvy than me can translate it into a proper equation

y = h - { ( h + 30 ) / 25.4 * dpi } px

Would that be mathematically correct based on en.wikipedia.org/wiki/Fractional_part?
(Disclosure: my last math lesson was around 1982 or so…)

12 minutes ago, debraspicher said:

That's not a real surprise since "misalignment" of Artboards in Designer cause the same problems with pixel layouts.

That's true.
The major difference being that we can align artboards to the absolute pixel grid ourselves, based on the left-most and top-most artboards' origin.
But we have no influence on the gap between Publisher spreads. It remains firm at 30 mm.

It could be worked around if APu would accept non-integer DPI but that doesn't seem to be the case: according to my math [cough, cough], e.g. 299.72 DPI should theoretically work because then the 30 mm gap would be integer 354 pixels. 

MacBookAir 15": MacOS Ventura > Affinity v1, v2, v2 beta // MacBookPro 15" mid-2012: MacOS El Capitan > Affinity v1 / MacOS Catalina > Affinity v1, v2, v2 beta // iPad 8th: iPadOS 16 > Affinity v2

Link to comment
Share on other sites

10 hours ago, loukash said:

y = h - { ( h + 30 ) / 25.4 * dpi } px

Would that be mathematically correct based on en.wikipedia.org/wiki/Fractional_part?

Alright, it seems that curly brackets aren't necessarily telling clearly what what to do with their content, so the clearer equation would likely be:

y = h - frac( ( h + 30 ) / 25.4 * dpi ) px

Where h = initial page height in mm.

MacBookAir 15": MacOS Ventura > Affinity v1, v2, v2 beta // MacBookPro 15" mid-2012: MacOS El Capitan > Affinity v1 / MacOS Catalina > Affinity v1, v2, v2 beta // iPad 8th: iPadOS 16 > Affinity v2

Link to comment
Share on other sites

Another day, another workaround, one that works in APu v1 for sure (I will have to reboot the Mac to Catalina to test it in v2):

  1. Select your New Document preset, assuming you want DPI ~300
  2. Change units to Pixel
  3. Round all values to the next integer pixel
  4. 1 page only! do not create multiple pages yet!
  5. Once the blank document is created, go to Document Setup > DPI: 299.72 – now it will stick, unlike in the New Document dialog.
  6. Add as many pages you wish (tested with 1000).
  7. As long as you have Force pixel alignment active, all objects should be pixel aligned even on page 1000.
  8. You can now switch document units back to mm/inch/whatever.
    Note that objects with integer mm values logically won't always fully align to the pixel grid. 
    But 10 mm = 118 px, so alignment and sizes in 5 mm steps will still snap to the grid.

The trick:
DPI 299.72 will set the firm 30 mm vertical gap between spreads to integer 354 px.
Thus since every page now has an integer pixel height as well, fractions of pixels won't add up. (Well, perhaps there might be a minor rounding error if you line up like 10000 spreads DIN A0…)

If you need/want to align to integer 1 mm, then you should apply DPI 304.8 in step 5 – i.e. the spread gap will then be integer 360 px.
1 mm @ 304.8 DPI = 12 px, so you can easily align in 0.25 mm steps.

MacBookAir 15": MacOS Ventura > Affinity v1, v2, v2 beta // MacBookPro 15" mid-2012: MacOS El Capitan > Affinity v1 / MacOS Catalina > Affinity v1, v2, v2 beta // iPad 8th: iPadOS 16 > Affinity v2

Link to comment
Share on other sites

On iPad, APu 2 doesn't accept fractional DPI values, it will round up or down.
So the only workaround to keep pixel grid alignment over multiple spreads is to use integer DPI that will convert those stupid 30 mm into integer pixels.
And there are not many candidates. The math is fairly simple, and one of those values will surely look familiar:

DPI 127
DPI 254
DPI 381

Yep, DPI 254 should look familiar to you because 1 inch = 25.4 mm.

Serif, please fix this disaster!

MacBookAir 15": MacOS Ventura > Affinity v1, v2, v2 beta // MacBookPro 15" mid-2012: MacOS El Capitan > Affinity v1 / MacOS Catalina > Affinity v1, v2, v2 beta // iPad 8th: iPadOS 16 > Affinity v2

Link to comment
Share on other sites

7 hours ago, loukash said:

(I will have to reboot the Mac to Catalina to test it in v2)

Bad news.
Same as on iPad, the DPI field rounds fractions to integer. So the only DPI values that will keep all pages aligned to pixel grid are 127, 254, 381, 508, 635, 762 etc.

Or go back to v1 where you can enter fractional DPI as per my workaround above.

MacBookAir 15": MacOS Ventura > Affinity v1, v2, v2 beta // MacBookPro 15" mid-2012: MacOS El Capitan > Affinity v1 / MacOS Catalina > Affinity v1, v2, v2 beta // iPad 8th: iPadOS 16 > Affinity v2

Link to comment
Share on other sites

Now for some good news:

For a print workflow, it seems that at least some of the misalignment is only a display issue:
If I export a PDF/X-4 or Press Ready from a page that appears totally off pixel grid in Photo persona, all "numerically" aligned pixel objects are aligned nonetheless, incl. pixel brush strokes.

Not so if I export to bitmap format, or PDF/X-1, X-3: rasterized vector objects will be off the pixel grid like on the display preview.

MacBookAir 15": MacOS Ventura > Affinity v1, v2, v2 beta // MacBookPro 15" mid-2012: MacOS El Capitan > Affinity v1 / MacOS Catalina > Affinity v1, v2, v2 beta // iPad 8th: iPadOS 16 > Affinity v2

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.