>Chromium already merging the AV2 software decoder (dav2d).>Pretty much everyone has AV1 HW decoders, even crapple.>Thanks to the hand-woven assembly of dav1d even a Pentium 4 can software decode AV1.>YT, Netflix and others will start streaming AV2 next year.>This shit site is still stuck with VP9, even though it is slower to encode and decode.Mods, please fix.
>>110204490Don't care still using h264
>>110204605>h264 on a 4MB size budgetRetard
>>110204490It took nine years for this site to get VP9. Progress seems to run at a snail's pace here.
>>110204966They need to guarantee it would work on iPhone. Hiroshima Nagasaki only uses an iPhone.
>>110205163AV1 works on iPhones since the iPhone 15 Pro (2023), on newer models it does not even require Pro.
>>110205509Yeah, but they need to guarantee it works for nine years is what he probably means. Check back in 2032.(Actually, this site has just forgotten how to do any feature development whatsoever. It took them an entire day just to patch PHP)
>>110205695Could this site just honestly be a government project.Like theres things that would be cheap to implement to improve the experience but they dontThey hardly make money off it, so why would they buy it in the first place. Why havent they sold this site they dont care about at all?
>>110204490YouTube and Netflix will continue to look like shit no matter how good video codecs get because they'll just use it as an excuse to lower bitrates even further.
>>110205838That is beside the point, see >>110204729AV1 use case is literally meant for things like 4chan with its 4MB limit on webms.
>>110204490I have been using it everywhere important, skill issue
>>110207142How? You can't post AV1 on here.
>>110207169He just said "everywhere important"
>>110207412Sir, the 4chin-chin website is most influential
VP9 being the most advanced codec here wouldn't be such an issue if we had limits larger than 4096KB
>>110205509>2023and this is exactly why it isn't supported on 4chan, yettry again in 2030 to 2035
its a miracle we even got vp9 support
>>110205763the dev is a part-timer that only comes around when rape ape wants a new captcha system, or when it's april fools time
>>110205509>>110205163The compatibility argument falls apart when you have a bunch of anons uploading 10-bit VP9 webms which most iOS devices can't decode.
>>110208779>>>110205509I wonder if this 12bit webm will play here
>>110204490>a new codec right as we're finally starting to get av1 supportgoogle's goal is probably to create implementation fatigue just like they did with android so everyone stops bothering with google's bullshit and turn to fpga hardware codecs or whatever. they took forever to accept jxl on grounds that it had no rust decoder btw. but avif runs on the SOFTWARE C++ decoder because all image codecs aren't hw accelerated because these soi coders are too dumb for that (and lazy too for maintainence)
>>110207633it was a bug turned feature. adding new codecs support is literally just the relaxation of file checkers in terms of the magic bytes one detects. if you use ffmpeg you are forced to have support for all formats. the only time this place has willingly added a codec (vp8 was because it's what you had to do to get webm to cut down on massive gifs) was mp4, which made sense because that's an actually good codec.
>>110209868mp4 is not a codec.
>>110209913you knew what I meant retard.
>>110210062No. What codec are you talking about? Learn to express yourself better, nigger.
>>110210086Drop the semantics fuckface
>>110209868mp4 isn't a codec mongo. mp4... with avc, hevc, mpeg-2?
>>110210108the codec that mp4 was first used for and is only ever used for in by sane people.>>110210086why should I when the implication is obvious? you're just mad that I shat all over your lil daiz agenda that you had to fixate on this nonsense topic to divert everyone's attention from the truth. you're even madder that your attempt to discredit me for not using the proper autistic terminology to socially signal my competency to the unmeritocratic autist community that you had to doublepost.
>>110210148Take your meds, schizo.
>>110210151nothing about my post is schizophrenic, buzzword faggot. I called you daiz-like but you might just be daiz, in how you resort to pilpul and diversion tactics every time. in how you snap to the most convenient zinger and drop all prior lines of argument in a blatant showing of zero intellectual integrity.
>>110204490noooooooo if you change the codec again i won't be able to use my 20 year old stinkpad to shitpost anymore.
>>110209440It plays on my PC
>>110209440Not even my Google phone plays it. It's ludicrous that they were ever allowed here.Heck, my old phone could not even play 10-bit VP9, yet AV1 worked just fine.
>>110210178Can you even decode VP9 10-bit?
>>110209868The only and I mean ONLY reason h264 was added was to allow the xitter bots to repost engagement bait directly from xitter
>>110209868>which made sense because that's an actually good codec.except it isn't. we already had webm/vp9/opus, and all of those are better than mp4/h.264/aac which is what was added.it wasn't an improvement, all they did was add support for legacy formats so people didn't need to convert their files as often.there's no reason to use mp4/h.264/aac when converting something, use the newer formats we already had
