Converting large DivX5 archive to AV1. Goal is to make it accessible by modern browsers for next 20 years.

While DIVX codec is responsible for starting movie piracy on internet is surprisingly very low quality, videos are very blocky. Its modified H263 codec. I did few testing and open theora codec seems to be better than divX.

AV1 includes pretty decent deblocking filter. Just converting to AV1 will significantly increase visual quality and practically all blocking will be removed. Just few videos needs additional deblocking in ffmpeg. I use deblock with block=16 and hqdn3d= 1.5,1.5,6,6 (parameters and filters suggested by chatgpt after uploading few sample images and before / after images).

after A/B/C testing I determined that I will go with CRF=23. PSNR/SSIM tests didn't yield usable results. Most times worse values looked visually better. lag-in-frames=25 and aq_mode=3 further improved quality and reduced file size.

Audio converted from PCM16 to 90kbits VBR LibOpus 1.5.

Result Video size reduced from 5633KB (divX5 + PCM16) -> 819KB (AV1+OPUS). While improving quality because of AV1 denoise/deblocking.

Hi, im using SvtAv1EncApp to test AV1's two pass mode.

My command is as follows:

SvtAv1EncApp -i .\vidyo1_720p_60fps.y4m --rc 1 --tbr 300 --passes 2 --stats ./av1logs/svtav1log.stat --progress 2 -b output.ivf

