2024-01-19, 05:48 PM
(This post was last modified: 2024-01-19, 06:12 PM by tmsrxzar. Edited 2 times in total.)
(2024-01-19, 05:43 PM)kimbo Wrote: Yes, I did, read the OP please.
(2024-01-19, 03:52 PM)kimbo Wrote: Hey guys, could anyone point me in the right direction as to where in code Jellyfin-web detects client capabilities?
In my case it is wrong, and emby has no issue direct playing h265 content, while jellyfin reports that the codec is incompatible
It seems its using some method other than isTypeSupported, canPlayType or mediaCapabilities, since all of these report that h265 is supported
Running Thorium with hardware decoding disabled so its using FFmpegVideoDecoder which should have no issue playing h265.
I have tried the option "Prefer fMP4-HLS Media Container", no effect
Thanks for reading
https://www.google.com/search?q=thorium
"Thorium (chemical symbol Th) is a naturally occurring radioactive metal"
https://www.google.com/search?q=thorium+jellyfin
"Thorium: Chromium fork named after radioactive element"
so we know it's some sort of chrom(e)(ium) ...
for example, i am running a Firefox 115.6.0esr fork on Debian 12 Bookworm
a little looking and i wouldn't be able to help with thorium or chrome
the initial question of where does this code live turned into support for a browser i didn't know existed which is based on a browser i already cannot get to work
recommendations are
compare to a non forked browser, if it's a chrom* issue or a thorium one would be the question
compare to jellyfin media player which is better suited for the task at hand
compare to mpv-shim for jellyfin