I don't get it. Why actively add VP9 the moment something better arrives?
This is only 6MB and full HD (cropped 1080p)
Try doing that with VP9
AV1
I don't get it. Why actively add VP9 the moment something better arrives?
This is only 6MB and full HD (cropped 1080p)
Try doing that with VP9
why did you use such a weird example
it's specifically constructed to compress well as a webm and poorly as av1, in order to gaslight IQfy
Because frick you, I like it.
moscow people
What
i'll play devils advocate
The reason why is there was a large outcry for VP9, there isn't a large outcry for AV1. This isn't a video sharing website, so there isn't a need to stay on the most current codecs just because
>so few keyframes that seeking doesn't work at all
kek
>Why actively add VP9 the moment something better arrives?
1. vp9 hardware decoding is everywhere, and is very light to decode in software compared to av1, most 4chins users are running shitty Thinkpads from 2005
2. vp9 is WAAAY better than vp8, it was like going from h263 (not 4) to h265, a huge leap that was required because vp8 is dogshit, switching from vp9 to av1 isn't nearly as big of a deal
3. this isn't a video sharing platform, most webms one would want to share are <1 minute medium quality vids, not 5 minutes of 1080p content like you are showing off here, vp9 is already enough for that, vp8 wasn't
and i'm saying this as a huge av1 gay, I think it's more than fair if hiroshima waits another 4-5 years to add support for it
they should remove support for vp8/vorbis webms first, most people still encode with that slop using shitty online converters
>and is very light to decode in software compared to av1
No it's not. libdav1d is a thing.
>doesn't show any data proving that dav1d uses less power than libvpx decoding
you are moronic
also, libdav1d still isn't a thing on android (you only get google's shitty libgav1 decoder) and iOS has literally 0 software decoding capabilities, you can only play av1 on iphone 15 and later
>inb4 frick phone gays
yeah sure
but no phone gays means less traffic and less traffic means less ads viewed which means less money, which means hiroshima would shut 4chins down and you don't want that to happen, right?
Why doesn't SVT on Arch support AVX512?
hi pixDAIZ
You're gullible if you think the tripgay would actually try encoding first-hand He would quickly realize that it only adds 10% performance on Zen 4.
Genuine question though. I'm used to Windows with binaries that do support 512.
Why doesn't it support >10 bit or 4:4:4 chroma?
>>10 bit
Meme
>4:4:4
Good question. It's just luma times three, no?
Dont worry anon, the 4chinz team is hard at work trying to implement av1. Expect a swift release by around 2030
Hardware acceleration hasn't made it to the poorgay phones yet. Realistically speaking the kind of people visiting IQfy aren't going to be strapped. Hell most are still probably using 10 year old thinkpads.
The good news is that there's been a lot of work toward faster and faster software decode performance so we might not have to wait until 80% of computers have AV1 hardware decoding.
i already tried a while back and my 2016 phone can play 1080p24 av1 video in software
while generally software decoding is worse for battery life, it really shouldn't matter for a some short clips on IQfy
yuv420p8 av1 software decoders are really well optimized and it's the main ones that would be implemented in hardware
10bit or yuv444 decode way slower, but not all hardware decoders handle the former and few at all do the latter
from what i've seen 10bit av1 is the standard, i haven't seen a hardware decoder that doesn't do 10bit
it was common with h.265 as well, it was only h.264 where 10bit support was rare since i don't think that was ever really used outside of piracy
yeah, 10bit yuv420 is likely where hardware decoders will have the most impact
but av1 software decoders are good enough on yuv420p8 that you can use them even on mobile devices
10-bit AV1 is base profile.