Jump to content

Recommended Posts

Posted

Obviously there is a problem manifesting itself in the form of thin lines appearing at the edges of vector shapes under a couple of circumstances. (Affinity Designer v. 1.9.3 on a 2019 iMac running macOS 10.14.6)

Example 1 (Designer):

The edge of the rectangle clipping the circle (left side) remains faintly visible – in my experience this will be rendered as well (and so keep visible) if the artwork is exported to a pixel format file (e.g. JPG).
Note that when doing the (visually) same sort of "masking" using the same sort of elements by way of a subtractive compound these thin lines do apparently not appear.

Example 2a (Designer):

screenshot: area from artwork viewed in Designer (zoomed in at 400%) – no thin lines visible at borders

Example 2b (Designer):

screenshot: area from previous artwork after having been exported to JPG (100% quality); opended and viewed in Designer (zoomed in at 400%) – thin vertical lines visible where vector shapes touch (absolutely flush pixel perfect positioning!)

Example 2c (Designer):

screenshot: same as in 2b but flat black colour applied to the touching shapes (whereas in 2b there had been an additional 40% noise to the black)

Obviously it doesn’t matter if some noise has been applied to the individual objects’ fills thus possibly causing some sort of interference at the borders – those thin dividing lines continue appear with flat colours, too.

Other users report that this kind of problem also pops up with (seamless) patters where the pattern’s tiles touch. I haven't tried this but I guess they're right.

I've actually noticed those thin lines first when I started with Designer (v. 1.5, I think) quite some time ago – I had tried to get a first grip on masking then and at the time had hoped that they were some kind of temporary display glitch... However, when the lines kept showing up in the JPGs as well, which I exported from Designer I began to suspect that there might be something more to it.

I really hope, this problem will be adressed by Serif some time soon as it tends to severely hurt delicate artworks. Anybody looking just a bit closer will see these annoying lines, I'd think.

thin-lines-with-clipping-mask-but-not-with-compound_screen.png

in-designer_400%-zoom_screen.png

exported-to-jpg-100%-quality_400%-zoom_screen.png

no-noise-fills_exported-to-jpg-100%-quality_400%-zoom_screen.png

  • Staff
Posted

Hi Lorox,
To fix the first issue (when using clipping) go to Affinity Designer Preferences, Performance section and tick Use precise Clipping.
Regarding the other issues make sure all objects are pixel aligned (that is their X,Y coordinates and width and height are all integer values) and ideally check the image at 100% zoom. If pixel aligned correctly these (vertical and horizontal) lines shouldn't appear in the exported files.

Posted
5 minutes ago, MEB said:

Hi Lorox,
To fix the first issue (when using clipping) go to Affinity Designer Preferences, Performance section and tick Use precise Clipping.
Regarding the other makes sure all objects are pixel aligned (that is their X,Y coordinates and width and height are all integer values) and ideally check the image at 100% zoom. If pixel aligned correctly these (vertical and horizontal) lines shouldn't appear in the exported files.

Hi MEB,

thank you very much for replying this quick! The "Precise Clipping“ option had actually escaped my attention up to now. Anyway, this seems to work – so thanks again!

I had in fact made sure eventually that pixel alignment had been applied exactly as you suggest. Being someone who'd been designing mainly for print this hadn't seemed so obvious to me before, but when I encountered this issue I already thought precise pixel alignment would certainly be helpful and possibly minimize any rounding/antialiasing effects.

This having been said I also noticed that putting some element of the same or similar colour behind those elements’ boundaries also seems to make the lines disappear. But this might not be visually possible everywhere – so hopefully activating "Precise Clipping“ will do the job on a general basis.

  • 2 years later...
Posted

I noticed this same phenomena in AP. Turns out that if the image in a picture frame has the 'Page Box' set to 'TrimBox' these very thin lines will appear upon printing, but not show on-screen in AP. Neither the above suggestions nor any amount of cropping/editing in/out of app would remove them. Switching the Page Box to Minimum/Maximum Content fixed the issue.

@MEB This may be a bug. I'm running AP 2.5.5 on Win10.

Windows 10 Pro - AMD Ryzen 7 5700X 8-Core Processor 3.60 GHz - 32.0 GB Ram - NVIDIA GeForce GTX 1650

ASUS PA329CV

