- Posts: 30
- Joined: Sat Dec 17, 2022 12:08 am
- Real Name: Xander Wanlass
This may be a relatively niche issue, but it's a pretty important one in my opinion.
There is a massive difference between the implementation of Box filtering in the edit timeline vs Fusion.
I used the same image for both scaling methods, both scaled by a factor of 60 and rotated by 60 degrees.
In Fusion:
In the Edit Page:
Why does this matter? In Fusion, the Box filter is perfect for upscaling pixel art or screen capture footage. Bilinear and Bicubic upscaling cause gross, fuzzy pixels and weird diamond patterns. Nearest Neighbor works perfectly for scaling by whole integers (200%, 300%, 400%, etc.) but will introduce aliasing and cannot be smoothly transformed without causing pixel shift artifacts across rows and columns. Box retains the sharp pixels of Nearest Neighbor while also achieving the smooth transformations of bilinear/bicubic filtering. If that word vomit was too much, watch this video and skip to 1:02
Here's a quick demo:
I would love to see this fixed while 18.5 is still in beta. Thanks!
There is a massive difference between the implementation of Box filtering in the edit timeline vs Fusion.
I used the same image for both scaling methods, both scaled by a factor of 60 and rotated by 60 degrees.
In Fusion:
- In Fusion, box filtering behaves as expected. Pixels are square and there isn't any aliasing.
- Fusion.jpg (235.44 KiB) Viewed 660 times
In the Edit Page:
- In the Edit page, pixels get turned into rhombuses and it introduces aliasing. The strange thing is that it behaves as expected if all you do is upscale, not rotate.
- EditPage.jpg (215.04 KiB) Viewed 660 times
Why does this matter? In Fusion, the Box filter is perfect for upscaling pixel art or screen capture footage. Bilinear and Bicubic upscaling cause gross, fuzzy pixels and weird diamond patterns. Nearest Neighbor works perfectly for scaling by whole integers (200%, 300%, 400%, etc.) but will introduce aliasing and cannot be smoothly transformed without causing pixel shift artifacts across rows and columns. Box retains the sharp pixels of Nearest Neighbor while also achieving the smooth transformations of bilinear/bicubic filtering. If that word vomit was too much, watch this video and skip to 1:02
Here's a quick demo:
- A comparison of filters. Box, Nearest Neighbor, Bilinear, and Bicubic. This picture is extremely low resolution in order to easily demonstrate Nearest neighbor aliasing.
- FilterComparison.png (201.79 KiB) Viewed 660 times
I would love to see this fixed while 18.5 is still in beta. Thanks!
Windows 11, RTX 3070, Ryzen 5900x, 96 GB @ 3200MHz