taaz ( @taaz@biglemmowski.win ) English26•2 months agoFinally
cron ( @cron@feddit.org ) 20•2 months agoVA-API is Video Acceleration API
LaggyKar ( @LaggyKar@programming.dev ) 5•2 months agoYes, it says so in the first paragraph
cron ( @cron@feddit.org ) 6•2 months agoTrue. But at least for me, VA-API was not a known abbreviation, that’s why I copied the long form here.
Swedneck ( @Swedneck@discuss.tchncs.de ) 6•2 months agoonly like… a fucking decade late or something? jesus
kevincox ( @kevincox@lemmy.ml ) 19•2 months agoThis was intentional. The goal was to discourage the adoption of non-free codecs. They were partially successful, now AV1 is very widely supported (basically only older iThings that don’t have hardware decoding support don’t support it) which is a huge win because anyone can now deliver video on the web without needing a license to a proprietary codec. I would consider this fact alone a huge benefit and worth them holding other browsers asses to the flame.
Scoopta ( @Scoopta@programming.dev ) 3•2 months agoI definitely think this was a good move. Proprietary video codecs are silly and I’m glad VP9 and AV1 have been so widely adopted. I do wish more services used them instead of h.264 but at least it’s something.
Generous1146 ( @Generous1146@beehaw.org ) 5•2 months agoHell yeah, can’t wait to transcode all my movies again 🥲
Zetta ( @Zetta@mander.xyz ) 12•2 months agoWhy, use an open source standard. AV1 for the win
jagged_circle ( @jagged_circle@feddit.nl ) English4•2 months agoWhy do I want h265. Didnt the copyright on h264 finally run out, so now I can use it without a license finally?
I’m not going to be using h265
Illecors ( @Illecors@lemmy.cafe ) English4•2 months agoIt’s much more efficient space wise.
jagged_circle ( @jagged_circle@feddit.nl ) English1•2 months agoH264 is much more efficient space wise than webm. So I’ll use h264 because I finally can legally
thingsiplay ( @thingsiplay@beehaw.org ) 4•2 months agoFirefox indeed.