Jellyfin-web: Support AV1 in mp4

[cromefire]

Support detection of av1 in mp4 in firefox and chrome:

To probe support use:

video.canPlayType("video/mp4; codecs=av1");

[cromefire]

To try av1 in firefox (desktop), turn on "always prefer" here and then try this (ensure av1 is used in the stats for nerds)

[MrTimscampi]

We already do: #1167

[cromefire]

Okay but av1 in mp4 support is still missing. This would be video/mp4;Codecs=av1

[cromefire]

This is what YouTube for example does

[Artiume]

So av1 files can't be streamed in .ts containers. we have to use mp4 containers. I tried disabling video transcoding to verify it would work in the browser and it kept failing. Turns out it was trying to Direct Stream and ffmpeg ate itself.

https://github.com/SPBTV/video_av1_samples

[cromefire]

Yeah webm and mp4 only and some weird format (ivf or so?) for now

[stale[bot]]

Issues go stale after 90d of inactivity. Mark the issue as fresh by adding a comment or commit. Stale issues close after an additional 14d of inactivity. If this issue is safe to close now please do so. If you have any questions you can reach us on Matrix or Social Media.

[cromefire]

Not stale

[cromefire]

Shush bot

[Extarys]

Can we also add mkv containers? I know how to work with mkv and it's tools,etc. I must not be alone using mkv containers with av1? I tried streaming a mkv av1 50fps video in jellyfin and got a not supported error, quite sad.

It would feel weird having a bluray collection locally with a "webm" file format, or is it?
I used mp4 "back in the days" when the video was x264 encoded but that is pretty much it. all my videos are mkv now.

[MrTimscampi]

MKV is unfortunately not supported by browsers.

Historically, MKV was treated as WebM (By Emby, then that behavior was inherited by Jellyfin). However, we removed that behavior because, while WebM is essentially a small subset of MKV, it's not fully compatible with MKV, and caused some errors when files weren't compatible.

[Extarys]

@MrTimscampi Oh I see, thank you for the explanation. :heart: I guess it's easier in the backend to support webm only than trying to support both :disappointed:

It is a little off topic so feel free to redirect me if needed, but I'll get faster answer and probably a better one too asking this here and now: If I want my library to be as jellyfin-friendly possible while having the flexibility and audio quality I currently have, should I start using webm for my new encodes with opus/av1 instead DTS and stuff? I mean, opus rocks. :v:

x264 videos inside mkv should be pretty easy to "port", just need to transcode the audio track. Main issue is vodsub but I know there is plan to extract the images on the server and support them in browser or something so no biggy on that part. The sad thing is aas subtitles won't have the custom fonts because webm doesn't support attachments. Kodi and the mpv-shim can use those tho, but I understand the browser's limitation too.

EDIT: Ohhh I think mp4 does pretty much everything I want compared to webm and is supported in browser, so... woops.