yeah, going to run this now, thank you
HW transcoding is working flawless with this version, thank you again! Is there an eta on the official realease?
I know those changes have already been put into the master source tree.
Whenever they build a new release, I expect it to be included.
They’re working on fixes right now (based on activity I’m seeing).
I suspect they have a list of “Must Fix”
For that reason, I don’t know a date or even a build version other than ASAP.
When was the last release? Start counting the usual cycle I guess 
Sorry
No problem, thank you again!
I look at release notes on 1.31.1.6716 and I see:
- (Transcoder) Hardware decoding using Nvidia GPUs could fail with certain driver versions (#14069) (#14070)
However - @takeittothemax says doesn’t fix transcode issue as noted NVIDIA hardware acceleration inconsistently working with web streaming - #96 by takeittothemax
How do we know what issue that changelog notice fixes? Where do I lookup #14069 and #14070
Is there an good issue tracking location for releases?
Please use the Engineering release (6715) above.
Release 6716 does NOT contain the fixes which are in Engineering build 6715
hey sorry im kinda new to unraid. can anyone assist with how to run the docker exec command?
1.31.1.6733 is out
@ChuckPa Do you know if the patch is inside of this release?
Good news, build 6715 does appear to have resolved the “No decoder surfaces left” errors. All videos will transcode properly.
However, I’m back to “some of the time nothing happens”. As usual, 404 errors in the PMS server console when that occurs.
EDIT: just did a quick sanity check starting the 1080p h264 test video and requesting a change to 1080p 12Mbps: build 6364 failed 1/10, and 6715 3/10. Not sure that’s enough samples to be sure there’s a difference, but obviously the problem persists.
Build 6733 is behaving the same as 6715 for me, so I suspect the patch was indeed included.
I went and checked.
It looks like some is in 6733 but there is still a 6739 in Alpha build (our internal – pre-QA testing)
I ask we all test as much as possible. If tweaks are needed, let’s please get them ASAP
Please recreate the failure for me. (SERVER DEBUG LOGGING enabled)
I want to trace what happens. There’s something else happening
Here’s logs from an attempt on build 6715 - playback of the 1080p H264 video started in direct play, and an attempt to transcode at 00:11:23.021 to 1080p 12Mbps failed, with the 404’s I’m describing as symptomatic starting at 00:11:25.202.
OK… i see the 404’s
Switching resolution mid playback seems to still be an issue.
To confirm what I see, Set your Playback Quality prior to starting playback
I tried 20 times to be sure, but yes if the quality is set to 12Mbps before playback starts, it transcodes properly.
If you can
- set a playback quality
- observe playback is as expected (at that quality setting)
- attempt to change playback quality
- see playback now fail
- we have a repeatable error.
(I see it too)
Yes, starting at 12Mbps and changing quality is sometimes failing. Not always, so sadly it’s not perfectly reproducible, but yes sometimes.
That’s repeatable enough for me.
When I switch from any 2160p UHD → 1080p, it fails.
I got this 
3 Likes
Any of the released plex media server versions cover the fix for this issue?
No success there yet.
I’ve gotten caught on other tasks enough that I can do the deep-dive debug on this for them. (been using the debugger all day… 
)
I’m going to put PMS in the debugger and find out where it breaks. I won’t know why but at least I’ll know where and can pass that info.
