Order of operations
A pipeline means exactly the operations you wrote, in the order you wrote them, and Hokusai never reorders them. For most pairs of operations the order does not matter; for some it changes the picture, the size, or whether the result is even valid. Each page below runs both orders on the same input and shows what Hokusai produced. Only orders with an observable difference are covered, not every permutation.
| Question | Page | Verdict |
|---|---|---|
| Blur then shrink, or shrink then blur? | Resize, blur & sharpen | Different pixels: do both at the final scale, shrinking first |
| Sharpen before or after resizing? | Resize, blur & sharpen | After; the same sharpen is about three times weaker if it comes first |
autoOrient before or after resize? |
Orientation and resize | Before; otherwise width and height are the wrong way round |
rotate then flatten, or flatten then rotate? |
Flatten before JPEG | Flatten last, or JPEG paints the new corners black |
extend then trim, or trim then extend? |
Trim and extend | Different sizes: trim removes padding added before it |
Composite then resize, or resize then composite? |
Composite order | Different logo size; blur after compositing blurs the logo |
| Where does the encoder go? | Encoder position | Anywhere: byte-identical; the last one wins |
extract before or after resize? |
Crop & canvas | Same numbers, different pixels |
The rule of thumb
Section titled “The rule of thumb”- Orient first (
autoOrient()), so width and height mean what they say. - Reduce next: crop to the region you want, then
resize. Work done before a large reduction is partly thrown away. - Adjust at the final size: blur, sharpen, tone, colour.
- Compose and flatten last, then choose the encoder and metadata policy (their position is free).
Exceptions exist and are on the pages above; the examples run in CI, so the results shown are what the documented release produces.