I’ve been keeping my eye on this thread, and it sure sounds like he’s describing the same behavior I’m seeing. Transcodes work for non-web clients, web client streams start properly even with transcoding, but changing quality in the web client breaks it. He’s also reporting the transcode runner threads being killed prematurely, which I think I’m seeing in the logs.
Have a look at this quick summary table I put together of my “testing matrix” (filtered to unique combinations only) - the combination of using the web client and having hardware-accelerated video encoding enabled seems to be important. I don’t know enough about the inner working of plex, but is there any reason for the web client to know about hardware acceleration and thus make the request slightly differently, or for plex to handle requests from the web client differently from an app? I can’t imagine either answer is yes, but somehow when I combine those two factors I get problems.
Testing Matrix Summary.txt (2.2 KB)
EDIT: I tried using the Plex Media Player client on my Arch Linux desktop, and it also suffered from the same issue.
