Thanks for update. I just wasn’t sure if some of the transcoder stuff mentioned covered this issue. Didn’t want to updated without being sure.
What would i look for in release notes that would tip me off to this issue being fixed?
Thanks for your work on this issue.
Not sure what the fix will be labeled as but it’ll be seemingly obscure.
I’ll know first and will be testing it prior to release.
To verify: 6715 should be 100% fixed regardless of Nvidia driver version or is this still being actively worked on/samples needed? I’m having the same issue with PMS 6715 running on CentOS 7 with a Quadro P620 passed through ESXI 8.0 to the VM with Nvidia driver 525.89.02.
PMS will start HW decode and HW encode fine regardless of how the “initial” quality is set but if it’s changed mid-stream, the transcoder shows up briefly in nvidia-smi then exits and the video will not start playing in the web client (Chrome/FF). Not sure if you’re still needing “full” test results for all 5 sample videos posted. More than happy to run through the gamut, just didn’t want to put in the time if either 6715 is known to still exhibit the bug or if we need to be running a very specific Nvidia driver to work (525.60.13 was mentioned earlier) or if the fix in 6715 was specific to Debian based distros and not RHEL based and those will be fixed later…
-
Everything included in build 6715, plus those additional corrections found in final testing, are in build 6810
-
The same binary executable code put into DEB packaging is also put into RPM packaging.
– We generate one set of x86_64 binaries and then “package” it for every 64 bit platform & distro which needs it.
(From a Xeons to AMDs to AlderLakes to Synology, QNAP, and ASUSTOR – They all get the exact same 64 bit binary files)
I was on 6810 then downgraded to 6715 in researching this issue. I’ll run through the tests and get you the results, unless I need to be on a specific Nvidia driver?
1 Like
CUDA 11.7 ( which is about Nvidia 515 drivers) are still OK but not required.
CUDA 12.0 (which I’m using Nvidia 525.60.13 drivers for) are recommended.
The only thing you cannot do is go too low. The reason for this is AV1 support is now in the transcoder. It will bark at you if it’s expecting a “AV1” reply (yes/no type) from the driver and doesn’t get it.
I tried to break the transcoder – switching from 2160 output → 1080p AND back several times .
Wouldn’t you know it ? NEVER FAILED. … but i know wit will.
I have to catch it.
I reverted to the snapshot I took before downgrading PMS then downgraded Nvidia so now I’m at PMS 6810, Nvidia 525.60.11 (couldn’t find 525.60.13 for the Quadro P620). If I have the web client set at 1080p 20Mb/s for initial quality and start the test1 video above, it’ll HW decode/HW encode just fine but if I try changing to say 720p medium/3Mb/s mid-stream, nvidia-smi shows the 2nd transcode session start then immediately stop and the web client shows an infinite-buffering circle. If I disable “Use hardware-accelerated video encoding”, it’ll HW decode and SW encode but I can change the quality mid-stream and it works fine (verified with “nvidia-smi -q | grep Utilization -A4” that the encoder isn’t being utilized).
Been at this for a few hours, need to take a break for now but will come back and run the full gamut of the test you outlined above and get you the results…Maybe the encoder on the P620 isn’t up to the task?
1 Like
@ChuckPa
Anything new on this one? The issue with the quality change mid-stream seems to be still happening. Just tried to change my transcode from 4K->1080p11mbit down to 1080p8mbit but it fails… I could see the new transcoding task in nvtop but the process then dies and playback errors out…
Our meetings are weekly on Monday.
I will find out more then.
I looked at the submitted issue I wrote 2 weeks ago and see no action on it.
(no target version assigned)
2 Likes
May I ask if there has been something new?
I’ve escalated this. It’s marked as “planned” but no details have been provided.
I don’t know if that means “Planned for next release” or “Planned sometime before Christmas” 
1 Like
any update on this? would be nice to stop running an aging version of the server.
Try using https://app.plex.tv (it’s version 4.106) which is a big step up from what’s bundled.
If that fixes the problem, then I can start bugging them about bundling it into PMS
Unfortunately Plex Web 4.106.1 via https://app.plex.tv with PMS 1.32.2.7002 is still having problems changing quality for me. Thanks for keeping tabs on this thread!
I knocked on the door over at their place the other day.
Lights were off. Door was padlocked, Cobwebs everywhere. 
I think my next step is to call a realtor
2 Likes
I’ve still not had chance to go in and check this out yet, sorry! I’ve been having to mess with J-fin (sorry for swearing ) with OTA EPG as it seems we’ve got an EPG problem (Freeview UK). I’ve dropped a new topic about it.
… Anywho, back to this topic. I’ll try and get going on this soon, maybe Monday. 
Take your time. When you decide which you’re going to use, let me know.
I’ll be on reduced hours the next two weeks
1 Like
I hope things are ok with you @ChuckPa ?
I like to keep on using Plex, but for now I’ve just made a 2nd DVR (recordings) folder and got Jellyfin to record to that, then I share that folder with Plex 
It gets around the problem for now. I did think about adding the custom XML I’m making with OTA EPG data, but I know that’s fallen over before… We really don’t use the TV DVR much, so I don’t find out there’s a problem until my Mrs. says “hay! Plex is at it again, why does it hate me and/or Emmerdale”; it’s tuned into a running joke now!
Anywho, back on topic. I tried using the app.plex.tv UI to stream a 4k movies; it was still having issues. Mainly working for one stream, then click/change bandwidth and it would fail, then pick a 3rd and it might work… Almost like on/off/on again… This I tested last week, my PMS was on the previous version to 1.32.2.7100 (what ever that was). I’ve updated since then and I’m trying to do the same test and it’s still the same.
One thing I have noted though, is that on the 2nd “on” attempt (don’t know how to better describe it) it will work, but you have to wait like 30 seconds or more! It’s taking a lot long to switch and test as you just don’t know if it will work. PMS dashboard takes about 10seconds to recognise the change, but even longer for the Chrome client to kick in. I can see that the data is defiantly going over LAN according to the dashboard 
I’m not tried to fish out any logs just now, this was more of a test and see if it’s changed…
Long story short, it’s the same; works every other quality change (ish), but not takes longer to start playing if it’s going to work.
In today’s meeting, I was told there are now another set of hands on the TV/DVR issues.
While I didn’t catch everything said, hearing there are more hands is very good news.
The Bandwidth/ Resolution changing is a known problem I’ve been trying to champion. It’s a known problem with Plex/web since 4.100
I got some time with the engineer today.
He tried to tell me it was a server problem (Bad decision) 
I shared the logs which captured Plex/web not waiting for PMS to reconfigure after the change request (issue a new session ID).
For you, the workaround isn’t great but simple.
- Settings - Player (Plex/web) - Quality
- Turn off the automatics
- SET the quality to what you want in advance.
It’ll work every time.
2 Likes
