nvidia-patch VS JBOPS

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

Maybe not with stock Plex, but Tautulli with the JBOPS scripts should be able to do it.

I've been running the killscript to stop 4K transcodes for years, and I've just noticed that it doesn't work any longer. When it's triggered, I get the following error in Tautulli logs:

I am attempting to limit stream auto play at night and I found this limiterr python script was the only option that seems to be available running on tautuilli.(https://github.com/blacktwin/JBOPS/blob/master/killstream/limiterr.py).

I recommend using Tautulli and this https://github.com/blacktwin/JBOPS/tree/master/killstream to automatically kill streams. Also configure it to reference https://mediaclients.wiki whenever it kills the stream so users know how to fix it.

What about this script https://github.com/blacktwin/JBOPS/blob/master/utility/merge_multiepisodes.py

Tautulli for monitoring and notifications, plus some scripts for "maintenance," such as killing 4K transcodes and stopping remote streams after they've been paused for X minutes. These are from the JBOPS repository.

Script: https://github.com/blacktwin/JBOPS/blob/master/reporting/streaming_service_availability.py

Unless someone has already created what you're looking for (JBOPS/reporting is a good initial place to look), you'll probably have to write something yourself that makes calls to Tautulli's API.