Krita transform tool produces aliased edges

Develop Artists Feedback & Testing
23

:thinking:
On my side, for what I see on big 16000x16000px image (and also from traces I’ve put when I tried to understand the situation)

  • The first (fast) transform use workers to parallelize render from tiles (512x512 it seems)
    – It’s fast
    – UI is not blocked
    – We can see tiles being updated during process


    Example: rendering tiles is parallelized, UI is not blocked (can switch tab in docker for example)

  • The second (HQ) transform seems to not be parallelized
    – It’s slower than fats method (even using same bilinear algorithm)
    – UI is blocked
    – Transformed render is updated in one-shot after complete transform


    Example: rendering tiles is not parallelized, UI is blocked (can’t switch tab in docker for example)
    First we see here the bilinear being applied, can switch between tabs
    *Then, we see the progress bar in docker: HQ in on progress, can’t switch between tabs in UI and at the end, when all tiles are processed we see the HQ updated (used a nearest-neighbor here to see the difference)

Don’t worry, it was in case you had the answer :sweat_smile:
I spent most of my last saturday and part of sunday on it, without understanding it… :woozy_face:
You understand the situation here better than me so I know what is the feeling to be confused about how this work :sweat_smile:

Let’s wait for Dmitry feedback about this :slight_smile:

And the most important is the ability to fix the aliasing stuff, the parallelization is another subject I think.

Grum999