Plex hardware transcoding not working Quadro P2000

PMP? on which platform? It looked like you have Linux as the player platform?

PMS in ubuntu server 20.04, and PMP in Windows 10

This are the ones I am testing.
Also tested PMS in Windows 10, and same issues. Logical if the problem is coming from the player and not the server

I have checked the chrome browser speeds:

And this are my graphs from my PC:

The convert (maximum) which is the one that works for me is 78.2mbps, and my network and CPU seems to be pretty much stable. However when I change it to whatever resolution I pick from the list, it just doesn’t work, neither try to buffer.

I will see if someone from the Windows team can come look.

Thanks man :slight_smile:

Hey @ChuckPa were you able to check this with an engineer?

Hello,

I have been testing with lots of players:

PMP
Browsers (Internet Edge, Chrome, Safari, Firefox)
IPAD
Android
Kodi app
LG tv app

And what I can say is that, all browsers and PMP are the ones giving issues with this, the rest are just working fine, no issues at all.

Hey @ChuckPa I have seen these other errors on my PMP:

Jul 15, 2021 22:32:03.691 [2924] INFO - [Web] [QWebChannel(player.play)] response: {"errorCode":0,"result":null}
Jul 15, 2021 22:32:03.691 [2924] INFO - [Web] [QWebChannel(player.onPlaying)] undefined
Jul 15, 2021 22:32:04.698 [2924] DEBUG - [MPVEngine/mpv] ffmpeg: Mime-type: 'video/x-matroska'
Jul 15, 2021 22:32:04.698 [2924] DEBUG - [MPVEngine/mpv] demux: Trying demuxers for level=normal.
Jul 15, 2021 22:32:04.798 [2924] ERROR - [MPVEngine/mpv] ffmpeg: tls: Error in the pull function.
Jul 15, 2021 22:32:04.801 [2924] DEBUG - [MPVEngine/mpv] lavf: No format found, try lowering probescore or forcing the format.
Jul 15, 2021 22:32:04.801 [2924] DEBUG - [MPVEngine/mpv] demux: Trying demuxers for level=unsafe.
Jul 15, 2021 22:32:04.804 [2924] DEBUG - [MPVEngine/mpv] lavf: No format found, try lowering probescore or forcing the format.
Jul 15, 2021 22:32:04.806 [2924] DEBUG - [MPVEngine/mpv] cplayer: Opening failed or was aborted: https://192-168-1-17.7aef6ec71e88487c9b4a12cba92ab9df.plex.direct:32400/video/:/transcode/universal/start?hasMDE=1&path=%2Flibrary%2Fmetadata%2F366&mediaIndex=0&partIndex=0&protocol=http&fastSeek=1&directPlay=0&directStream=0&subtitleSize=100&audioBoost=100&location=lan&maxVideoBitrate=4000&directStreamAudio=0&session=zxmjj5c306exwid9sjxorslp&offset=3309&subtitles=auto&copyts=1&Accept-Language=es&X-Plex-Session-Identifier=r9x3sd3nfkeyy6s4uae5fen2&X-Plex-Chunked=1&X-Plex-Incomplete-Segments=1&X-Plex-Product=Plex%20for%20Windows&X-Plex-Version=1.33.0.2444-a220eae4&X-Plex-Client-Identifier=kkmjrzjptr7t72xmvwrmmrmi&X-Plex-Platform=windows&X-Plex-Platform-Version=10.0.19041&X-Plex-Sync-Version=2&X-Plex-Features=external-media%2Cindirect-media&X-Plex-Model=standalone&X-Plex-Device-Name=DESKTOP-6Q2C7R4&X-Plex-Device-Screen-Resolution=2560x1377%2C2560x1440&X-Plex-Client-Profile-Name=Plex%20Desktop&X-Plex-Token=xxxxxxxxxxxxxxxxxxxx&X-Plex-Language=es
Jul 15, 2021 22:32:04.807 [2924] ERROR - [MPVEngine] unrecognized file format.
Jul 15, 2021 22:32:04.807 [2924] DEBUG - [MPVEngine/QHotkeyInput] Playback state is now 'Stopped'
Jul 15, 2021 22:32:04.807 [2924] DEBUG - [MPVEngine/mpv] cplayer: finished playback, unrecognized file format (reason 4)
Jul 15, 2021 22:32:04.807 [2924] ERROR - [MPVEngine/mpv] cplayer: Failed to recognize file format.
Jul 15, 2021 22:32:04.807 [2924] INFO - [MPVEngine/mpv] cplayer: 
Jul 15, 2021 22:32:04.807 [2924] INFO - [Web] [QWebChannel(player.onError)] 4294967279
Jul 15, 2021 22:32:04.807 [2924] ERROR - [Web] [QTMedia(4)] A critical error occurred: 4294967279 Ocurrió un error desconocido (4294967279)
Jul 15, 2021 22:32:04.807 [2924] INFO - [Web] [QWebChannel(player.onBuffering)] disconnected
Jul 15, 2021 22:32:04.807 [2924] INFO - [Web] [QWebChannel(player.onSeekableRangesUpdate)] disconnected

Could it be related to that?
Is it just complaining because of an unrecognized video format?

I’ve been experiencing the exact same issues with the Windows 10 Plex app as well. Seen another thread where the Plex logs say the video connections to the PMS try on Loopback address. So will not work. My PMS is also a Windows 10 box and when I run the exact same Plex app on that box, everything works fine.

Edge browser to PMS works fine, Music in the Win 10 Plex app also works fine. So a bug in the Windows Plex App for sure. Plex on iOS works over wifi and 4g. So not an issues with the Plex Media Server at all, just the Win 10 Plex App.

