What's the current state of the MVP vs Native Player in the AppleTV Client

[Lostboy66 9]

I normally set it to Auto, but would think Native would be more efficient (all my content is either H.264 or H.265 which are all native).   What advantages/disadvantages  the MVP player have vs the Native player, and how does the Auto setting work?

[vdatanet 1650]

In practice the choice matters less for what plays natively and more for what doesn't.

Native player – Goes through AVFoundation, so decoding is done by the Apple TV hardware and it's the only path that can output HEVC HDR/Dolby Vision properly. The weak point is the streaming/buffering side: with high-bitrate content it's not very efficient and it's fairly easy to run into buffering, even on direct play.

It's also limited to containers and protocols AVFoundation understands. MKV isn't one of them, and since Emby doesn't currently support HLS with fMP4 segments, MKV content can't simply be remuxed into something the native player accepts — it ends up being transcoded instead. That's why in practice pretty much all HEVC HDR content gets transcoded.

MPV player – Handles almost any container, so it avoids the container-driven transcodes and generally holds a stream better. The trade-off is HDR: MPV tone-maps the picture itself rather than passing HEVC HDR through to the Apple TV's own decode/display pipeline, so you don't get true HDR output.

Auto – Emby decides per item: it uses the native player when the stream is something AVFoundation can direct play, and falls back to MPV when it isn't. So "Auto" doesn't mean "always native" even if all your content is H.264/H.265 — the container and the HDR metadata matter as much as the codec.

What would really fix this is support for HLS with fMP4 and remuxing, so the Apple TV could play HEVC HDR natively without transcoding. That's not possible today.