How does Jellyfin-web determine what content a client is capable of playing?

[kimbo]

I went ahead and forced hevc & aac on the webm container list (by editing main.jellyfin.bundle.js), figured it wouldnt work if its not being done by default... to my surprise this does work

So, why doesnt jellyfin add hevc to the webm container in DirectPlayProfiles? Seems odd that the client chooses the profile with the least number of supported codecs

[TheDreadPirate]

My understanding is that HEVC is not officially supported in webM (officially supports VP8, VP9, AV1). It is also my understanding that the devs prefer to follow the specs of the standards instead of doing something off-standard, but technically works.

[kimbo]

My understanding is that HEVC is not officially supported in webM (officially supports VP8, VP9, AV1).  It is also my understanding that the devs prefer to follow the specs of the standards instead of doing something off-standard, but technically works.

Thanks for the info, like I said I expected it not to work, but, then why is jellyfin picking webm if webm does not support the media's codec? Jellyfin should be selecting a container based on what the medias is, to ensure directplay