Only do DoVi remux when the client supports profiles without fallbacks

[gnattu]

In 10.10 clients that can only play the fallback layer like the Samsung TVs will report DOVIWithHDR10 as supported video range, but the server should not do remux in DoVi as the client can only play the fallback layer. This changes the server to only do DoVi remux when the client can play DoVi videos without a fallback layer.

Changes

Issues

Forum report: https://forum.jellyfin.org/t-issue-with-playback-of-hevc-files-in-jellyfin-dolby-vision-tag-misconfiguration?pid=43992

[GeorgeH005]

The supportsDolbyVision function in browserDeviceProfile.js in the web client should have returned false, shouldn't it have? Even if it did somehow return true, shouldn't the canPlayType functions have also returned false? I do not understand how the capabilities were reported as such in the first place.

[gnattu]

The supportsDolbyVision function in browserDeviceProfile.js in the web client should have returned false, shouldn't it have? Even if it did somehow return true, shouldn't the canPlayType functions have also returned false? I do not understand how the capabilities were reported as such in the first place.

LG TV and Samsung TV has different logics because for Samsung TVs there are no DoVi capabilities at all so those color ranges are reported purely for the fallback layer. On LG TVs the real DoVi without fallback is always reported on supported TVs.

The reason behind this change is that Samsung TV also has buggy HLS player that struggles with seeking.

[GeorgeH005]

Don't they share the client code? Those capabilities can't be reported as far as I recall without supportsDolbyVision being true, which is either set by the wrapper app, or because the client is using safari on an iDevice.

[gnattu]

Clients can inject the profiles by design and that is injected by Tizen app wrapper iirc.

jellyfin/jellyfin-web@aa4004a

it is directly hard coded.

[GeorgeH005]

I will have to look deeper into the client code. Thanks for explaining!