Some 4K HDR media is simply... not supported.

[segin 1]

And it makes no sense because I've had similarly-encoded 4K HDR content work flawlessly with Emby (including various server-side transcoding scenarios.) 

What does Emby detect for the "unsupported" media? That it's in a Matroska container (it'll list simply "MKV" by the file path.) It doesn't list codecs, streams, anything. Just "MKV". 

VLC, on the other hand, has absolutely no problem with the video. 

I've several movies that are unsupported (although by all means they should be) by Emby like this. Incidentially, most of my 4K HDR content is coded in a similar manner, but does work with Emby. In addition, these "broken" videos are broken with seemingly all clients: Web, iOS, Android, Windows/Xbox, Roku, Tizen, and LG webOS (at least, these are what I've tried.) 

Is it possibly something with the way the Matroska file itself is packaged? 

[Abobader 2941]

Hello segin,

** This is an auto reply **

Please wait for someone from staff support or our members to reply to you.

It's recommended to provide more info, as it explain in this thread:

Thank you.

Emby Team

[segin 1]

Nevermind, I feel really stupid - the problem came down to incorrect Unix permissions on the filesystem holding the movies.

[Luke 37006]

Thanks for following up.