>He doesn't use H266 video encoding
>>107088618use case?
I remember this being finalized in like 2020 and I still haven't seen a single torrent using it.
Wait a few years until its properly implemented on hardware, wonder if there is demo videos out there
>>107088618My GPU doesn't support it and CPU encoding is probably slower than molasses right now like AV1 encoding used to be.
will be deprecated and superseded before any kind of real world adoption just like it's predecessor
Wasn't the "x266" name taken by a troll company?
It just works
>>107088618i can't keep up with these gazillion of standards that all do the same shit
>>107088651Fortunately the German company that made the reference encoder and decoder is not subject to the Frankfurt court which is the only court in the entire world that's ever humored patent trolls.
AOM is already black magic though
>>107088618>status: in forcewtf does that mean
>>107088618Not supported natively in chrome or firefox. So please stop encoding your video torrents with this shit.
>>107088658>bloated filesize
>>107088783post nose
>>107088675THISLike what's even the point of VVC other than being a straight up digital racketeering? SVT-AV1 is now officially faster/better than x264 and encoding VVC takes a gorrillioon lightyears.https://desuarchive.org/g/thread/106327782
>>107088822>digital racketeeringDigital EXTORTION racketeering*
>>107088618every video I've encoded using vvenc has incredible quality/size ratio, however i always have a timestamp issue when playing them. why? issue from the decoders/players (ffmpeg)? the encoding( i use the basic options)?
>>107088618Is it patent encumbered?
4K res AV1 can be decoded above 60 frames per second even on 10 year old laptop CPUs. Can VVC do the same? If not this thing is guaranteed to be DOA no matter how much they reduce royalty fees.https://openbenchmarking.org/test/pts/dav1d
>>107088629rip UHDB
do the numbers mean anything or is just a shit naming scheme they'll keep using until 269?
>>107088930Are you new to the MPEG consortium? It's always patent encumbered. Tons of companies make money just on licensing different aspects.It's gotten so bad that Google, Netflix, etc had to get together and create competing open standards (AV1 which beats H265) and in the future AV2 (improved AV1 for 8k+ and higher resolutions).
>>107088618they all suck.as soon as there is a dark scene and you dont use an insane crf value, you get blocky artifact shit. with every encoderor you play around with retarded psycho quantization shit for hours/days
DOAEven HEVC was failing until Apple bailed it out of irrelevance.
>>107088618they should rename themselves to the Joint Encoding Experts Team
>>107088930it's not, don't listen to what the google shills tell you. patents only matter when you're designing your own media codec. otherwise what matters is the licensing. aom and mpreg both are "encumbered" by patents, both have licensing conditions. the newest mpeg formats put no limits on encoders and end users and anything not on the hardware side of things, and even then it's basically zero limits there too. aom's terms are that everyone must cede all their patent rights in the past present and future to aom ie. google if they make (and/or deploy?) an en/decoder. it's sorta like blackmail to anyone who needs to support the youtube (and incidentally contrarians on nyaa too) usecase for their lusers. it's basically copyleft, but instead of everyone reaping the rewards of freedom only google does giving them a unique competitive edge.
>>107092599AFAIK AV1s terms are actually more like this: If you patent troll us, we'll revoke your license.Stopping mpeg-la kikes from repeating the VP8 patent trolling farce that got them kicked out of the webm project is bad because?
>>107092599Also isn't the x266 encoder project stillborn because the mpeg-la kikes are demanding blood money in royalty payments?
>>107092703they don't discriminate against patent trolling. to google any attempt to negotiate blatant patent violations is considered "trolling." this is pilpul.they got "kicked out" of webm the same way jxl was from chrome, kike.>>107092728that's total fud. vvc is as "stillborn" as av1 is, despite being railroaded into youtube where the cattle don't know what they've lost (and the fact that vvc actually competes with av2)
>>107093215How is AV1 "stillborn" when its now literally faster to encode than x264?See >>107088822Like if AV1 was a nothingburger then it would have never been this heavily optimized to the point where it's making x264 obsolete.
>>107093215>they got "kicked out" of webm the same way jxl was from chrome, kike.JXL patent trolled Google? Very interesting, can you elaborate? I thought it was just because Microsoft won some JXL patent and now JXL is in danger of requiring royalty payments to Microsoft.
>>107093282the rust effect. more people building the ecosystem for it than anyone leveraging the ecosystem.as another example, the use of av1 in weeaboo discord tranny circles is more politics than actual viewer demand.>>107093304>patent trolling out of nowhereyou know exactly why they were both "kicked out". this is pilpul
>>107088618>video encodingHonest stupid question: with the hardware advances, can't we just literally do something like full 24-bit depth 8K res bitmaps, 60 of them each second, and similarly with audio wave files, everyhing fully uncompressed? Can't modern advances in hardware just handle that with no need for muh compression?
>>107093340You're claiming that JXL patent trolled Google because that's LITERALLY what mpeg-la kikes did with VP8. They "cried out in pain" while they struct google at the same time about infringing patents on VP8 which the DOJ found was 100% horse shit.Shit man, I wanna know about the JXL patent trolling google because that's infinitely more amusing than Microsoft charging royalty fees for JXL usage.
>>107093395I did not. keep up the pilpul and I will respond in kind
>>107093368No because of RAM constraints. IN THEORY your idea works with 64GB of RAM not 4GB of RAM on like 50% of consumer phones.Which is incredibly retarded, the bare minimum in 2025 should be 8GB of RAM but idk, goyim shit stuff I guess.
>>107093418Then what the fuck are you saying then you fucking retard? Are you a bot?sugirir h
>>107093430mp4's inclusion in webm is not at all related to vp8's possible infringement. google only made it so because they're a company of crybabies>doj defending the cia projectyeah I wonder why they'd be so quick to fend for google like with the eu digital markets act and antitrust lawsuit, lol. their verdict means nothing on the moral situation at hand
>>107093419But buffering?Also, if those are the numbers for 8K, then it should probably work with 1080p, then. Older shows shouldn't need any compression.
>>107088618>not using superior XvidNvgmi
>>107093479Crybaby? Care to elaborate because this is what I understand and the ones shitting and pissing their pants seems to be mpeg-la, not google. Like I get hating google as /g/ board culture but in this one instance they were extremely based.>2010s>Google: buys On2 and releases VP8 as royalty-free>"finally, a codec not chained to a bunch of rent-seeking boomers">MPEG-LA: seethes uncontrollably>"anyone got some dusty IP we can mash together to claim VP8 infringes?">DOJ: notices the smell of anti-competitive garbage>"are you forming a patent pool to kill a royalty-free competitor?">MPEG-LA: sweating bullets>"N-n-nooo officer, we’re just protecting innovation!">Google: keeps shipping VP8 and WebM anyway because they smell blood in the water>DOJ: raises eyebros after a few years of back and forth litigations"So do you actually have ANY proof that VP8 is patent infringing?">MPEG-LA: on the verge getting fined billions and billions and billions>"nah... we'll be good now.">*repeats the same fucking kike shit with HEVC*>*adds a per stream royalty fee pissing off every single streaming website on earth*>"WTF why is only like 10% of the web using HEVC!???"
>>107093595Fuck right off, sick cunt.
>>107090221>make competing standards>industries that went all in on mpeg consortium keep using their codecs>only time anyone sees anything about AV1 or AV2 is the resident schizophrenic that shitposts on this boardpretty depressing
>>107093595not interested in being on your watch list, fbi.
I'm still waiting for h265 support
>>107093815Netflix literally abandoned hevc in favor of AV1. It's ogre for mpeg-la.https://www.tvtechnology.com/news/netflix-rolls-out-av1-film-grain-synthesis-streams-for-film-content
>>107093831Bro, 4chan would literally need to pay for every fucking video file uploaded here that would use HEVC.HEVC patents expire in like 2030 and 4chan would need another decade to update anything. And that's ASSUMING that disney doesn't buy 4chan.
>>107093865HEVC has multiple versions and some patents will last until ~2035-40Most if not all AVC (264) will be free from restrictions by 2030.
>>107093993Man, it boggles the mind that shit like this is legal. Our modern day extortion rackets are happening right now... on the fucking internet.
>>107094025>genius is surprised by how patents workit's like you faggots think that all people are inventing things out of the goodness of their hearts and profit motive just doesn't exist. of course it's legal, that's the entire premise of having patents. your creation is protected and faggots will need to cough up money to license it. it's not a perfect system and is abused constantly but it's better than nothing.
>>107094109Yeah but 10-20 years for royalties is very reasonable so we can make better things. Like even VP9 will encode worse than H264 if you don't know sekrit parameters meant to legally skirt around H264 patents.
>>107094025H.262 expired some time ago and H.264 expired in most of the world afaik. That would explain the anti264 astroturf I've seen for some time.
>>107094230OR maybe...Just maybe, H264 is a smoldering turd of a video codec? Just a guess.>"at least it's not xvid!"
>>107094291>pushing meme codec>libx264 restricted to +3 mbits >lets forget about the +10 times higher CC>lets forget about the lost frames problem during decodingLmao even.
>>107094671>"NOOOOOOO DON'T H264 AT BITRATES THAT SAVE PEOPLE MONEY">"ANYTHING BUT THAT!"
>>107094671>>lets forget about the +10 times higher CC????See >>107088822
It's funny to think some retards will seethe for something as stupid as people using x264.Lmao.VideoLAN will live rent free in their minds for decades.
>>107093837>Netflix literally abandoned hevc in favor of AV1. It's ogre for mpeg-la.Apple joining AOM sealed the deal. People don't remember why h264 skyrocketed in popularity. It's because Apple adopted it
>>107094291Not him but I personally dislike x265 artifactingx264 is still honest, if the bitrate is too low it looks blocky and you know you need to bump it upx265 is... weird, like it just kinda melts shit together like some kind of ai generated crap. Meaning you can look at an encoding and not see any artifacts but if you pull the original next to it you notice that some spots are... changed. That's a lot worse than a bit of blurriness imo
>>107088618Why would you use something that is worse quality per byte and likely going to eat gbs of space?
>>107095266x265 was great when it came out because the filesizes were tiny.Not nowadays. Don't know how that happened.
How's hardware support? Unless I can transcode it on the fly I don't really care.
>>107095266AV1 actually fixed this with synthetic grain, see >>107093837The problem is compressing video with 1 gorrillion motion vectors from analogue noise from old film reals is hella hard.
>>107094291>2023This is pretty old data at this point.Come on guys, stop posting bs and post some fokken GRAPHS!
Mogged by AV2.
>>107098765Honestly it's getting mortally wounded by PSY AV1 forks already and some of their improvements are headed toward the mainline SVT branch. AV2 is just a mercy killing at this point.
>>107093706why'd you post that image? what the fuck led your thoughts to that?did not bother reading your whole ass fan fiction on daddy google's misadventures either. the webpiss jeets were mad as jxl the same way the webmid poos were at mp4, end of story. zoomers are just too dumb to see how garbage and cancerous vp8 was for its time and the drama everyone had to endure as google rammed their garbage codec through the internet.
>>107099297The image represents mpeg-la trying to NTR Google. Obviously it didn't work and the whole world is laughing at them.Did I strike a nerve mr mpeg-la representative? Gonna cry? Piss your pants maybe? Maybe shit and cum?
>>107088618Can we just stop with all this bullshit? XviD and DivX were fine but then everyone settled on H/X.264. Video compression has been handled. It's a solved issue. Lets instead focus on fitting more 1's and 0's in a tighter space for more storage capacity.
>>107099358Even if you don't give a shit about Anime, where AV1 is like 90% more efficient than H264, it introduced synthetic grain which solved the problem of trying to compress movies with lots of grain that normally required 100 Mbps with H264. See >>107093837Like it's kinda nuts that people aren't making a bigger deal out of this. You no longer need 100Mbps to preserve grain anymore.
>>107099342I did not read the image at all. I'm sorry if you expected me to.av1 is losing hard lol. you troons act like rust shills but have not achieved even 0.1% of success the rustfags found with the strategy. outside of contrarian rippers and youtube sheepishly adding av1 as a possible format (and rarely ever using it) where the fuck is it even good for?your only propaganda angle is software transcoder efficiency lol, as if anyone even cares. it's just a stepping stone. the only possible argument to be made with it is that good transcoders lead to good adoption. that adoption never materialized. the codec is so shit absolutely nobody was waiting for its transcoder to get good. the end goal is always adoption. if some argument does not lead to adoption it is a moot point.av1 now has the same widespread hardware support as hevc and it's still a huge nothingburger. vp8 vp9 av1 and soon av2 are all a waste of hardware transcoding silicon all because google mandated it as such. if anyone's getting cucked, cuckbrain, it's nvidia et al.
>>107099374Lol u mad, mpeg-la stooge
>>107099358>Lets instead focus on fitting more 1's and 0's in a tighter space for more storage capacity.But isn't that what developing newer more optimal/currently feasible codecs already is
>>107099378who the fuck even cares about the mpeg org? dumbass faggot. the only possible positions to be held online is pro-google and anti-google. the only entity people give a shit about is google. not a single soul online gives a single fuck about mpeg the organization. we both only care about what google does, and how google reacts.
>>107099358x264 (the open source codec) is the sweetest point for a general codec and it fails gracefully (personal opinion). It's slower than h262 (mpeg 2) and 263/xvid but the extra computing is proportional to the space saving, x265 and newer are like 10 times slower to save ~30-40% but not in generalIf MPEG 2 still is usable for some things then h264 will be usable for a long time.
>>107099385No it's a waste of time that only serves to fill the landfills with more e-waste the minute AV-238 comes out and your TV/set top box can no longer decode the video efficiently.
>>107099373>Like it's kinda nuts that people aren't making a bigger deal out of this. You no longer need 100Mbps to preserve grain anymore.It is a big deal and it is impressive but also I'd imagine more people would care if more people still used film.
>>107099374Please cry harder, your tears are delicious.https://www.advanced-television.com/2025/09/25/vodafone-meta-google-push-av1-video-codec/
>>107099395Is MPEG 2 still being used? I feel like the last time I saw it being implemented was for OTA broadcasts.>x264 (the open source codec) is the sweetest point for a general codec Agreed
>>107099404even rust no longer has to shill the promise of adoption. av1 fanatics left on perpetual edging kek
>>107099415Yes, mostly for digital tv/.ts and some camera drones, kinda a niche compared to h264
