1.0.6: Aliasing when resizing

Is something not working like it should? Let us know.
User avatar

2018-01-23 22:04:12

This seems to be a new issue with 1.0.6.

In the original Pixelmator, in Photoshop, and in previous versions of Pixelmator Pro, it seemed like a low quality scaling algorithm (not quite nearest neighbour, but not much better) is used to generate a realtime preview while the user adjusts the scale parameters/handles, and then when the scale operation is completed a higher quality algorithm (bilinear? cubic?) is used to generate a great-looking result.

Now, when resizing a layer, I'm seeing really bad aliasing or sampling error that persists all the way through to export. It's almost as if the low-quality preview algorithm is also applied after the resizing operation is complete.

Original PNG:

Image

Scaled to 50% in Pixelmator 3.7, then exported to PNG:

Image

Scaled to 50% in Pixelmator Pro 1.0.6, then exported to PNG:

Image

Resizing in Pixelmator Pro used to be one of my favourite features, since it seemingly was done non-destructively. That was fantastic, and I'd love for that behaviour to persist into the future. I just want to make sure that when it comes time to do a final render at the target size, that a high quality scaling algorithm is used.
User avatar

2018-01-24 17:13:02

Thank you so much for bringing this to our attention!
User avatar

2018-02-01 20:54:26

Just in case this got overlooked — it seems like this issue is still present in 1.0.7
User avatar

2018-02-02 06:01:27

Sorry for not replying sooner — this is a known issue, the current resampling algorithm isn't working quite as well as we'd hoped, so we'll be improving it, although the changes might have to wait a short while as we're planning to add additional resampling algorithms (e.g. nearest neighbor and Lanczos) to Pixelmator Pro. In any case, thanks for keeping us on our toes!
User avatar

2018-02-03 17:47:00

Excellent. Thanks for the response!
User avatar

2018-07-23 20:29:45

I just wanted to bump this topic, as this issue is still present in 1.1.2. It's the only thing holding me back from using Pixelmator Pro full-time.