2024-02-09, 03:08 AM
maybe i was thinking mediainfo, in any case
pretty sure you are suffering from the same issue as firetv stick
https://github.com/google/ExoPlayer/issues/11096
i was looking to see if your metadata matched up to the issue report when i asked for ffmpeg -i but i guess i asked for the wrong thing
highlights are
not fixable from jellyfin, pretty much only workarounds and hacks
you may have better luck re-encoding without cropping, some users report unusual resolutions do not work when standard ones do
with that i see the one that works is 3840x1600 being divisible by 4, the one that does not with the same dolby vision data is 3840x1604, 1604 not being divisible by 4
this is just based on back and forth i've read between users and developers
forcing transcoding ffmpeg should drop the bad parts because it's not supported HDR10+ or Dolby Vision so it would disappear, but won't look very good
stripping the dolby vision metadata with dovi_tool https://github.com/quietvoid/dovi_tool
this commit to Kodi's code has users reporting the issue is mitigated by removing HDR10+ https://github.com/quietvoid/xbmc/commit...42747a73bb
that commit being by the same author as dovi_tool sort of makes sense
pretty sure you are suffering from the same issue as firetv stick
https://github.com/google/ExoPlayer/issues/11096
i was looking to see if your metadata matched up to the issue report when i asked for ffmpeg -i but i guess i asked for the wrong thing
highlights are
not fixable from jellyfin, pretty much only workarounds and hacks
you may have better luck re-encoding without cropping, some users report unusual resolutions do not work when standard ones do
with that i see the one that works is 3840x1600 being divisible by 4, the one that does not with the same dolby vision data is 3840x1604, 1604 not being divisible by 4
this is just based on back and forth i've read between users and developers
forcing transcoding ffmpeg should drop the bad parts because it's not supported HDR10+ or Dolby Vision so it would disappear, but won't look very good
stripping the dolby vision metadata with dovi_tool https://github.com/quietvoid/dovi_tool
this commit to Kodi's code has users reporting the issue is mitigated by removing HDR10+ https://github.com/quietvoid/xbmc/commit...42747a73bb
that commit being by the same author as dovi_tool sort of makes sense