4 ms·
The problem that I had was I couldn't figure out what string I needed to pass here. I found some docs in the AV1 spec like: > For example, codecs="av01.0.04M.1
by kevincox 5y ago
The problem that I had was I couldn't figure out what string I needed to pass here. I found some docs in the AV1 spec like:
> For example, codecs="av01.0.04M.10.0.112.09.16.09.0" represents AV1 Main Profile, level 3.0, Main tier, 10-bit content, non-monochrome, with 4:2:0 chroma subsampling co-located with (0, 0) luma sample, ITU-R BT.2100 color primaries, ITU-R BT.2100 PQ transfer characteristics, ITU-R BT.2100 YCbCr color matrix, and studio swing representation.
But how the hell am I supposed to reliably figure that out. It would be awesome if the browser devtools or the Media API could spit out the right string for a video file.
- LeoNatan25 5y agoA “video file” is a misnomer. A “video file” (such as mp4) is actually a container with several different tracks, which can be one or more video tracks, audio, subtitles, metadata (chapters, DV, synchronization) and others. If the browser is not aware of any of these, it will not be able to provide the information you require (but is a probably good indicator that the track is t supported).
- kevincox 5y agoWell that is a problem of the API, but at least it can recommend what the best string to put in the source tag's type attribute. > If the browser is not aware of any of these In my case the browser is playing the file, so it should know what info is there. But ideally it would at least make a best-effort attempt.