Rendering to AV1

1. offizieller Beitrag

    I've been using HEVC with Voukoder for a while now, but After the updates to the AV1 after finally updating, rendering does not take a long as it used to with the SVT support. For 1440p game recordings i have it set for 2,000 kbit with a max bitrate of 10,000 kbit, ultra fast preset, and main tier. The quality of the videos look really good in my opinion. a 20 minute 1440P video ended up being 340 MB in size. Very good file size to quality compared to h.264 and h.265(HEVC)

    I dont see too much information for AV1 out in the wild. I am wondering who else is using the AV1 codec and what settings they are using. I haven't played mych with the constrained variable bitrate, or the constant quantizer yet.

  • Vouk 21. Juli 2022 um 16:33

    Hat das Thema freigeschaltet.

    Personally I much prefer CRF over a set bitrate, and going with a value of 20-30 is usually a pretty safe bet. Just go by the default values that Intel set for SVT-AV1, then adapt them to your needs. For v1.0 that would be Preset 10 with CRF 35, for example. But note that, if I remember correctly, Voukoder is still stuck on v0.9, while the most recent version is 1.1x.

    Most of these options aren't relevant to Voukoder, but I'm posting them for context: SVT-AV1 Github

    AV1 is still under dev, and does not provide a stable image output, and you might not able to view render results on mobile phones unless you have a good media player app. Generally not recommeded for reliability dependant workloads

    And, unless new compression methods show up, AV1 is more of a cranked up x265 with depreciated features due to slowness added back, but I could be wrong since I have not been following updates

    They're similar-ish, but function differently. Preferably use CRF if possible, it will result in smaller file-sizes, or more "optimized" if you wanna think of it that way.

    Sorry for the confusion mate. I mostly use (SVT-)AV1 through FFMPEG, where it does support CRF, so I didn't notice Voukoder only having CQ as an option.

    You can see the preset number in the lil box below all the other options

    Preset 8 = Ultra Fast

    Preset 10 = Warp 9.975

    Just tried Voukoder 11.1-IntelARC with an Intel Arc a380 board and was able to do hardware renders for AV1(Intel QSV) in both Vegas 20 and Resolve18 Studio. But not with 11.3.2. Curious what ffmpeg is used for 11.1... I cannot find an ffmpeg with "av1_qsv" as an encoder... only as a decoder in 5.1-full.

    • Offizieller Beitrag

    The changes required for av1_qsv are not part of the latest stable FFmpeg 5.1 release yet. It is currently custom built from an unstable version where issues have been experienced already. Once FFmpeg supports it in a stable release (maybe 5.2?) it will be fully supported in the normal voukoder release.

    Thanks. Also, for some reason not seeing h264_qsv or hevc_qsv encoders on my systems with uhd630 or uhd750 igpus if I install 11.3.2. But they do show up if I install 11.1. Can also encode with them in Win releases of ffmpeg 5.1 from gyan and btbn.

    • Offizieller Beitrag

    I don't know about this. The IntelArc release (and also all future later versions of Voukoder) is using Intels new OneVPL framework instead of MFX. I'm not sure if the supported chipsets change with this switch.

    Here's the Voukoder dialog/codecs I get on a 9900k/uhd630/Radeon7 system with Voukoder 11.1 running Vegas 20:

    The Intel Qsv stuff goes away if I update to 11.3.2. Same deal on my 11900k/Arc380/6900xt system except I see more qsv with 11.1... adds qsv av1 and qsv vp9. But only if I point windows to Intel in display/graphics entries for the host app... set either to power saving (win10) or specific gpu (latest win11). When I run ffmpeg 5.1 itself, it is only influenced by the windows setting for decoding, not encoding. It just doesn't have av1_qsv and vp9_qsv but it's got the other 2 encoders no matter what the windows setting is.