I took PGS and VOBSUB (image based burning) as well as SRT, ASS, and SSA (Text-based) burning into consideration.
From a heavest / worst case -> lightest load order:
Decode HEVC (software)
Burn Image based subtitles
Burn text based subtitles
Any other decode in encode > 30 Mbps
general stuff here
.
.
.
.
.
HEVC / H264 Hardware decode & encode w/ remux
Convert the audio.
Remux the container to send out (Direct Stream w/o audio conversion)
As primary example of this, please consider the NAS processors (J3455- ApolloLake).
It will handle 2 HEVC HDR streams -> H.264 with ease (40+ Mbps each).
It will choke on subtitle burning of any type.
This is why my i7 suggestion.
Depending on your use case, if you only plan on 1-2 concurrent streams, the i5 is less costly
(i5-7500)
A lot of Linux distros don’t have full support yet.
Plex doesn’t support the 9xxx processors at all right now.
This is because Plex doesn’t have the iHD video driver which is required. (Intel migrated to it for the 9xxx series)
Quad core machines do very well . Dual cores struggle.
When burning subtitles, which are a single-threaded task, single-core speed wins out.
Otherwise, try to favor upper end clock speed (but not insane) quad core w/ hyper threading and you will be very safe.
Hi again guys, I just wanted to give you an update on what I did to fix my issues.
So I didn’t had to buy any hardware after all (maybe a big fat ssd to replace my hard drive but anyway). On someone advice, I’m using now the Infuse 6 Pro app with my Apple TV 4K with the Plex Media Server integration. And this is awesome! I’m even thinking about getting a plex pass to get trailers and extras for my movies.
Here’s some info on what I suceeded to direct play with Plex + Infuse: