Alliance for Open Media codecs

[hydra3333]

Excelent post :thanks: And +1

[Tommy Carrot]

If anyone is curious how the encoding speed improved in the last half year or so, here's a little comparison between the different versions:

version | enc time | filesize
0.1.0-9348 | 152 | 183494
0.1.0-9559 | 119 | 182391
0.1.0-9658 | 109 | 182118
1.0.0-6 | 94 | 182856
1.0.0-82 | 86 | 182952
1.0.0-181 | 61 | 184139
1.0.0-245 | 59 | 189154
1.0.0-399 | 51 | 180221
1.0.0-541 | 22 | 184505
1.0.0-629 | 15 | 184616


I used cpu-used=1 in all cases, and tried to match the bitrates as close as possible in constant quality mode. The encoding speed is still very slow, but as you can see, it finally started to improve at a higher pace lately (although the last 2 builds used CONFIG_LOWBITDEPTH=1, so they are not really comparable). Aomenc is still way too slow for any productive purpose, but at least it's possible to test it now.

[Nintendo Maniac 64]

Excelent post :thanks:

And +2



fight between Rider and Saber for whoever knows what I'm talking about

The original visual novel (https://vndb.org/v11) is better. :p

(and that's not all all because I've had a hand with some of the media stuff in the latest and upcoming unofficial English PC versions of "Fate/stay night Realta Nua" (http://forums.nrvnqsr.com/showthread.php/4745-Fate-Stay-Night-Realta-Nua-PC-version-Mirror-Moon-TL-insertion-project/page585), nope no way what 'choo talkin' bout Willis you crazy)

[NikosD]

If anyone is curious how the encoding speed improved in the last half year or so, here's a little comparison between the different versions:

version | enc time | filesize
0.1.0-9348 | 152 | 183494
.
.
1.0.0-629 | 15 | 184616


It seems it's an order of magnitude faster.

10 times faster is a lot, but obviously it has further big margins to improve.

I wonder how long is going to take for another 10 times improvement.

[SmilingWolf]

The original visual novel (https://vndb.org/v11) is better. :p

(and that's not all all because I've had a hand with some of the media stuff in the latest and upcoming unofficial English PC versions of "Fate/stay night Realta Nua" (http://forums.nrvnqsr.com/showthread.php/4745-Fate-Stay-Night-Realta-Nua-PC-version-Mirror-Moon-TL-insertion-project/page585), nope no way what 'choo talkin' bout Willis you crazy)

I'd have you fight me IRL for dissing anything ufotable, but that evened out after you gave me a reason to install FSN again :D
(And for being on the first line in the works, thanks to y'all for what you do!)

Also, the pre-edit "the original visual novel from 2004" was just fine, I didn't choose FSN just because the clips look good ;)

I wonder how long is going to take for another 10 times improvement.

That's an interesting question.
The 0.1.0-9348 (https://forum.doom9.org/showthread.php?p=1840615#post1840615) build is from April, so that's 146 days (https://www.timeanddate.com/date/durationresult.html?d1=29&m1=4&y1=2018&d2=21&m2=9&y2=2018&ti=on) between the first and the last tested build. Now, of course these things don't really follow a linear time-optimization correlation, buuuuut I wonder where we'll be in another 4 months :)
Maybe they'll get cpu-used=4 on par (speed wise) with x265's placebo-and-then-slowed-down-some-more, using the no-wpp etc. etc. settings benwaggoner suggested a few pages ago (https://forum.doom9.org/showthread.php?p=1849998#post1849998), which in my limited testing came around at half aomenc's time a week or two ago.
Also rav1e might become a real game changer for av1 encoding in the same timeframe. I surely hope so.

And a small heads up, Video Dev Days (https://www.videolan.org/videolan/events/vdd18/) have officially begun, and today they're going to showoff dav1d, their very own decoder!

Exciting times ahead!

[Selur]

And a small heads up, VideoLAN Developer Days have officially began, and today they're going to showoff dav1d, their very own encoder!
decoder not encoder
according to: https://www.videolan.org/videolan/events/vdd18/#saturday

[SmilingWolf]

Aye, caffeinated typo slipped in. Corrected, thanks!

EDIT: in the meantime, the presentation has finished. Does anyone know if there's a livestream or at least a youtube channel where they upload stuff as they go?

[nevcairiel]

EDIT: in the meantime, the presentation has finished. Does anyone know if there's a livestream or at least a youtube channel where they upload stuff as they go?

Unfortunately, I don't think so. Its rather hilarious that a open-source multimedia conference can't figure out streaming or at least on-demand videos afterwards. :)

[Mr_Khyron]

dav1d source code
https://code.videolan.org/videolan/dav1d
:)

[SmilingWolf]

dav1d source code
https://code.videolan.org/videolan/dav1d
:)

Uwheee!

dav1d-0.0.1-7-bb521ef9: https://mega.nz/#!w9xlxZpT!_KfDw7rp9LWMosjNIdSZeuqhgOr7PaHkG8eJgoHLwrg
EDIT: botched on Windows because of the usual open(file, "r") bug. Needs to be open(file, "rb") for binary objects, lest files be treated as text and the input mangled.
Will submit a patch ASAP
EDIT2: https://code.videolan.org/videolan/dav1d/merge_requests/12/diffs

[Zebulon84]

Previous Video Dev Days conferences are available on Vimeo (https://vimeo.com/videolan/collections) so I guess it will be the same for 2018. But videos for 2017 Video Dev Days were posted last may, so we may have to wait quite a while.

[hajj_3]

Previous Video Dev Days conferences are available on Vimeo (https://vimeo.com/videolan/collections) so I guess it will be the same for 2018. But videos for 2017 Video Dev Days were posted last may, so we may have to wait quite a while.

possibly, the 2016 ones were posted on their youtube channel in a timely manner: https://www.youtube.com/user/VideoLANorg/videos

[Nintendo Maniac 64]

Now the wait begins for dav1d to be implemented into LAVfilters and for my low multi-threaded utilization woes to be gone once and for all!

...please tell me I'm not being overly optimistic by saying that? The way I see it, a Xeon x3470 shouldn't be all too different from the likes of an i7-8550U seeing as the Xeon has a ~33% IPC deficit while the i7 has a ~33% clockrate deficit, so the end result should be pretty similar (not counting AVX anyway).

I mean, if its too slow on an i7-8550U, then it'll be too slow for almost all laptops in existence except for maybe those 6core i9 laptops and those crazy gamer/professional laptops that have full-fat desktop CPUs like that Asus with a Ryzen 1700.




you gave me a reason to install FSN again :DJust as long as it's that upcoming "merge project" mentioned on the last couple of pages at the end of the linked thread, otherwise I'll never forgive you. :p

(to clarify, the original visual novel only renders at 800x600 while this "merge project" will have HD visuals and high-res text - that alone should make it a no-brainer)


Also, the pre-edit "the original visual novel from 2004" was just fineI only removed the "2004" text because I thought using "original" would be clearer to convey that the visual novel came before any think else Fate-related.

[SmilingWolf]

Now the wait begins for dav1d to be implemented into LAVfilters and for my low multi-threaded utilization woes to be gone once and for all!

...please tell me I'm not being overly optimistic by saying that? The way I see it, a Xeon x3470 shouldn't be all too different from the likes of an i7-8550U seeing as the Xeon has a ~33% IPC deficit while the i7 has a ~33% clockrate deficit, so the end result should be pretty similar (not counting AVX anyway).

I mean, if its too slow on an i7-8550U, then it'll be too slow for almost all laptops in existence except for maybe those 6core i9 laptops and those crazy gamer/professional laptops that have full-fat desktop CPUs like that Asus with a Ryzen 1700.

I'm afraid we're not quite there yet. Using my most CPU-intensive clip (PresageFlowerFight, 1080 encoded with as many tiles as possible) I have only been able to observe a 45% max utilization with --framethreads 8
My CPU is an i7-4770, with 4/8 cores

Some timings:
# time ./dav1d.exe --framethreads 8 -o /dev/null --muxer yuv4mpeg2 -i Fight.cq20.1080p.ivf 2> /dev/null

real 0m19,460s
user 0m0,000s
sys 0m0,000s

# time aomdec.exe --threads=8 -o /dev/null Fight.cq20.1080p.ivf

real 0m5,170s
user 0m0,000s
sys 0m0,000s

Right now dav1d is implemented in pure C and of course it shows. It'll be more interesting after ASM optimizations start trickling in.

EDIT: after playing a bit with the numbers I've been able to push the times down a bit further and CPU util higher (50-53% range):
# time ./dav1d.exe --framethreads 6 --tilethreads 2 -o /dev/null --muxer yuv4mpeg2 -i Fight.cq20.1080p.ivf 2> /dev/null

real 0m17,800s
user 0m0,000s
sys 0m0,000s

I only removed the "2004" text because I thought using "original" would be clearer to convey that the visual novel came before any think else Fate-related.
I see, I see (https://www.youtube.com/watch?v=R8y1GILBUcc)

[hajj_3]

MPC-BE 1.5.2.3976 Beta has been released which can play my 1920x800 551kbps bitrate AV1 file that i have smoothly, used up to 46% cpu on core i3-7100U 2.4ghz

Link: https://sourceforge.net/projects/mpcbe/files/latest/download

[LigH]

New uploads: (MSYS2; MinGW32: GCC 7.3.0 / MinGW64: GCC 8.2.0)

AOM v1.0.0-643-gaf3e5cc66 (https://www.mediafire.com/file/z697gkw8877yhqu/aom_v1.0.0-643-gaf3e5cc66.7z)

rav1e 0.1.0 (d330de0 / 2018-09-23) (https://www.mediafire.com/file/u5wrgqg77ehukm0/rav1e_0.1.0_2018-09-23_d330de0.7z)

dav1d 0.0.1 (5e05e65 / 2018-09-23) (https://www.mediafire.com/file/djxkwy12x2cv3wq/dav1d_0.0.1_2018-09-23_5e05e65.7z)

[marcomsousa]

AV1 already have 3 encoders and/or decoders, it's a good start..

[olduser217]

I heard that Ateme demonstrated 4k60 AV1 decoding on TV (seems like LG TV) during the recent IBC Show.
Anybody attended the show and saw it?

[marcomsousa]

I heard that Ateme demonstrated 4k60 AV1 decoding on TV (seems like LG TV) during the recent IBC Show.
Anybody attended the show and saw it?

At NAB Conference:

ATEME: Video (https://www.youtube.com/watch?v=7_731UnjMuo)
Other AOMedia: Video1 (https://www.youtube.com/watch?v=CVFWZbolHhE) Video2 (https://www.youtube.com/watch?v=k6WSqb4O2x0) Video3 (https://www.youtube.com/watch?v=NW3h0s2E4EQ&list=PL97T7zfqOOF108asipLcqHAdTOkCGsFsa&index=3) Video4 (https://www.youtube.com/watch?v=aAayA_2jCb8)

[SmilingWolf]

32/64bits binaries:
av1-1.0.0-654-gd0076f507: https://mega.nz/#!kto20KoR!XbcrlXv7QZFRzks38Jqm8oss8P3IDlZx3X0tfeVwJx4

64bits binaries only (I don't have a 32bits toolchain in my MSYS2 env):
dav1d-0.0.1-37-9075f0e: https://mega.nz/#!co5wFQyQ!EZhG33K4zBp6MHbEqfFdNc3p2qvIKmdYdPPtDJqCWBw

The dav1d build has been patched so that the input/output files are opened in binary mode, for the reasons previously explained. Band-aid solution until the PR is accepted upstream.

[savage747]

I dusted off my own automated codec testing setup so I can track AV1-development. Of course, objective metrics do not replace subjective testing, but this should still be okay to get some very rough estimates.

The following graph takes about 45 minutes to generate on my Ryzen 2700 (8 cores, 16 threads). To keep things sane, I'm using --cpu-used=4, which is a somwhat "fast" setting.

The modern codecs may perform even better on HD resolutions.

[benwaggoner]

I dusted off my own automated codec testing setup so I can track AV1-development. Of course, objective metrics do not replace subjective testing, but this should still be okay to get some very rough estimates.
It can be VERY rough. It would be pretty typical for a new psychovisual feature to result in improved quality AND reduced scores with objective metrics. That is pretty much the defining feature of a psychovisual optimization :).

The following graph takes about 45 minutes to generate on my Ryzen 2700 (8 cores, 16 threads). To keep things sane, I'm using --cpu-used=4, which is a somwhat "fast" setting.

The modern codecs may perform even better on HD resolutions.
HEVC certainly has a bigger advantage over H.264 at UHD resolutions.

It's hard to say with AV1 since the encoders are so slow that there isn't a substantial corpus of high-quality HD AV1 encodes to evaluate yet. In theory it should also scale well, but today's encoders obviously haven't been able to get a lot of resolution-tuned psychovisual optimization yet.

A whole lot of AV1's discussed capabilities are more informed speculation than anything based on real-world demonstrations of real-world scenarios.

[IgorC]

Would it make sense just drop a bitdepth of 8 bits already? Especially now when AV1 was just realesed. All right, decoder optimizations and hardware support will come anyway.
Yes, 8 bits is faster to encode/decode but banding ruins a major part of quality gains at quite large range of bitrates.

VP9 8-bits vs 10 bits is a day and night difference.
https://sonnati.files.wordpress.com/2016/06/10bit2.png
https://sonnati.wordpress.com/2016/06/17/does-vp9-deserve-attention-part-ii/

Even VP9/HEVC 10-12bit are already so advanced to produce block-free video even at quite low bitrates.
I wouldn't be surprised if AV1 8 bits would look worse than VP9/HEVC 10-12 bits (or just comparable)

[olduser217]

At NAB Conference:

ATEME: Video (https://www.youtube.com/watch?v=7_731UnjMuo)
Other AOMedia: Video1 (https://www.youtube.com/watch?v=CVFWZbolHhE) Video2 (https://www.youtube.com/watch?v=k6WSqb4O2x0) Video3 (https://www.youtube.com/watch?v=NW3h0s2E4EQ&list=PL97T7zfqOOF108asipLcqHAdTOkCGsFsa&index=3) Video4 (https://www.youtube.com/watch?v=aAayA_2jCb8)

Thanks for the video link.
Just curious whether the Ateme demo was done with existing TV hardware (assuming software decoding with ARM based SOC), or the TV was just been used as a display for decoding done with PC.

[Blue_MiSfit]

Well, they were using the player in the TV (at least, it looks like the standard LG player UI) - so my guess is a special engineering prototype TV with an FPGA or something in it :devil:

[benwaggoner]

Would it make sense just drop a bitdepth of 8 bits already? Especially now when AV1 was just realesed. All right, decoder optimizations and hardware support will come anyway.
Yes, 8 bits is faster to encode/decode but banding ruins a major part of quality gains at quite large range of bitrates.

VP9 8-bits vs 10 bits is a day and night difference.
https://sonnati.files.wordpress.com/2016/06/10bit2.png
https://sonnati.wordpress.com/2016/06/17/does-vp9-deserve-attention-part-ii/

Even VP9/HEVC 10-12bit are already so advanced to produce block-free video even at quite low bitrates.
I wouldn't be surprised if AV1 8 bits would look worse than VP9/HEVC 10-12 bits (or just comparable)

HEVC eliminates most of the 10-bit advantage over 8-bit that H.264 had. If the source doesn’t have banding, you don’t get much new banding even at lower bitrates. I think AV1 should have ballpark similar improvements.

But yeah, it would be great if the “Main” profile for future codecs always supported at least 10-bit. That’s required for HDR, which is quickly becoming mainstream. It’s not like the SoC or GOU vendors are developing 8-bit only decoders anymore, even if some display pipelines are 8-bit RGB. But 10-bit 64-960 4:2:0 Y’CbCr makes for better 0-255 RGB 4:4:4 anyway.

[benwaggoner]

Well, they were using the player in the TV (at least, it looks like the standard LG player UI) - so my guess is a special engineering prototype TV with an FPGA or something in it :devil:


If it’s a fast 8-core ARM or something, software decode should be feasible, especially if the GPU was leveraged for some operations. Decoder optimization is a LOT easier and faster than encoder optimization, since there is only one right answer for decoding. We’ll have a good idea of the potential performance of AV1 decoders way before we will for encoders.

[blurred]

Interesting discussion: https://www.reddit.com/r/linux/comments/9i4h7y/av1_video_samples_now_available_on_youtube_netflix/

It points some FSF licensing issues from 2010:
- https://www.fsf.org/blogs/community/google-free-on2-vp8-for-youtube :"Until we move to free formats, the threat of patent lawsuits and licensing fees hangs over every software developer, video creator, hardware maker, web site and corporation -- including you."

- https://www.fsf.org/blogs/licensing/googles-updated-webm-license : "Unfortunately, the interaction between the copyright license and the patent license made the result GPL-incompatible. Based on the concerns of developers writing GPL-covered software, Google publicly stated that they would take some time to review the WebM license and try to address the community's concerns. Today, they released a revised license, and it is GPL-compatible."
"The most important part of the change is that Google has separated the patent license from the copyright license. Now the copyright license on the software is a totally standard three-clause BSD license, which is clearly compatible with the GPL. The patent license, in turn, provides distributors with permission to exercise all the rights, and meet all the conditions, in the GPL, as required by GPLv2 section 7; and those permissions are consistent with the ones provided by the patent grant in GPLv3 section 11. All this means that developers distributing GPL-covered software can take advantage of the patent license without running afoul of the GPL's conditions, whether they're using GPLv2 or GPLv3."

Does it still apply to AV1?

[SmilingWolf]

MSYS2/GCC 8.2 builds:
av1-1.0.0-692-g16c9affcb: https://mega.nz/#!U1AVFI5R!jPhrtngqfp0uNnVUo-GLfZMDT-h8Yl8p05ACp9Fn4Ok
dav1d-0.0.1-103-deab253: https://mega.nz/#!xpAHSYwB!hA4Unc81jOTbhxgKrCCRTMd0qKqaX3oODqiV3cs3ZP8

dav1d builds are also available here: https://code.videolan.org/videolan/dav1d/pipelines
Cloud button on the right

The first ASM routines for dav1d have been checked in! Time to benchmark again :)

[TEB]

I heard that Ateme demonstrated 4k60 AV1 decoding on TV (seems like LG TV) during the recent IBC Show.
Anybody attended the show and saw it?

Yupp saw it, but infact it was a HEVC encoded output from a AV1 source (high bitrate) as far as i know..

[Mr_Khyron]

https://www.twoorioles.com/
Offering unprecedented compression gains, high video quality and broad industry support, AV1 promises to be the next universal video compression standard. With 20 to 30 percent better quality than VP9 and HEVC, AV1 has buy-in from such technology leaders as Google, Apple, Microsoft, Netflix, Amazon, Intel, Cisco, Facebook and Mozilla. We’re helping to lead the charge with the industry's first commercial encoder for AV1. As part of our EVE (Efficient Video Encoder) family, EVE for AV1 is in beta testing with several industry partners. With our 16 years of video compression innovation, we’re making the promise of AV1 a reality.
https://www.twoorioles.com/eve-for-av1/

[Mr_Khyron]

Alibaba Cloud, the cloud computing arm of Alibaba Group, has joined the Alliance for Open Media (AOMedia) as a Promoter member. Alibaba Cloud will collaborate with AOMedia and other industry leaders in pursuit of an open and royalty-free AOMedia video codec, AV1.
https://aomedia.org/alibaba-cloud-joins-the-alliance-for-open-media/

[benwaggoner]

https://www.twoorioles.com/

https://www.twoorioles.com/eve-for-av1/
I really wish PR and such would stop throwing around this "20-30% better than HEVC and VP9" stuff. There is no way to know if that's achievable or not yet, without mature AV1 encoders. And we know that the best HEVC encoders can outperform the best VP9 encoders by easily 20-30% for real-world scenarios, so a quote assuming VP9 and HEVC are equivalent just invalidates the AV1 comparison.

Honestly, finding real-world scenarios where libvpx can deliver better quality @ bitrate @ perf than x264 is a challenge, although I suspect that's primarily due to x264's massively greater psychovisual tuning and perf optimization efforts, not differences in the bitstream standards.

[NikosD]

I really wish PR and such would stop throwing around this "20-30% better than HEVC and VP9" stuff. There is no way to know if that's achievable or not yet, without mature AV1 encoders...
Honestly, finding real-world scenarios where libvpx can deliver better quality @ bitrate @ perf than x264 is a challenge, although I suspect that's primarily due to x264's massively greater psychovisual tuning and perf optimization efforts, not differences in the bitstream standards.
I think the same could be said for HEVC too compared to AVC.

I remember the days when x265 was claiming 50% more compression for the same quality compared to x264, but you have to dig too much to find such a case, if any.

[olduser217]

Yupp saw it, but infact it was a HEVC encoded output from a AV1 source (high bitrate) as far as i know..

Do you mean that the AV1 bitstream was actually transcoded to HEVC stream and then playback using the LG TV?
If this is the case, it seems like the purpose was to showcase the AV1 encoding/transcoding capability rather than decoding of AV1 on existing SOC hardware.

[LigH]

@olduser217: I understood that the same way...

[marcomsousa]

Do you mean that the AV1 bitstream was actually transcoded to HEVC stream and then playback using the LG TV?
If this is the case, it seems like the purpose was to showcase the AV1 encoding/transcoding capability rather than decoding of AV1 on existing SOC hardware.

@olduser217: I understood that the same way...

They are a software company. They have a software solution that permit encoding and transcoding to BIG companies.
So, a big company can (in 2019) store in AV1 format and transcoding to ANY format LIVE.
Or encoding from ANY format to AV1.
At this moment, they are changing their solution to be Public Cloud Server friendly. Changing to microservices architecture capable to scale any number of servers automatically.

PS: They don’t have anything magically, so encoding it’s still slow and expensive.

[olduser217]

They are a software company. They have a software solution that permit encoding and transcoding to BIG companies.
So, a big company can (in 2019) store in AV1 format and transcoding to ANY format LIVE.
Or encoding from ANY format to AV1.
At this moment, they are changing their solution to be Public Cloud Server friendly. Changing to microservices architecture capable to scale any number of servers automatically.

PS: They don’t have anything magically, soy encoding it’s still slow and expensive.

@marcomsousa @LigH
Thanks for the explanation.

So, for the exhibition, the AV1 bitstream (I heard during the demo, the AV1 source was from an USB thumbdrive which was plugged into the TV) was uploaded to their server and downloaded as HEVC bitstream, then playback from the TV which support HEVC decoding?

[hajj_3]

Video Dev Days 2018 videos:
https://www.youtube.com/watch?v=1bSsP0Wi46E - AV1: in the end, what got in?
https://www.youtube.com/watch?v=ytsRYKQc6kQ - rav1e: the best rust AV1 encoder
https://www.youtube.com/watch?v=UhIgBdrKyNM - Dav1d: a fast new AV1 decoder

[marcomsousa]

...

Thanks, just add a new dav1d video and labels

Google AOM

Chrome (Q4 2018)
WebRTC Integration (2019)
Android Q (Q3 2019)
SOC Hardware (2020)

[Beelzebubu]

And we know that the best HEVC encoders can outperform the best VP9 encoders by easily 20-30% for real-world scenarios, so a quote assuming VP9 and HEVC are equivalent just invalidates the AV1 comparison.

[..]

libvpx

I'm all for pointing out PR for what it is, but to equate "libvpx" with "best VP9 encoders" is inherently unfair as an argument against an actually-good VP9 encoder.

[LigH]

The media-autobuild_suite already allows using libdav1d in ffmpeg; unfortunately, from time to time, other libraries may break it, so consider to exclude what you don't really need...

[benwaggoner]

I think the same could be said for HEVC too compared to AVC.

I remember the days when x265 was claiming 50% more compression for the same quality compared to x264, but you have to dig too much to find such a case, if any.
I have seen 50% reduction at very low bitrates and UHD resolutions. But for moderately grainy SD/HD content, x264 versus x265 is more like 30%.

Grain/noise parameterization and reconstruction is probably the single biggest next step in encoding performance, since random noise is intrinsically uncompressible.

[benwaggoner]

I'm all for pointing out PR for what it is, but to equate "libvpx" with "best VP9 encoders" is inherently unfair as an argument against an actually-good VP9 encoder.
I wasn't specifically calling out libvpx here, but I've not been able to get a real-world comparison of anything substantially better in terms of potential quality (not even quality @ perf).

I'm quite curious about what Eve can really do! But I've struggled to find samples for which source is available so I can try a real apples-to-apples. Their website seems to just have frames, not even any actual video examples.

If anyone can point me towards any, I'd really appreciate it, and could probably make some comparative HEVC encodes available.

For example, here's a recent Tears of Steel x265 test I did (1.5 Mbps average 4 Mbps peak, max 5 sec GOP, unlimited encoding time)

https://1drv.ms/v/s!AlvIQZWsyeO-kKplp2EQ8-Q4bCNVZw

It is pretty awesome that we can deliver a pretty good 1080p experience at VideoCD bitrates! 20x more pixels, and I think better per-pixel quality.

I've been doing 1, 1.5, and 2 Mbps ToS encodes using x265, x264, xvid, WMV VC-1, and VC-1 adaptive resolution Smooth Streaming. Hoping to kick off a VP9 set today, but it's been surprisingly hard to get good detailed parameter tuning documentation for libvpx.

I really hope libaom will get something as good as x265.readthedocs.io! That's really the gold standard of encoder documentation to date.

[TD-Linux]

"The most important part of the change is that Google has separated the patent license from the copyright license. Now the copyright license on the software is a totally standard three-clause BSD license, which is clearly compatible with the GPL. The patent license, in turn, provides distributors with permission to exercise all the rights, and meet all the conditions, in the GPL, as required by GPLv2 section 7; and those permissions are consistent with the ones provided by the patent grant in GPLv3 section 11. All this means that developers distributing GPL-covered software can take advantage of the patent license without running afoul of the GPL's conditions, whether they're using GPLv2 or GPLv3."

Does it still apply to AV1?

Yes, it does.

[Blue_MiSfit]

All the improvements in dav1d is fabulous. Up to 50fps for 8 bit 1080p with 4 threads AND NO ASM YET is pretty amazing.

[Mr_Khyron]

http://www.jbkempf.com/blog/post/2018/Introducing-dav1d

[LigH]

And wiiaboo + schmidthubert made ffmpeg build again. So build your favourite kind of ffmpeg with dav1d. — Sorry, too early, API may have changed, some exports are not found suddenly.



@benwaggoner: PM?

[Adonisds]

I just did some performance testing with the 1080p 30fps AV1 encode of the Gus Kenworthy & Tom Wallisch X Games Slopestyle GoPro Preview (https://www.youtube.com/watch?v=_fAOe8oz8qM) video in MPC-HC v1.8.1 x64 with its built-in LAVfilters; I originally tried the Halo video but I found the X Games video to be much more demanding (but also much more motion-sick inducing, especially when playing at slower than real-time).

With my 4c/8t Nehalem Xeon x3470 I was only seeing ~25% CPU utilization at maximum even though I was unable to play back the video in real-time (it was somewhere between 16fps and 20fps). Mathematically that should mean that it's only using 2 threads, but disabling SMT and setting my BIOS to only enable 2 cores resulted in noticably worse performance, yet setting the BIOS to enable 3 cores without SMT resulted in the same 16-20fps performance I was originally seeing yet at only ~67% CPU utilization.

At least with the LAVfilters bundled with MPC-HC v1.8.1 x64, it would seem that the AV1 decoder can only utilize 3 cores and no SMT, yet even then the 2 less loaded cores are only hitting around half of their according core's available utilization.


And for reference, the 720p 30fps AV1 encode of that same video played back without a hitch on my Xeon - heck it left enough headroom that I could turn on a bunch of motion interpolation which greatly helped alleviate the motion sickness I got from watching the 1080p AV1 encode playback at sub-20fps frame rates (it's times like this that I thank the devs over at Nintendo for making F-Zero X and F-Zero GX native 60fps games).



Now I'm a bit out-of-the-loop, but I couldn't help but notice that YouTube-DL was using the .MP4 extension for AV1 downloads - is that in fact correct behavior? (and no, I don't mean AVC1, otherwise my PC would have been playing back the videos easy-peasy).

How do you turn on motion interpolation?

[Mr_Khyron]

https://itpeernetwork.intel.com/open-source-visual-cloud/
Next Gen CODECs

Streaming media is the foundation for visual cloud workloads. Our open source projects will also advance the next generation of CODECs, specifically Scalable Video Technology (SVT) for HEVC and AV1.

Additionally, Intel is contributing to the SVT-HEVC Encoder core to enable high performance, quality, and scalability of HEVC video encoding under a highly permissive BSD and patent license. This HEVC-compliant encoder library core achieves excellent density-quality tradeoffs and is highly optimized for Intel® Xeon® Scalable and Intel® Xeon® D processors.

We are also forming a new SVT-AV1 open source encoder project as an enhancement to the Alliance for Open Media (AOM) to provide a cleaner, easier to use codebase. Community support is critical to open source innovation, and Intel welcomes contributions to the SVT-AV1 project. Register for email updates at 01.org.

As video consumption and generation continues to grow, so will the number of industries that must deliver high-bandwidth, low-latency video at scale. Open source software is fundamental to meeting the demands, and Intel is committed to collaborating with industry leaders to grow the community.