@mbarylski said:
Ok, so if I turn off direct play and let the server do the transcoding will I get 4k with burned in titles after HDR and Atmos are added to the app? I’m guessing no, because the client codec still plays a role even if forcing transcoding on the server.
Until the h264 problem gets fixed, then burned subtitles will cause a transcode down to 1080p. If you have your subtitles in srt’s (or another text based subtitle) then no transcoding is necessary and the subtitles can be sent side by side with the video file.
Not really clear though on why I couldn’t just let the server do all the work.
The basic model is going to be a server, client, and TV setup:
Server -------> Client-------->TV
The server sends the file to the client. If the file is directly playable the file is sent as is. It works similarly as a download from a webpage. Where you ask the server for the file and then it sends you the file, no messing around with it.
Now let’s say that your using google drive/onedrive/etc and instead of just asking for the file you ask for the files to be in a .zip file. The server compresses the file and then sends it your way. This is similar to what happens when a client tells the server to transcode the audio or video. In effect the client is telling the server “I can’t play X, so convert it to Y”.
So now in the zip example you have your zip file, if you don’t have any program to unzip the file you can’t do anything with it, but if you have a program to unzip the file then you are able to decompress the file and access all the content. This is what happens when the audio/video/subtitle stream hit the client. The client act’s like the decompressor and makes that video/audio stream available for the TV to display. So if the client has no way to decompress the file into a usable format then the TV has no way to display it.
Now there are some exceptions to this. The biggest one is audio pass-through. This basically tells the client don’t worry about the audio something else further on will take care of it. Either the TV itself, or another device further in the chain.
In actual practice this process is a bit more in depth, but hopefully that gets the basic process down for you. If not let me know and I can see if I can get a better explanation for you.
Short answer: The server tries to carry the heavy loading of converting before getting to the client, but the client still needs to be able to play that new format or it can’t output it to the TV. It’s very similar to transcoding where if the server can’t decode the original file it can’t convert it to the new format, just that if the client can’t decode the audio/video you will normally get a cannot play this file type message.