I’m using plexmediaserver_1.41.2.9136-59a5b8283_amd64.deb on an i7-1360p in docker. I have plex pass.
No HEVC encoding options. Did I screw up somewhere?
Edit: Apparently I did screw up somewhere. Somehow I was running 1.41.2.9134-3391644e0 and when I updated to 1.41.2.9136-59a5b8283, the HEVC options became visible.
Zero issues with the Arc A380 over here, using Docker on Ubuntu Server 24.04.1 and Kodi (PM4K) as a client.
Ditto, I’m running Windows 11 x64. A380 working as expected.
CAREFUL
Please do not get off-topic.
Please stop here – or open a new thread.
Just want to say awesome job. Working perfectly for my use case, tested transcoding to a few devices (primarily android or Google TV based) and the quality of the HEVC transcodes has been awesome.
very excited for this, hopefully we can see it pushed to beta soon!
Movies that have a *.ts container are showing a black screens now on playback. 2019 Shield for the player, Windows 11 plex server. Moving the content to MKV containers works fine. Current release of this preview. Main release of Plex works fine.
@tmillszero1 can you please replicate this and then share your logs?
PMS @ Windows x64 | i5 14500 | 32 GB RAM
Is it normal that my iGPU can’t even manage a 4K HDR encode (4K → 4K) with subtitle burn-in? I only get about 0.7 encoding speed, the UHD 770 runs at 90% load. Without encoding, the load drops to below 10%.
@chris_decker08 Please see the attached logs and screenshot of Mediainfo of an example file that is exhibiting the behavior.
PlexLogs.zip (7.1 MB)
Sample
Mediainfo screenshot
On linux I was getting about the same values with my Intel a310 or a380 anytime PGS subs were on and I was playing on a device that did not support them, once I updated to a newer test build the encoding speed jumped up.
In my case, it’s a little different.
Subtitles are always SRT. The burn-in only occurs because audio has to be converted (LG WebOS does not support DTS, for example) and PMS automatically transcodes the video stream as well.
I use the latest Forum Preview.
@Schmitzke do you get the same sort of cpu load without subtitles? subtitle burn in seems to be expensive for 4k 10 bit videos
LG with WebOS does support DTS, its just depending on your TV…: G39 (last year) and G48 definitely do support it.
With an GTX 1050 Ti and 2x 4k x265 encodes running, I got round about 70-75% usage, down to fit my 30 mbit upload, and no problems. Please excuse the lack of details, I forgot to pay attention shame on me
//EDIT:
==> GPU-Usage is now, at least with this release, a “need to have” on the Web-Dashboard. Please add/consider as feature!
Thx
i can transcode with just an i3-1235u in x265 4k HDR 10bit with just the built in Intel HW encoder @ the automatic 10000mbps just fine, usage hits around 20-30% on the CPU, no buffer. But as soon as subtitle burn-in gets turned on it’s a complete no go. buffers like no tomorrow. is there a way to get plex to convert the PGS or ASS to just plain non-style text like SRT.
PGS are image based subtitles (like VOBSUB), you need OCR to convert images to text. Or maybe when they introduce Plex AI in 2035.
correct, we cannot convert image based subs such as PGS to SRT, however I believe if you have your players “subtitle burn in” setting set to “only image formats” then it will down convert ass to srt
Without needing to burn in subtitles, everything works wonderfully. Whether HDR-to-SDR or HDR-to-HDR, the UHD 770 handles it with ease. I was especially pleased to see that tone mapping now works with hardware support on Windows. Even with subtitles burned in, performance was impressive. Previously, this was a no-go with my iGPU. But now, I’m facing the same issue again with x265—at least when subtitles are burned in.
Perhaps it might still be possible to modify the LG and Samsung apps so that SRT subtitles aren’t burned in when transcoding audio or video. Honestly, I’d much prefer no subtitles over constant buffering. 
After all, these two platforms affect a large number of users. 
Yes, that’s correct. LG only suspended DTS support for a few years. However, precisely those TV generations are quite prevalent, just like the many Tizen TVs without DTS support.
But that’s more of a side note. My primary point was that any kind of transcoding leads to the burning-in of subtitles. Whether it’s due to bandwidth limitations or a lack of codec support, there’s no Direct Play with subtitles (whether SRT or PGS) as you would have with Android; instead, they’re always burned in.
And unfortunately, that’s a deal breaker.
Are you saying that h264 subtitles burn in works better than h265 subtitles burn in?
