ahhh... the future of efficiency
AV1
Other urls found in this thread:
github.com
cepro.com
twitter.com
>0.1 fps
Holy shit that is a massive improvement. Maybe we'll get to 1 fps in 2020.
Before shitposting further, please provide the following information
>what resolution
>what settings
>what libaom version (roughly)
Thanks.
libaom is slow shit. We're at the point where people are writing alternative implementations that are actually optimised.
github.com
AV1 is for loser virgins. Professionals use HEVC
You mean Intel
>720p
>absolute standard -crf 30 -b:v 0 -strict experimental
>ffmpeg newest, libaom 1.0.0-1297-g52ea88fd1
I'll wait for Intel's libva support and newer hardware encoding before I decide whether I will use it or not. As it stands now it isn't useful for an end user.
>.ivf output
no thanks
shiieeeett
cepro.com
Hey clown, long time no see.
Thanks. So unless ffmpeg changed their defaults you ran it with -cpu-used 1 and on a single thread.
Also I forget to ask: Which CPU?
rav1e is significally faster last time I tried it, my laptop with ulv quad core took like 8 hours to compress a 20 minute 720p video, it's still very slow but with a threadripper or something compressing should be reasonably feasible
But have they caught up quality-wise?
side by side comparison files looked exactly the same but that's subjective, idk if there's a way to objectively measure it using some tool I only tried it because I was bored one day
They must have, because all cores choked
6700K overclokced to 4.7GHz
>github.com
looks like it's just for scaling, retard
>side by side comparison files looked exactly the same
Last I used it (end of November) results looked slightly worse when using roughly the same encoding speed for both aomenc and rav1e.
>idk if there's a way to objectively measure it
You could use VMAF.
Of course pissphone is libanvs user
>VMAF
is there an easy way to use that from windows? from what I can see i'd have to recompile ffmpeg specifically to include libvmaf and I can't be arsed to install compilers and shit for that one thing
You either have to compile ffmpeg with VMAF, compile VMAF directly and use ffmpeg2vmaf or wait for Windows builds to include VMAF. I don't know of any other option.
Easier option is probably to just make comparison shots and post them.
>libaom
>AV1
>HEVC
What's wrong with MPEG-4? nearly all devices have HW acceleration, file size isn't an issue anymore.
>file size isn't an issue anymore.
AV1 AVI
Think about it.
Are you the same person in every AV1 thread?
Given that AVI has basically disappeared already, I don't expect to see too much confusion.
I lost my virginity to avi.
Thanks for always being based and upsetting the plebbitor newfriends trying too hard to fit in
>agreeing with tripfags
you are the redditor here faggot
>(((av1)))
>(((rav1e)))
>(((dav1d)))
>(((intelav1)))
they are not even trying anymore
This. HEVC hardware decoding is adopted in every modern SoC/CPU. AV1 is a dumpster fire nobody going to touch with a ten foot stick before you can decode it on a sandy bridge celeron.
AVI is a container, smoothbrain.
you need gpu acceleration
Nah, fuck AV1 altogether
>expecting hardware when it hasn't been a year since the bitstream froze
meanwhile, using HEVC is essentially walking on eggshells because of patent fuckery
Doesn’t mean shit if you pirate.
What do you think the providers use to encode? If the software theu use can't release a full-featured hevc encoder then it's as good as dead in the pirating world
>what is x265
A collection of compromises
I've tried Intel's SVT-AV1 encoder. It's is the absolute fastest AV1 encoder thus far but the RAM requirements are insane. Encoding 720p eats 11 GB RAM. Yes, really. You're supposed to be able to do 1080p with 16 GB RAM but that's clearly only if you're not running anything else, no X, no nothing, just Intel's encoder. Consider if you're Adobe or someone like that and you'd like to have a VP9 encoder as part of your video editing software which is itself easily using 30-50 GB RAM when editing 4k. Adding another 50 GB as a requirement ain't something you'd like to do.
Hm. I'm doing something wrong and I don't know what. Can't get it to use more than 4GB RAM for 720p footage. What settings do you use for encoding?
>0.1 fps
Waaaaaa so this is the power of... AV1
When Intelav1v?
can someone explain why everyone is so sure that AV1 will ever get fast enough?
what if their algorithm is just computionally worse than the competition?
b-but muh 50% size reduction
I hope he is. I love dedicated people.
>what if their algorithm is just computionally worse than the competition?
Oh, it is. Every new video codec is more complex than the prior generation. VVC and AV2 will be even worse than AV1.
However codec development is a slow and complex process. It's not as black and white as many Jow Forumsentoomen want you to believe. Reference encoders in general are a bad way to judge a standard. They have a lot of unnecessary shit included to allow for testing and experiments and are usually not tailored towards end users. That's why people stop using them at some point in favor of more optimized encoders. And even when you look at those optimized encoders there will be grave differences. Just look up HEVC encoder performances if you don't believe me.
It's a reference encoder. They're all like that.
>can someone explain why everyone is so sure that AV1 will ever get fast enough?
That depends on what you mean by "fast enough". The point most people are making is just that it will get a lot faster.
x265 got fast yet?
How do I watch AV1 on Linux, tho? Chromium works, but it's embarrassing to use it as a video player. I use SMPlayer+mpv, test video has SMPlayer dropping frames hard.
Use dav1d instead of libaom.
ffmpeg -i input.ivf -c:v copy output.mkv