Blurring in case of resize to integer multiples

[NotMyFault]

Hi,

i created a 33x33 px rectangle pixel layer from a QR code.

when resizing this to integer multiples, e.g 66 or 99, it stays sharp, both in case of same h/w or different h/w.

When i reduce the opacity of edges, this totally differs: now the tile becomes totally blurry in most cases.

i would like to understand the reason why sharp/blurry depends on 1px edge being partially transparent.

 

2.1 iPad rendering bug.afphoto

[NotMyFault]

I have to correct my observation.

the blurriness at integer multiples gets triggered when:

• one side is not stretched above factor 2, the other is stretched by 2 or more

If both sides stretched by factor 2 or more, no blurriness occurs.

Transparent pixels are not a factor.

 

[Dan C]

Hi @NotMyFault,

Thanks for your report!

As I understand it, this is expected behaviour when resizing a pixel layer disproportionally with View Quality set to Bilinear.

In the desktop version under Settings > Performance you can change the View Quality to Nearest Neighbour, which stops the 'blurring' from being introduced at any re-size.

 
Unfortunately this option isn't currently available on iPad, the View Quality is always set to Bilinear and therefore this is expected.

I will be sure to add your 'vote' to our internal request to add the View Quality controls to the iPad version now.

I hope this helps

[NotMyFault]

Thanks, @Dan C

Getting feature parity on iPad would be great.

Don‘t forget to add my vote if there is an open request to get all resample methods internally for individual layers (move tool + rasterize).

Unfortunately, even if this behavior is „expected“ by Affinity, users need a way to get non-blurry results.

For those who stumble over this issue, here is a workaround: