This site may earn chapter commissions from the links on this page. Terms of use.

News broke (or "broke") yesterday on the fact that AMD'southward Fidelity FX Super Resolution (FSR) is derived from a Lanczos sharpening filter. The reason we put "bankrupt" in quotes is because AMD literally published statements in its own publicly available source code acknowledging this fact:

The scalar uses a modified fast approximation to the standard lanczos(size=2) kernel. EASU runs in a unmarried laissez passer, and so it applies a directionally and anisotropically adaptive radial lanczos. This is also kept as unproblematic as possible to accept minimum runtime.

The lanzcos filter has negative lobes, so by itself it will introduce ringing. To remove all ringing, the algorithm uses the nearest 2×2 input texels as a neighborhood, and limits output to the minimum and maximum of that neighborhood.

The simply reason there's even a whiff of controversy most this is because AMD told journalists that FSR represented a 100 pct in-house solution. There is a meaningful difference between "Developed 100 percent in-business firm" and "based on classic Lanczos scaling, but with various improvements." AMD should have been straightforward to journalists nigh what it had created.

AMD-FSR-Explanation

In that location is nothing intrinsically wrong with basing a sharpening arroyo on Lanczos filtering. Lanczos is a fairly common image upscaling algorithm that you lot'll run into used in applications similar AviSynth. It's commonly used considering it works well. This doesn't mean AMD didn't change it — the company made several changes to reduce ringing (over-sharpening artifacts) and to accelerate the application of the filter. It besides open up sourced its work so that developers could integrate information technology more easily.

As for whether or not this constitutes "upscaling," it absolutely does. Upscaling existed long before artificial intelligence was formally practical to the problem and Lanczos filters are some of the best options for upscaling that were by and large available. In the slider beneath I've upscaled 2 images using bicubic filtering and nearest neighbour filtering. That latter produces sharp edges and more than noticeable pixelation:

https://imgsli.com/NjQzMjk

AMD has positioned FSR equally an "respond" to DLSS. Whether you call back that'southward a fair label or non probably depends on how you view the ii technologies. At the highest level, both DLSS and FSR are intended to achieve the aforementioned goal, namely: Making your output look ameliorate without assessing a real penalty for doing so.

Nvidia created DLSS, an AI-based approach that leverages the tensor cores the company builds into its products. This capability is specific to Nvidia hardware. You can fairly debate that it represents a unique Nvidia value-add and that it will allow Nvidia GPUs to shift more than resources towards ray tracing and abroad from rasterization. You can also argue that it represents however another example of Nvidia deploying a technology intended to cater only to Nvidia users rather than doing anything for gaming and graphics equally a whole.

AMD has congenital a solution that works on AMD and Nvidia GPUs from 2016 forrard, including Pascal, Polaris, Turing, Ampere, Vega, Radeon VII, RDNA, and RDNA2. It was never going to be the same kind of solution every bit DLSS because DLSS is Nvidia-tuned and Nvidia-specific. They are two different approaches to the problem of improving graphics quality without paying a heavy punishment for doing so.

Reviews of FSR more often than not suggest that the technology gives a moderate frame rate boost even in its highest "Ultra Quality" detail mode. This kind of feature could be peculiarly useful for integrated gamers wanting to meliorate 720p output to something more like 1080p without paying the respective resolution penalty. AMD could have — and should have — been more than explicitly clear about what FSR was and what technology it was based on. Implementing a fast Lanczos filter with adaptations to forestall ringing is not nada. The feature was capable of standing on its own two feet.

Nosotros suggest enabling features similar FSR when they are available in whatever situation where you need to trade resolution for raw functioning and are hoping to claw back a little paradigm quality anyway.

Now Read:

  • AMD's New six-Core and 8-Core APUs Are a Bigger Bargain Than They Might Seem
  • AMD'south New 5700G, 5600G APUs Offer Solid Gaming Results, Plug Holes in Ryzen Lineup
  • AMD and Valve Are Building a Meliorate CPU Driver For Linux