It turns out that they were prophetic, not delusional.ĪV1 uses the open-source dav1d decoder which came out of the VideoLAN, VLC, and FFmpeg communities, with sponsorship from the Alliance for Open Media. Stating these things 15-20 years ago would have prompted laughter and at least a few jibes aimed at the one claiming this would one day would be a thing, especially at the suggestion Intel would have a competitive discrete GPU.
Things have changed over the past decade, with Microsoft now offering Linux based instances on Azure, various companies accepting that they need to open source at least some of their driver technology and now Intel being the first to hardware accelerate a royalty free codec. A movie would take days to get encoded.AMD And NVIDIA Provide Hardware AV1 Decoding, But Not Encoding From what I know, SVT-AV1 is developed by Netflix in cooperation with Intel, So I assume they somehow rely on hardware encoding using an Intel CPU extension.ĭoes somebody maybe know more and how they did it? I really can't imagine that they just do CPU only encoding. If I take a look at the numbers of media elements Netflix offers, the amount is just huge, and I really don't understand how they did it. Recently I came along a news article about Netflix and that they are upgrading their library to AV1. No matter which one of these I try, the performance is slow, even slower than with HEVC. You will notice that there are 3 main encoders available to handle encoding to av1. If you take a look at the following doc pages from ffmpeg: That was the point where things started to get strange, as I want to have this codec instead of h264 ^^.
Yesterday I started implementing AV1 as codec, as it will in near future detach h264 as it's more efficient with the same level of compatibility across all the available browsers.
To enable streaming, I take the input video and re-convert it into HLS segments in multiple version and codecs to reach maximum compatibility. I'm developing a VoD application as a white label product that runs in a SaaS context using K8s.
0 kommentar(er)
