Anyone else think it's weird they are pushing to release this so early? I mean, H.264 came out a decade after MPEG2, H.265 was out in 2013, a decade after H.264. Now H.266 suddenly appears a month ago only 7 years after the failed mess?
H.264 was way better than MPEG2, H.265 isn't much better than its predecessor, certainly not for the much higher resources it takes. Adoption has been a failure, everybody flocked to alternatives due to the strict licensing issues and the best alternative (AV1) not only isn't any better from the quick test I did but takes WAY LONGER to encode than H.265.
H.266 threatens to be far worse in terms of complexity. CPU frequency has not increased for 16 years now, so we can forget about Moore's law saving the day.
Why in holy hell are they pushing for this standard? We aren't ready for it.
+ Reply to Thread
Results 1 to 18 of 18
-
-
H266 is still not fully finalized yet as standard so relax. Besides, You do realize that creating optimized encoder will take another 5 years?
-
-
The standard is finalized, encoders are to follow. H.265 was finalized in April 2013 and the x265 implementation reached version 1.0 a year later, quality not increasing since then despite the new features. This means in summer 2021 we'll have a stable H.266 implementation if the same pattern follows.
It is also doomed to repeat the same licensing problems and will go nowhere but the alternatives aren't going anywhere either.
Why doesn't MPEG get their shit together before prematurely pushing another standard? -
I was being a bit facetious regarding h265 being finalised hence brackets hardware. Is it going out on a limb to say hardware has not kept up with it nor ever will? I'm sticking with h264. I think your post highlights a lot of frustrations people still feel with hevc. You'll probably get some 'comeback' from advocates of it.
-
-
Seeing that vpu encoder chips support for newer formats get better and better I'm wondering what will happen on that front with H.266,...
But I agree, it'll probably not before 2025 that we will have mature encoders for H.266.users currently on my ignore list: deadrats, Stears555, marcorocchini -
I disagree, I have been doing tests and have not seen quality improve with x265 at all since version 1.0. Now, it was with 480p videos but I don't see why that would utterly negate an increase in quality.
Other than with anime, no H265 implementation I've seen has surpassed x264 more than marginally. It has been a disappointment. -
-
Your statement is laughable, x264 is not in the same league as x265 and I wouldn't expect it to be. The only thing that "hurts" x265 is that it's pretty slow relative to x264, but if the x265 teams would actually keep the promise they made years ago to incorporate GPU acceleration the same way the Main Concept people have done with their HEVC encoder, then, for the time being, x265 would be untouchable.
-
-
-
-
-
This statement is so confusing, it's hard to know where to begin. I don't know where you got the impression that someone wants or needs you to kill members of the genus Rattus, but I'll do a quick test encode for you.
https://www.blackmagicdesign.com/products/blackmagicpocketcinemacamera/workflow
Source: 16:24GB Wedding video, 1034Mb/s, 6144*3456 (16:9), 24fps, cropped and resized via Handbrake to 4096x1712 (2.40:1, Mod16)
I cheated in favor of x264, 2 pass, preset slow, tune film, 5Mb/s; x265 I used 1 pass, preset very fast, tune grain, 5Mb/s, I through in a quick nvenc hevc encode, just for shits and giggles.
Note, I would never, ever use only 5Mb/s for 4k, not with AVC, not with HEVC, maybe with AV1, because I have seen some crazy good encodes with SVT-AV1 with the slower presets (6 and lower).
Also note, that the x265 encode used less bit rate than the x264 one, and the nvenc encode used less still, and nvenc was not a Turing encode and it still managed to be pretty close to x264.
So... -
Just to really drive home the point, I did 3 more encodes, with the ToS 13GB JPEG2000 source, I exported it as a x264 CRF 0 lossless and used that as source, I did this because I wanted to minimize the decoding bottleneck associated with JPEG2000, due the desire to report encoding speed this time.
Like the last encode, I cheated in favor of x264, 2 pass, preset slow, tune film, 5Mb/s, x265 was 1 pass,preset very fast, tune grain and I threw in an nvenc hevc encode as well. The source was a 4096x1714, which I cropped by 2 pixels from the top to make it 4096x1712 (MOD16).
Again, this is way less bit rate than I would ever use for a 4k encode.
As for encode times, x264 took 26min28sec, x265 took 46 minutes and nvenc took 6min18sec; this is for a 12min14sec source.
I don't think anyone with even a modicum of intellectual honesty will say that x264 won either of these 2 test encode contests. -
And this is all related to H.266, how?
And this should be in this thread, why?
At least I don't even care any more to look at such comparisons here any more unless they are in their dedicated own threads.
-> time to abandon another thread,...users currently on my ignore list: deadrats, Stears555, marcorocchini -
A good quality video file if it results from h.266 will be nice for those of use who don't have super fast internet speeds. I do nearly all my encodes with h.264 because it takes up less time and not every device accepts h.265
Similar Threads
-
fraunhofer now ready to "sell" h266 as 50% smaller than h265 nearly same q.
By aedipuss in forum Latest Video NewsReplies: 4Last Post: 8th Jul 2020, 09:52