Hello,

It seems to go a bit further, there is another post running for more than a year already:

With some people under P2000 having these same issues. However myself and them do have issues trying to change quality and transcode under a browser.
But once we lower the linux kernel, everything seems to work, just till 4 transcodes. So I guess multiple bugs might be going on

Hello all,

This is the new information I was able to get:

So after many troubleshooting, trying different OS, and different configs, I was able to identify that one of the main causes of this was because of running the system under legacy config in BIOS, and not EUFI. Once I changed to UEFI, I was able to ā€œsolveā€ the problem.

When I started to run in UEFI, I was able to achieve 8 4k transcodes in Plex for windows, without any issues, by using Debian 10 under proxmox. However, the same proxmox config, I was only able to get 4 4k transcodes on debian 20, the bug seems to still be happening on here.

Also I tried running debian and ubuntu under UNRAID, and the same problem for both, 4 4k transcodes on ubuntu, and 5 4k transcodes under debian.

About web browsers, whether I use debian/ubuntu, on UNRAID or Proxmox, the same issue still goes on. It seems like plex is hitting some sort of timeout or whatever, and killing the Nvidia process before it actually starts. At least now I am able to run all GPU power under debian 10 without issues.

With all this information, knowing that this is happening under this OS, can someone from plex team start taking this serious and help all the affected people that are under this situation?
@chrisallen @ChuckPa

Kind regards

There is a memory requirement issue in FFMEPG when using NVDEC (the Linux Nvidia Decoder) that causes more memory to be reserved than is actually required. We made a change on the PMS side to reduce this as much as we can, but without an upstream ffmpeg fix, it will likely still only be able to do 4-6 4K transcodes (you can look at the output of nvidia-smi to see how much GPU memory a transcode requires.

As things stand NVDEC decoder memory usage is still generally 30 to 50% higher than it should be, but nowhere near the 200%+ seen previously. The remaining excess is tracked upstream at trac.ffmpeg.org/ticket/9285 (reported by our own Transcoder developer)

1 Like

Hello,

Yep, I knew that you placed a fix for the GPU VRAM, I have been running nvidia-smi and nvtop, to check the status of the GPU during all my tests, but I am even having issues although the VRAM is not full, but maybe half of its capacity. However, it’s really weird that for example debian just runs fine, and ubuntu have some difficulties…
Also still having full browsers issues, with whatever SO I am using.
Also these issues with P2000 were reported already on mid 2020:

So I am not sure, that your FFMEPG fix, is the cause of all these.
If you could please investigate a bit, as you have a P2000, it would be great, as for sure, you will be also affected, on all things we all have been reporting.

Kind regards

Hello @chrisallen,

Were you able to dive deep more on this issue?

Kind regards

Sorry no I have not had a chance to look into this as I am busy with other tasks. What I can say in my P2000 is working just fine with Unraid 6.9.2 + pass though to Plex docker container. That is Linux kernel 5.10.28

When you say it is working fine, is that you are able to hit 100% VRAM usage? Are you able to run like 8 4k transcodes?

Hello,

So my last comment on the other post was:

Blockquote
So after many troubleshooting, trying different OS, and different configs, I was able to identify that one of the main causes of this was because of running the system under legacy config in BIOS, and not EUFI. Once I changed to UEFI, I was able to ā€œsolveā€ the problem.
When I started to run in UEFI, I was able to achieve 8 4k transcodes in Plex for windows, without any issues, by using Debian 10 under proxmox. However, the same proxmox config, I was only able to get 4 4k transcodes on debian 20, the bug seems to still be happening on here.
Also I tried running debian and ubuntu under UNRAID, and the same problem for both, 4 4k transcodes on ubuntu, and 5 4k transcodes under debian.
About web browsers, whether I use debian/ubuntu, on UNRAID or Proxmox, the same issue still goes on. It seems like plex is hitting some sort of timeout or whatever, and killing the Nvidia process before it actually starts. At least now I am able to run all GPU power under debian 10 without issues.
With all this information, knowing that this is happening under this OS, can someone from plex team start taking this serious and help all the affected people that are under this situation?
@chrisallen @ChuckPa

Now that debian 11 came out with new 5.10 kernel, I tested it and as I expected, now plex is just not working with more than 4 4k transcodes.
Is there any plan to start looking at this issue, as I said before it was reported quite time ago, and seems no one is take care of it…

Kind regards

Hi @el_pedriyo What happens when you try to start a 5th 4K transcode? Is there some performance issue or something more serious? Either way, can you describe what happens and then provide logs that cover you starting the 5th transcode so I can have our developer take a look?

I’d like to keep this topic alive. I am also experiencing the same issue. Running Ubuntu 20.1 w/ P2000. Doesnt matter which player I use it will kill the transcoder if I select any quality level other than Automatic. @el_pedriyo Were you able to get the transcodes to work on 20.1?

Plex Media Server Logs_2021-09-26_22-49-11.zip (1.3 MB)

Hey,

Sorry I have been busy moving from house, and had no chance to upload the logs for @chrisallen to take a look with new debian and ubuntu. The issue is still going on for sure, however I decided to keep under debian 10 as it was working good on there.
Will see if this week I have a bit of time to post all logs when Plex directly kills the playbacks.

@chrisallen asnwering to your questions, what happens when I open a 5th transcode, is plex giving an error like this one:
image
or simply killing the playback.
About a performance issue, I guess is something broken somewhere. As I was saying before I will try to upload the logs once I have a bit of time during this week.

Kind regards

1 Like