nvidia-patch VS FidelityFX-FSR

This can be patched out. https://github.com/keylase/nvidia-patch

NVIDIA Corporation GA106 [GeForce RTX 3060] and I applied the patch here https://github.com/keylase/nvidia-patch

> CUDA, and pretty much all optimization(hacks) done to run games better

And arbitrary limitations implemented at the driver level to force you to purchase their enterprise GPUs, see https://github.com/keylase/nvidia-patch#nvenc-and-nvfbc-patc...

Nvidia has no motivation to make a consumer card with lots of VRAM, that's basically the only (relevant) separator between the GeForce family and the Quadro lineup.

There are restrictions on NVENC streams with consumer cards, but that has been a solved problem for a while [0].

If they were to make a consumer card with more VRAM, it would immediately undercut their own Quadro/Tesla lineup, which cost substantially more. I don't see a reason for them to do it.

0: https://github.com/keylase/nvidia-patch

I have never had to do the session limit bump thing from the last link. I have a 3090 as well and simply did the initial unlock, which worked fine. I would reinstall fresh drivers from Nvidia, making sure you install the newest one that is supported by the unlock tool (536.40 as of this post, the GitHub for the patch has links to the drivers - https://github.com/keylase/nvidia-patch/tree/master/win)

Aren't these Quadro versions. The patch here. https://github.com/keylase/nvidia-patch supports Quadro versions of you click on the win clickable.

Second, the GPU. The GPU is probably as important as the CPU, and in some cases more important, and when we talk about GPUs we will primarily talk about Nvidia GPUs as they are officialy supported by the Plex team. NVIDIA GPUs are important for Plex hardware transcoding due to their dedicated video encoding/decoding units, superior performance, wide codec support, improved video quality, reduced CPU load, power efficiency. They offer a powerful hardware acceleration solution that can greatly enhance the transcoding capabilities of a Plex server. It's also important to note that Nvidia GPUs require a patch to unlock the number of HW transcoding streams. Dedicated GPUs are large pieces of hardware and have their place in desktop PCs. However, they can also be used with mini-PCs by using an external GPU enclosure.

As there's no NVENC patch available (yet) for the Beta driver branch - referring to this one: https://github.com/keylase/nvidia-patch - which can lift the limits of HW transcoding, I was now wondering a little, as I can see 5 (hw) streams on Plex, which actually shouldn't/cannot be the case no?

I haven’t done this yet but there is a patch on GitHub that removes the limitation for consumer GPUs. Makes lower end cards more attractive for this type of work

Also DLSS has pretty strict requirements in advertising, requiring nvidia logo & adverts on splash screens and give nvidia any rights to use your app in their own advertising. [0] It's certainly not "free". A completely night and day difference to FSR, which just uses MIT [1]

Lots of people online seem to believe both are "free", so the only reason why you wouldn't implement one is some back room deal. But in my experience, just getting everyone into the same room to sign off on things like that is hard.

[0] https://github.com/NVIDIA/DLSS/blob/main/LICENSE.txt

[1] https://github.com/GPUOpen-Effects/FidelityFX-FSR/blob/maste...

"IT doesn't work that way. DLSS may be a click in some Unreal Games, but custom engines? Yeah, no. You need to modify the code to implement it, which is PROHIBITED by the license Nvidia has you accept when you accept their SDK terms: https://github.com/NVIDIA/DLSS/blob/main/LICENSE.txt DLSS is not FOSS (Free and Open Source) like FSR. For comparison, FSR's license that lets you do whatever the hell you need to get it functioning in the game or improve performance: https://github.com/GPUOpen-Effects/FidelityFX-FSR/blob/master/license.txt Blame Nvidia for devs not wanting to touch non-free code and enter a legal agreement where they may be litigated down the line...for implementing a technology that SELLS Nvidia GPUs. It's literally like me threatening to sue you for bringing customers to my business. Again, blame Nvidia. By the way, they are also the one that sold you the feature, so let them be the one to implement it. I keep hearing Nvidia is a "god tier software company" but can't implement DLSS on the driver side? Somehow I don't buy it, especially when they release game-ready drivers anyway. And before someone brings up the BS argument it needs game data, anyone can find those memory addresses to get to the engine or they can ask. Considering they are Nvidia, don't think any game dev will keep silent about it or how to interface with their game if there are driver issues. EDIT: Also just so you know, XeSS is also under a similarly stupid license as DLSS XeSS License: https://github.com/intel/xess/blob/main/licenses/LICENSE.pdf Keep in mind this nugget from Intel's license: "No reverse engineering, decompilation, or disassembly..." Only issue is that games need to be DECOMPILED when DEBUGGED! "

FSR 1.0 is a simpler, open source implementation, isn't it?

Same Unity release had also included FSR (which are open-source shaders: one, two)

It’s also only part of FSR. If the point your trying to make is that FSR is just fancy lanzcos, it’s not. You can see for yourself if you’re able to read C code: https://github.com/GPUOpen-Effects/FidelityFX-FSR

I'd recommend using AMD's FSR1 instead for this. It's designed for games so it should run very fast and looks reasonably good (using Lanczos).

High quality upsampling is a shader to upscale lower render scale images into your native display resolution, for the implementation see: https://github.com/GPUOpen-Effects/FidelityFX-FSR

It goes one further too because FSR is open source so if you wanted (and knew what you were doing) you could go and look yourself https://github.com/GPUOpen-Effects/FidelityFX-FSR

Here's a rather concise explanation. And again, the source is available.

FSR source code is available on Github, so is much better documented FSR2.0.