The clip comes from Xiph.org Video Test Media [derf's collection].

The file plays fine via ffplay, however I'm concerned about the filesizes being slightly different run to run.

I ran the above command about ten times, and got bitrates ranging from 296.57kbps (371331 bytes) to 297.32kbps (372271 bytes), so a variation of around +/- 1kbps.

Is this normal? I thought codecs as a whole are deterministic. I looked up film grain and it's disabled by default in this build, but to make sure i set it to 0 and the results were the same. Can this be a quirk of two-pass encoding?

Is this something to be concerned with?

Hey, I'm a twitch streamer trying to do research on cards that'll encode to AV1 for whenever AV1 encoding formally becomes accepted on twitch.

Atm I'm using my RTX 4090 to encode to AV1 (the twitch beta), but the number of outputs is pretty sad.

I was looking at the AMD MA35D card for a 2-PC stream set up, but that card is like $1600 usd, and that's more than I want to spend.

I'm not very good at tech stuff, so I honestly don't know for sure, but I feel like there has to be a cost friendly consumer card that'll output AV1 encoded streams at scale with a more than a 4090 card, but perhaps less hardcore than the MA35D.

This is an informational post regarding the m4 mac mini (base spec) performance and comparing it to an x86 mini pc, specifically the aoostar gem10 7940hs. I have seen geekbench numbers of the m4 but have not seen encoding performance so hoping this may give insight to those curious.

Firstly, geekbench 6 results performed which are in line with what I've seen online:

• m4 mac mini
• aoostar gem10 7940hs

Both machines compiled ffmpeg, svt-av1-psy, and libopus from source at equivalent compilation settings using the same library versions:

ffmpeg version: ffmpeg version git-2024-12-13-90af8e07
svtav1 version: SVT-AV1-PSY v2.3.0-1-g916cabd (release)
libopus version: libopus.so.0.10.1-g7db2693

The input clip was a 2 minute 4k HDR DV clip with multiple audio clips/channels and subs:

Video
Format                                   : HEVC
Format/Info                              : High Efficiency Video Coding
Format profile                           : Main 10@L5.1@High
HDR format                               : Dolby Vision, Version 1.0, Profile 7.6, dvhe.07.06, BL+EL+RPU, no metadata compression, Blu-ray compatible / SMPTE ST 2086, Version HDR10, HDR10 compatible
Codec ID                                 : V_MPEGH/ISO/HEVC
Duration                                 : 2 min 1 s
Bit rate                                 : 68.5 Mb/s
Width                                    : 3 840 pixels
Height                                   : 2 160 pixels
...
Audio #1
Format/Info                              : Meridian Lossless Packing FBA with 16-channel presentation
Commercial name                          : Dolby TrueHD with Dolby Atmos
Codec ID                                 : A_TRUEHD
Duration                                 : 2 min 0 s
Bit rate mode                            : Variable
Bit rate                                 : 5 026 kb/s
Maximum bit rate                         : 8 175 kb/s
Channel(s)                               : 8 channels

The input clip was encoded with the following params:

-pix_fmt yuv420p10le -crf 25 -preset 3 -g 240 film-grain=14:film-grain-denoise=1:adaptive-film-grain=1:sharpness=3:tune=3:enable-overlays=1:scd=1:fast-decode=1:enable-variance-boost=1:enable-qm=1:qm-min=0:qm-max=15

And output was:

Video
Format                                   : AV1
Format/Info                              : AOMedia Video 1
Format profile                           : Main@L5.0
HDR format                               : Dolby Vision, Version 1.0, Profile 10.1, dav1.10.06, BL+RPU, no metadata compression, HDR10 compatible / SMPTE ST 2086, Version HDR10, HDR10 compatible / SMPTE ST 2086, Version HDR10, HDR10 compatible
Codec ID                                 : V_AV1
...
Audio #1
Format                                   : Opus
Codec ID                                 : A_OPUS
Duration                                 : 2 min 0 s
Bit rate                                 : 474 kb/s
Channel(s)                               : 8 channels

Timing for the m4:

real    37m25.461s
user    320m11.437s
sys     1m8.569s

and timing for the gem10:

real    25m19.849s
user    316m15.012s
sys     0m58.333s

Average wattage for the m4 and gem10 reached 34w and 62w respectively.

TLDR: Despite what geekbench results say, m4 mac mini is not more powerful than relatively new x86 mini pcs right now for CPU dependent workloads, at least in this instance for video encoding. M4 mac mini is however more performant per watt and generally cheaper only comparing at the base spec.

I tested AV1 "Main" fullHD 30fps profile at several old computers, like 10 years old.

They decode AV1 video flawlessly in full screen without frame drops. Most CPU intensive task on these computers is web browser - they will not be able to do DOM animations + AV1 decoding.

There is high performance drop moving to 1440p

H.265 CRF 20/24 preset Slow

Hi, using FF Works, GUI for FFMPeg on Mac.
Having been trying out AV1 movie compression and am impressed with compression rate (using SVT-AV1) compared to the HEVC I was used working with.
But I'd like to understand the three different settings available for AV1 conversions :

1. Quality Mode
2. Constant quality factor mode (CRF 20 as baseline)
3. Bitrate mode

Basically I'm converting 1920x1080 H264 recordings.
In quality mode, it doesn't matter how high i put the quality (50-100%), I'm always getting the same output size. Why ?
Upping 2. even a bit (from 20 to 23) I'm getting about a 20% increase in size but no noticeable quality difference.
In bitrate mode, going from standard high quality (199906.56 Kb/s) to very high quality (29859,84) gives me an error.

Can anyone help me wrapping my head around this ?

At the same filesize, but relatively low bitrates, which would produce better visual quality?

Im trying to figure out why there is such a large difference in encoding time, using seemingly the same parameters.

For example, with FFMPEG, I get these results:

# 5:23 to complete 
# 216M
ffmpeg -i test.mkv \
       -y \
       -c:v libsvtav1 \
       -crf 25 \
       -preset 6 \
       -vf "scale=1920:1080" \
       -c:a libopus \
       -b:a 192k \
       test.mp4

With av1an, I get the following:

# 17:19 to complete
# 221M
av1an -i test.mkv \
      -y \
      -e svt-av1 \
      -a "-c:a libopus -b:a 192k" \
      -f "-vf scale=1920:1080" \
      -v "--rc 0 --crf 25 --preset 6" \
      -o test.mp4

Theyre using seemingly the same settings, but the av1an encode is taking more than 3x longer. I was trying to switch to av1an because I assumed it would be faster with it being able to utilize more of the CPU, and I doing something wrong here?

Specs:

Ryzen 7 3700x

32 GB DDR4 3200mhz

Hi guys! I've been PC shopping recently. I want to record/edit/stream 1440p60 video (mostly games). I'm relatively confident that an i5-12600k and a 7700xt will work well when recording the games I play in HEVC (GPU handling the graphics while the igpu handles encoding with intel quick-sync).

However, the i5-12600k's (and intel's 13/14th gen processors) igpu can't encode in AV1. With that in mind, I think I'd have to upgrade my GPU to something like an NVidia 4700 super to make use of nvenc for encoding. This would be about $200 more than getting the 7700xt.

So this question is two-fold: does that sound like sound reasoning? and is encoding in AV1 as opposed to HEVC worth the extra $200?

Here's a link to the full PC part list: https://pcpartpicker.com/list/7kqgt3

After asking around and receiving many different answers, I been wondering if AVIF is really an image or just a AV1 video. So, which is it, an image or a video format?

Do AVIF files (lossy or lossless) support HDR colors while png ones do not? Do animated AVIF files support them?

Edit: Sorry about the title! I somehow obliterated most of it and now I can’t edit it…

