

0·
6 days agoThere are a handful of common reasons.
- The client doesn’t support the formats. Browser clients are notoriously picky not supporting some common video (for example few browsers support h265 and it isn’t generally considered web-safe) and audio formats. But embedded devices may also cause trouble if they don’t have enough CPU to do non-accelerated playback and don’t have hardware support for the codec used.
- Playing at a lower bitrate. In that case you can transcode at the fly.
- Remuxing. This is things like the moov atom where the actual codecs are supported but not the container or exact packaging of the file.
But yeah, especially if you are using a player with wide format support you may not need it.
I’m pretty surprised that all of the audio formats work. I’m no so surprised that the TV has h265, although maybe a bit surprised that it is exposed to the browser. The container support is also pretty surprising. Unless your MKVs are so simple that they are effectively WEBM.
Or maybe it pops the link out of the browser into a dedicated media player which has decent codec support.
iDevices do expose h265 in the browser, but the container support is still a bit surprising. But then again WEBM is basically MKV, so maybe that is why it tends to work.