How the fuck is it still so fucking bad. x264 is literally 10 times faster to look the same. Fucking hate how I'm forced to use this slow piece of shit for HDR.
>>107055924>Another retard blaming H.265 for the shit show that is x265
>>107055924HDR works with h264 retard
>>107055924H.264 looks significantly worse then HEVC, AV1, or VVC. Get out of the stone age.
>>107055924The efficiency is the file size... It's waaaay slower because it's compressing the file way more.
>>107056053No it's not, x265 filesizes balloon to file sizes bigger than the source while x264 is half at lossless quality
>>107055924it doesn't look the sameit compresses betteryes, it takes 10 to 100 times longer to encode and is needs more power to decode
saar are we confusing encoders and codecs again? i haven't used x265 for a while but what always annoyed me about it were the questionable defaults
>solves video codecs
>>107057091at least with hevc you can still make good looking videos at the expense of file size. av1 is just shit all around
>HDR
>>107056737It doesn't seem to. You mean using the lossless flag? There's a lot of nuance to this but I think both work quite differently if you use software vs hardware and the lossless flag is something that I might be getting confused over as that might be a Handbrake flag... But just standard settings, everything auto, you should find it's quite a bit better.
>>107057152this
>>107055924It depends on resolution. The primary benefit modern video codecs is bigger macroblocks.H264 = 16x16 maxH265 = 64x64 maxThis is very important because the less "chunks" a video uses the better it compresses.1080p video = 8100 16x161080p video = ~506 64x64>>107057140AV1 has now achieved 2 things:Better compression than x264 slowFaster encode speed than x264 slowAlso it achieves them at the exact same time which is batshit crazy when you think about it because all it really had to do was encode faster than x265. https://desuarchive.org/g/thread/106327782Anyway at least at 1080p and above, I think we can all agree that AV1 has made H264 and HEVC OBSOLETE.
>>107055924Cause 265 is strictly for 4K video. Try a x264 at 4K it would be even slower than the x265. That's why x264 is still used cause it's better for small resolutions.
>>107058232Nah, going from 8 thousands + fucking macroblocks to only around 500 still makes an enormous difference at 1080p already.
>>107058263500 blocks in a tiny resolution looks like shit lmao
>>107058083AV1 has really poor compatability on non-computers. I don't think my G3 can play it native, but I might be mistaken. It definitely transcodes VP9 which sucks.
>>107058269????Anyway there's just no way you're going to achieve good compression efficiency with 8k + macroblocks. At that point finding redundancies becomes impractically difficult.>>107058308LoL but yeah the only real requirement AV1 has is a CPU with AVX2. That's really it so 2500Kfags will seethe uncontrollably at AV1 but Haswellchads stay based.
>>107058323>LoL but yeah the only real requirement AV1 has is a CPU with AVX2. That's really it so 2500Kfags will seethe uncontrollably at AV1 but Haswellchads stay based.not anymore, dav1d added acceleration for CPUs with SSSE3
>>107058323>Haswellchads stay basedI thought my setup was way too old to do anything modern but I'm surprise its holding up pretty well, dunno how much longer I can continue to use my i7-5930k but I'll likely upgrade to a threadripper setup when I'm ready to build a new pc.
>>107058934>threadripperZen 6 will have 24 or 32 cores on desktop Ryzens because 12-16 core CCDs have been confirmed.
h.265 has the problem of diminishing returns and x.265 didn't gain the same momentum and contributors as x.264 pre 2010, there're real alternatives than coding for a project semi-illegal.
>>107055924isnt h265 some hikvision slop meant to reduce outbound packet size (or maybe im thinking of h265+)either way my chink cameras had awful buffering issues on h265 and h265+ but since switching to h264 there hasnt been an issue