Trying to encode a show that contains a sharp increase in film grain partway through the episode. Is it possible to vary the synthetic film grain characteristics by time/frame in the film grain table? If so, is there any good documentation on how to do this? Tried searching around but couldn't really find any solid docs on how to construct the film grain table. Does it just come down to, say, reading the implementation of one of the encoders?

Has anyone tested using HandBrake on a handheld gaming device to encode videos in AV1 format?

Hey all. Pulling out what's left of my hair to get this sorted out. I think I might have the answer but I don't know enough about this to be sure.

Built a new box with a Ryzen 3 4100 and an Arc A380 card. This is replacing a NUC with an i3-7100U and no dedicated GPU, just onboard graphics. AV1 files on the NUC will play back with the CPU getting pinned with AV1 transcoding disabled in Jellyfin. Enabling AV1 transcoding on the NUC stops playback. AV1 will not play back at all in any combination I've tried on the new server. FFMPEG fails with error 187

I don't understand how the NUC is able to play back at all considering its CPU was released in 2017 which is before the initial release of AV1 as far as I can tell. I had issues playing back AV1 from the NUC last year from my TV, but it apparently works from a NVIDIA Shield I've since purchased. That's neither here nor there, though I'm still confused even though something about the NUC is able to process AV1. This led me to ask the question, "can the Ryzen 4100 understand AV1?". It doesn't have onboard graphics and I, apparently stupidly, figured that didn't matter because the tasks would be offloaded to the GPU. I understand the CPU still needs to understand what's being handed off, but this honestly didn't occur to me

Bit of some maybe relevant backstory, I went Ryzen with this build because I had a spare Ryzen 5 2600 sitting around. I figured I'd put it to good use since this new build didn't need to be a CPU workhorse only to realize it's too old to support rebar. The motherboard I got supports rebar with a compatible CPU, so I opted to get the cheap 4100. Also worth noting I installed the non-free Intel drivers and mirrored the configuration of my existing Jellyfin setup which does transcode other formats successfully if the playback host needs it

So here are my questions:

• Is this actually the problem? If yes:
  • What Ryzen CPU should I get instead so I don't have to replace the board?
  • Should I abandon Ryzen altogether and go Intel?

I just got a new 12 gen I5 and I'd love to shrink my library of 4K and 1080p remuxes. Lots of my movies do have film grain, and are older 80s and 90s movies, I also have a mix of newer movies and most of them are action movies, so lots of fast moving objects and dark spots. I would love to try to keep the video as clear as possible with not many visible artifacts, I will deal with audio separately.

The software I could use is Handbrake and FFmpeg, any recommendations on settings for handbrake or FFmpeg?

People in this subreddit has Posted a lot of Av1 support being added to this new mobile chip. Has anyone seen it in real hardware?

I currently see 2 devices red magic 10 pro, iqoo 13 which are using snapdragon 8 elite.

The phone specs sheet don't show anything about av1.

Anybody here know how to build libdovi on macOS such that SVT-AV1-PSY’s build.​sh can integrate it during compilation?

I’ve tried everything I can think of, but I just can’t get it to work. I can’t tell whether the documentation is just insufficient, I’m dumb, or both. And I know SVT-AV1-PSY with Dolby Vision can run on Mac, because I have the PSY branch of HandBrake running on my machine right now. (But it’s unsuitable for the transcoding I have in mind because it can’t utilize external film grain synthesis tables.)

All the variants of cargo cbuild I’ve tried result in Error: CliError { error: Some(none of the selected packages contains these features: capi), exit_code: 101 }. At this point I’m just...

me thinking “this might be my 13th reason”

Anyway, here are the relevant pages; the links jump to the key part of each page:

https://github.com/gianni-rosato/svt-av1-psy#:~:text=0%20(no%20sharpness).-,--dolby-vision-rpu%20path,info)%20(Thank%20you%20%40quietvoid%20!),-Progress%203

https://github.com/gianni-rosato/svt-av1-psy/blob/master/Docs/PSY-Development.md#:~:text=if%20you'd%20like%20to%20build%20with%20dolby%20vision%20support%2C%20you%20can%20do%20so%20by%20adding%20--enable-libdovi%20to%20the%20build%20script's%20args.%20this%20assumes%20you%20have%20libdovi%20installed%20on%20your%20system%20already%2C%20which%20is%20a%20separate%20process%20related%20to%20dovi_tool.

https://github.com/quietvoid/dovi_tool/blob/main/dolby_vision/README.md#libdovi-c-api

https://crates.io/crates/dolby_vision