Canon iR-ADV C7565 III

Posted

A further bit of maddening info: Duplicating (select - enter) the object brings back the lines. All attributes appear to be duplicated correctly, yet the lines show back up.

Windows 10 Pro - AMD Ryzen 7 5700X 8-Core Processor 3.60 GHz - 32.0 GB Ram - NVIDIA GeForce GTX 1650

ASUS PA329CV

Canon iR-ADV C7565 III

Posted

Can you provide an example document?
 

Most thin lines are caused by fractional positions or size of layers, leading to antialiasing (partial alpha ) at edge pixels

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

Rasterize and crop fixed the problem.

I still consider this a bug. But it's probably super difficult to consistently reproduce.

Windows 10 Pro - AMD Ryzen 7 5700X 8-Core Processor 3.60 GHz - 32.0 GB Ram - NVIDIA GeForce GTX 1650

ASUS PA329CV

Canon iR-ADV C7565 III

Posted
18 minutes ago, NotMyFault said:

Can you provide an example document?
 

Most thin lines are caused by fractional positions or size of layers, leading to antialiasing (partial alpha ) at edge pixels

In this file the garland images are the issue. Hide all layers on the back cover except the garland and print as the lines are not visible on-screen (which is the more frustrating). The select the garland layer and rasterize/crop. Reprint and the lines are not there.

The garland images in this file are fractional size (px), but I have set them to just integers to no effect. So that does not seem to be the issue for this case.

The lines do not show on a print ready PDF export.

I am printing on a Canon C7565 IR-Adv.

2024_New_Years_Eve_Bulletin_bug.afpub

Windows 10 Pro - AMD Ryzen 7 5700X 8-Core Processor 3.60 GHz - 32.0 GB Ram - NVIDIA GeForce GTX 1650

ASUS PA329CV

Canon iR-ADV C7565 III

Posted
1 hour ago, NotMyFault said:

leading to antialiasing (partial alpha ) at edge pixels

If this is what's happening, we should have an optional 'hard edge' available to apply.

Windows 10 Pro - AMD Ryzen 7 5700X 8-Core Processor 3.60 GHz - 32.0 GB Ram - NVIDIA GeForce GTX 1650

ASUS PA329CV

Canon iR-ADV C7565 III

Posted

Activate pixel view mode to see it in the App before printing.

It is just the rectangle on x pis 37.5

IMG_2091.thumb.png.4f6eeb73051cd7e0cba7c33d2810da1a.png

correct it to 37.0 and the thin lines is gone.

IMG_2092.thumb.png.7e8c8396b25b1120b43689a0f1ecd48e.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
1 hour ago, Chris_06 said:

If this is what's happening, we should have an optional 'hard edge' available to apply.

For vector layers you can simply deactivate AA in blend options.

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

@NotMyFault Thank you for your kind help with this.

My apologies, I should have posted pics of the print copy to clarify where the lines are. Here are shots of print copies of the garland with and without associated layers. On my screen nearly infinite zoom still does not show them.

signal-2024-12-30-084106.thumb.jpeg.09a19579755b1403148374a3164ed23f.jpeg

signal-2024-12-30-084106_002.thumb.jpeg.bc86441ad06e0b06b967d442b5bd3036.jpeg

Windows 10 Pro - AMD Ryzen 7 5700X 8-Core Processor 3.60 GHz - 32.0 GB Ram - NVIDIA GeForce GTX 1650

ASUS PA329CV

Canon iR-ADV C7565 III

Posted

This is probably caused by usage of embedded images. Rasterizing all of then should solve the issue.

or simply use „merge visible“ on top of layer stack.

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
1 hour ago, NotMyFault said:

Rasterizing all of then should solve the issue.

That was pretty much my conclusion. It still seems a bit buggy, but this works fine.

Thanks again for your help. Have a great new year!

Windows 10 Pro - AMD Ryzen 7 5700X 8-Core Processor 3.60 GHz - 32.0 GB Ram - NVIDIA GeForce GTX 1650

ASUS PA329CV

Canon iR-ADV C7565 III

Posted
45 minutes ago, Chris_06 said:

That was pretty much my conclusion. It still seems a bit buggy, but this works fine.

Thanks again for your help. Have a great new year!

Have a great new year, too. Happy that you issue is solved

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.