Server Version#: 1.40.4.8626
Player Version#: Roku devices
Since the latest update(s) (aka the last 2 versions) my Roku users are having weird experiences trying to play x265 series files. Sometimes it works, sometimes it doesn’t, users get a weird transcoder error, and on my side I can’t reproduce it so far.
I have 2 different Roku based users try to play their normal shows they watch and both failed to play. Debug logs were taken right after the errors and I had no other streams active.
I swapped my hardware transcoder setting from my Intel GPU to NVidia GPU and the Roku users are now working,
Issue appears to be when I have PLEX set to Intel GPU and Roku users trigger transcoding. It may not be a Roku specific since my other users Direct Play,
My Intel GPU (which I wish was working since using my NVidia GPU occasionally crashes my video games when also used to transcode) is an Intel UHD Graphics 770.
I’m seeing the same problem since two releases back.
Two remote users on Roku fave the problem for all transcodes. One of them also has the problem on a 2018 Samsung client with all transcodes.
I can reproduce the problem locally on a Roku, but only with videos that have ASS subtitles and the Roku client burn subtitles setting as always (doesn’t happen if set to burm image only).
In all cases switching transcoder from UHD 630 to Nvidia fixes it.
I submitted my report yesterday, not having seen yours.
@chris_decker08 Alerting you to these two reports because you are involved with recent Plex server transcoder changes that may be at the heart of the problems described here, starting with Plex Media Server release 1.40.3.8555. The timing may also coincide with Intel having fixed a bug that was referenced in your ongoing thread about hardware-based tonemapping (which I’ve been monitoring). I’m hoping the reports and logs provide some helpful clues, and I’m happy to provide more information as you may need.
Edit: I should clarify that this has nothing to do with tonemapping, per se. I know I’m running Plex on a platform that won’t support hardware-based tonemapping (7th gen w/UHD 630). But the transcoder failures the two of us are reporting here are not a result of tonemapping, rather a more common use of transcoding media not natively supported by a client. It may be a coincidence that it started at the the time as the recent server and Intel changes for transcoding/tonemapping, but I suspect they are related.
Does this build resolve the issue?
Installed the new build, seems to be working so far. I can see a Roku person streaming with HW transcoding on my Intel 770 right now. Thanks! Will update if I see any further related issues.
It does resolve the issue, at least for one of the scenarios I can easily test. I will ask my remote Roku & Samsung users to confirm.
Can I assume the changes you made will come to a new beta release soon?
Thanks Chris!
I was sent over here from my post HW Transcoding broken - #2 by FordGuy61.
This helped with only one file of mine with DTS, the 720p movie that only HW transcodes the DTS to a workable audio but the video seems to play fine for at least 5 minutes with no buffering. So counted as a small win…
However, this doesn’t help still with any other HW transcoding on 1080p or 4k files for audio or video HW transcoding it causes buffering every 10 seconds or so. 
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
