AV1

I've been using this command for running rav1e encoder:

ffmpeg -i test.mkv -pix_fmt yuv420p -f yuv4mpegpipe - | rav1e - --first-pass --quantizer 100 --speed 10 --tiles 8 --tune Psychovisual --second-pass --quantizer 100 --speed 10 --tiles 8 --tune Psychovisual --output output.ivf

But all it does is give this error:

av_interleaved_write_frame(): Invalid argument Last message repeated 3 times Error writing trailer of pipe:: Invalid argument

Does anyone know the correct syntax for two pass encode in rav1e?

-aq-mode E..V..... adaptive quantization mode (from -1 to 4) (default -1)

none E..V..... Aq not used

variance E..V..... Variance based Aq

complexity E..V..... Complexity based Aq

cyclic E..V..... Cyclic Refresh Aq

These are the options I get in FFmpeg, however I don't know in what mode it should be used, or how to properly use it, any input would be highly appreciated.

I've been trying to get used to C# because I've never really developed anything with it, except with C++.

WARNING This is still in a very early state, if you notice bugs or want some features added, comment below and I'll do my best.

Download link

GitHub https://github.com/Monteco/AV1TSU

GitHub repo coming soon.

Works only on Windows 64bit.

Which one do you prefer? Any reasons why?

I though it would be possible to mash CRF into 2 pass, but apparently it's not how it works. I knew I couldn't do it with HEVC and h.264 but I though that AV1 processes video differently.

So, are there any bitrate savings using one mode or another while achieving the same quality or are they the same?

I think it would be very useful to compile a list of what encoding performance we can achieve with our systems, however for we need a good source that would push AV1 to it's limits.

Requirements :

Should be quite short, around 1 minute for acceptable benchmark time.

Has to contain a wide array of scenes, such as tree leaves, fast moving objects, dark scenes with gradual lighting, wide array of colors, confetti or snow scene, noisy image, text, animation (Other suggestions what a should should contain are highly welcome).

Resolution, about this I am not so sure, maybe 1080p or we could divide it into 720p, 1080p and 4k, but it would be better to stick to one file to remove any additional confusion for new users, however this decision is not final.

Source file should be very high quality, near transparent, or completely lossless.

It should be royalty free for legal reasons.

I am waiting for your opinions about this, and how we could solve the lack of benchmarking information. When the source file is found, we will later decide on what settings it should be encoded.

Have some extra money (around 70 euros) and was thinking what kind of used CPU I should get, I need it to be a CPU and motherboard combo.

So far I've seen i5 2500k that can fit in my budget, however it seems that xeons are pretty good price/performance ratio for the money, but their motherboards are awfully expensive.

Planning to encode AV1 videos 24/7 so low power would be great, but it's not high priority.

I've been doing some encoding with Rav1e recently and noticed weird behavior with quantizer settings.

When encoding HEVC video with CRF settings, the size varied depending from the encoding speeds, sometimes it got a little bigger or smaller.

However with AV1 quantizer settings, the size does not change no matter what speed I encode with (tried with 10 to 3), only the encode quality changes.

It seems to me that Quantizer setting on Rav1e wroks more as a bitrate option, rather than quality metric.

Here are some sample files:

Quantizer at 10: link

Quantizer at 8: link

Updated ffmpeg and rav1e interpreter for easier AV1 encoding, now it has audio, audio options, video tune, and a few other things.

Download here

As part of my efforts to make an AV1 benchmark tool, I wrote a very simple program to make AV1 video encoding easier. How to use it:

Download and extract the folder

Drag and drop any video file into the folder

Launch encoder.exe file

Write what it asks for and press enter (filename must also include it's file type, ex: .mkv, .mp4)

Output file will be named output.ivf

For now it might not include audio, and expect it to be buggy, however I will improve it. Report issues in the comments, I will read them.

I've been trying out many different programs for encoding AV1 format videos, however many of them had different issues like bad support, or being very outdated.

Then I found out Axiom, made by a fellow reddit user MattMcManis. It is a GUI for FFmpeg, it is very flexible compared to handbrake because it doesn't come with FFmpeg built into it, that means you can update them independently, always making sure your codec is up to date.

So I decided to contact Matt and was very impressed by the active support this program had, I even asked for a small guide on AV1 encoding and he delivered.

Beware because AV1 is still in an experimental phase, you will encounter some quirks, for now it seems FFmpeg doesn't support webm container for AV1, however mkv seems to be working fine. Also you might expect of the encoding to slow down at the very end, but be patient, it just got really slow, even for AV1 standards.

Things that you will need to start encoding AV1:

Nightly build of FFmpeg

Latest Axiom version

Extract Axiom, FFmpeg

Open Axiom

Axiom will automatically detect required FFmpeg files for encoding if the ffmpeg folder is in the same directory as Axiom.exe.

If it doesn't detect, then go to settings and locate FFmpeg, FFprobe and FFplay(They should be in extracted ffmpeg folder/bin).

You can also put the ffmpeg folder in your C:\Program Files and set your Windows Environment Variables to use ffmpeg, Axiom will detect it from anywhere.

And you are ready to encode, again if you want to check what settings to use, use this guide and if you need a user guide, you can find it here, which you can also find it in Axiom folder.

Big kudos to MattMcManis for making this amazing program.

If you encounter a problem, please post a comment detailing it, Matt and I will try our best to find a solution to it.

https://www.ffmpeg.org/

http://www.streamingmedia.com/Articles/Editorial/Featured-Articles/NAB-2018-Mozilla-Talks-Daala-Firefox-and-AV1-124396.aspx

http://www.streamingmedia.com/Articles/Editorial/Featured-Articles/Commentary-HEVC-and-AV1-A-Behind-the-Scenes-Look-at-the-Video-Codec-Race-124245.aspx