🙏🏻

According this info 12th and 13th Generation Intel® Core™ Processors: can decode AV1 up to 16K!

I wonder have anyone tried this and is this true ?

Thanks !

hey guys,

i been a couple of posts (one by bitmovin) that the facebook app in ios now plays av1 videos on older iphone devices, probably with software decoding.

is that an option ?

Hello. Could anyone please give me an advice about AV1? I plan on buying a MacBook air using a black friday discount, my choice was the m2 version since it's cheaper than m3 and I'm not some sort of a power user that needs everything to be the newest fresh from the oven. Right now I'm using an old MacBook pro from 2015 and it's still great for me. Anyway, yesterday I found out that one of the biggest differences between m2 and m3 chips is the presence of an AV1 decoder on the m3 version. I really try to understand what that means but I need some advice. What does is mean that some websites are using AV1 and it's better to have a decoder build in? Are websites like YouTube (the most important for me) or Netflix using AV1 right now? Or are they only plan to use AV1 in the future? How would you choose between those two computers, is AV1 decoder really a deal breaker? Please be kind with me, I'm very new to this thing. Thank you in advance

I'm trying to use the svt-av1 encoder interface so I can try out custom film grain tables with the --fgs-table option (since this cannot be passed via ffmpeg currently). However I'm running into trouble just trying to do a sanity encode test. The output video from SvtAv1EncApp shows a weird messed up version of the video, implying either my encode settings or my raw YUV video is wrong.

My source video is 4k HDR (BT2020 space) with a frame rate of 23.98 (24000/1001). I sampled it using the following command

ffmpeg -i movie.mkv -ss 00:20:20 -t 00:00:05 -an -sn -c:v copy sample.mkv

Converted it to a raw video using

ffmpeg -i sample.mkv -f rawvideo -pix_fmt yuv420p -s 3840x2160 sample.yuv`

Then finally ran it through SvtAv1EncApp

SvtAv1EncApp -i sample.yuv -b OUT_sample1.mkv --progress 3 \
--fps-num 24000 --fps-denom 1001 \
--svtav1-params enable-hdr=1:width=3840:height=2160:preset=8:crf=20

But there's two things odd about the output and encode:

1. SVT AV1 only encoded 54 frames which is about 2s of video, but the video is 45s long, so I would have expected around double that amount of frames to be encoded
2. The output video itself is mangled: https://ibb.co/BTrVN67

I didn't see any errors printed to stderr, but here's the log of the encode:

• https://pastebin.com/XBRB0B5v

I'll point out I'm using the fork SVT-AV1-PSY, but I have used this encoder before in ffmpeg with no issues.

I want to encode Blu Ray to AV1 for specific use cases. I have a Nvidia RTX4060. Would 100% GPU encoding to AV1 work with it? Could you recommend a setting similar to

ffmpeg -hwaccel cuda -hwaccel_output_format cuda -i input.mkv -map 0:v -map 0:a:1 -c:v hevc_nvenc -preset p7 -b:v 0 -cq 25 -c:a libopus -ac 2 -b:a 128k output.mkv

with the same or better quality? I tried myself, but forgot to change the cq value and got a file bigger than the input file, went to 20 GB from 16 GB (FullHD). :-|

One last question: What would your recommendation be for reencoding documentaries (in FullHD, but with lots of details)? Doesn't need to be GPU encoding, just fast enough while still retaining most of the quality. Codec doesn't matter if you have good recommendations for H.264 or H.265.

Preferably command line (ffmpeg), I'm oldskool.

My use case is video (and audio) just barely good enough for casual viewing on a phone, so I can cram a whole bunch of passable entertainment on there. I've been using SVT-AV1 at 360p, CRF 55, preset 4, which for low-motion live action ends up at around 100 kbps or less when paired with 16 kbps Opus. Very small motion like mouth movement in a wide shot occasionally gets smoothed over, but not often, and overall it's good enough that I can watch the content without thinking about the quality.

However, I recently found myself needing quick encodes to watch videos in such an old format that they wouldn't play on my phone, and I used AVC for speed. Using x264 at 360p, with a CRF of 30 or 32 and Opus at 24 kbps, I got a similar total of around 100 kbps for 2D animation, and it was still 100% watchable on my phone. At that bitrate, I thought AVC would look terrible.

I thought AV1 had unmatched efficiency at minimal bitrates, but now I'm not so sure. Maybe I've misunderstood its exact niche. Is AV1 a good fit for this use case? If not, what's the best alternative?

I like its results for synthetic content and would like to replicate that in an independent workflow.