x265 - Work already started?

[Warperus]

Thank you, drmpeg.

[JEEB]

Originally Posted by jq963152

By the way: why are so many users here still referring to "HEVC"? It's officialy called "H.265" now, isn't it?

ISO/IEC name is still (MPEG-H) HEVC, H.265 is the ITU-T's name for it, only given to it lately (before that it was marked as ITU-T H.HEVC there).

Just like (MPEG-4) AVC is the ISO/IEC name for what is called H.264 over at the ITU-T.

[Biggiesized]

H.HEVC might have been a working name like H.26L.

[JEEB]

Originally Posted by Biggiesized

H.HEVC might have been a working name like H.26L.

It was indeed. Since numbers are usually only given relatively close to finalization of the specification (although yes, it still isn't finished).

In any case, my point was that both HEVC and H.265 are valid names for the format (I generally will be calling it HEVC because that's how I've been calling it for the past XY months, and the fact that it gained another nickname isn't going to change much of that habit)

[pandy]

Originally Posted by jq963152

Can't wait for x265 then .

https://code.google.com/p/x265/

Originally Posted by jq963152

@ x264 developers:

Can you please stop working on x264 and put all your workforce into x265 (or whatever you wanna call it) from now on ?

What with interlace? And how fast your CPU is clocked? 12GHz?

[aegisofrime]

Originally Posted by pandy

https://code.google.com/p/x265/



What with interlace? And how fast your CPU is clocked? 12GHz?

AFAIK that isn't "real" x265 though. The developer isn't part of the x264 team like Dark Shikari, akupenguin et al. I wonder what will DS et al call their implementation of HEVC now?

[easyfab]

Originally Posted by aegisofrime

AFAIK that isn't "real" x265 though. The developer isn't part of the x264 team like Dark Shikari, akupenguin et al. I wonder what will DS et al call their implementation of HEVC now?

Are you really sure that x264 team will do a HEVC encoder ?

[aegisofrime]

Originally Posted by easyfab

Are you really sure that x264 team will do a HEVC encoder ?

Nope I'm not sure at all. AFAIK DS has not commented on the issue. I'm just saying that the x265 linked is not done by the x264 developers.

[Sagittaire]

anyway the work for x264 is incredible ... perhaps time for other dev to work to x265.

[LigH]

Hype victim.

There are very few people willing to spend a week on a movie just to be a "pioneer" using a bleeding edge technology, not understanding that most consumers and casual users will demand a conversion being faster than playing time.

Give the developers the time they need to really understand the concepts, even before they start implementing half-baked code. A good software project is started in theory, and it is "almost done" (regarding its definition) before the first line of code starts. The less you know where you go, the more often you have to go back because you took a wrong turn.

[Audionut]

Not to mention, afaik, it was over 12months after version 1 of H.264 before the first commit of x264. And x264 was not fast initially.

Have we even got a final draft of HEVC yet?
I guess people these days are less patient.

[LigH]

They never had the joy of manually tweaking DivX 3.11α SBC parameters in Nandub until there were no "shit frames" left...

[pandy]

Originally Posted by jq963152

What do you mean with "What with interlace?"?

H.265 is designed for progressive video - mostly those with higher resolution in mind (4k and 8k)

Originally Posted by jq963152

So you're saying a 12 GHz CPU is needed to decode H.265 ?

Today probably yes especially for 4k content (8 k for sure) - count H.265 as 4 - 16 times more demanding than H.264 for CPU speed.

Originally Posted by jq963152

Also: the sooner the adoption of H.265 starts, the more likely it would be that there would be dedicated hardware to decode H.265. So a CPU might not even be necessary if NVIDIA or AMD for example would develop some VPUs capable of decoding H.265 .

Seriously, just look at those numbers posted by "xooyoozoo":




They sound amazing IMHO. So why not screw H.264 from now on and go for H.265 instead ?

But why - is see no point to go for H.265 for HD - it have sense for Ultra HD however until moderate priced displays for 4k will be not present then i don't see any gain for H.265 over H.264.

[aegisofrime]

Originally Posted by jq963152

So H.265 does not support interlacing?

That would be awesome .

Interlacing is a very evil thing IMHO and should have been abandoned a long time ago.

So, if H.265 drops interlacing support, then this actually is very much appreciated .

They can drop it as long as we get high frame rates.

Recently there's a disturbing trend of some DVDs coming out with 30p content. In this case, I actually prefer 30i as I can deinterlace it with QTGMC to get nice 60p content. With 30p, the best I can do is to double the framerate with Interframe, and the results are not as good as deinterlacing 30i with QTGMC.

[sneaker_ger]

H.265 still supports flagging content as interlaced - it just doesn't have any interlaced tools like PAFF or MBAFF anymore AFAIK.

[Guest]

Guys, debating interlacing versus progressive is off topic here. Further such posts will be deleted.

[IanB]

Split the debate crap off into it's own thread, it's spoiling an interesting thread.

[kidjan]

Originally Posted by paradoxical

And yet, all of this was being said by people when H.264 was ratified. Hardware support took many years to become as ubiquitous as it is. x264 didn't become as mature as it is now until many years after the standard came out. By this logic, we should have just stuck to MPEG-1 video.

Except there wasn't an existing base of billions of phones capable of decoding MPEG-1, and MPEG-1 was obviously a pretty basic standard comparatively speaking. Right now there are literally billions of embedded devices with hardware capability for H.264; it's a completely different situation if you take magnitude and proliferation into account, not to mention the relative maturity of H.264 when compared to something like MPEG-1 (please, no comparison)

[kidjan]

Originally Posted by Soulhunter

My prediction is that HEVC will give us more something like a 25% compression improvement, and probably mainly for high resolution content... Considering how much more cycles it eats, and that high resolution content takes ages to encode to begin with, its use is imo questionable, even more so considering that we don't know if 8k (and higher) will find widespread acceptance by the consumers or if it will go the way of high definition audio for music (SACD, Audio DVD...). As storage and bandwidth is growing I don't see much need for better compression than we have now with x264, at least not at the costs of the need for new encoding/decoder hardware and time (CPU cycles). Just my 2 cents *Back to IDLE mode*

...and that isn't even beginning to broach the whole patent subject. HEVC basically resets the clock on royalties.

Originally Posted by kidjan

Except there wasn't an existing base of billions of phones capable of decoding MPEG-1, and MPEG-1 was obviously a pretty basic standard comparatively speaking. Right now there are literally billions of embedded devices with hardware capability for H.264; it's a completely different situation if you take magnitude and proliferation into account, not to mention the relative maturity of H.264 when compared to something like MPEG-1 (please, no comparison)

There were more than a billion VCRs sold when DVD came out. There were more than a billion DVD players sold when BluRay came out. Did you fight against those things coming out as well? I really don't see how it's a different scenario other than you've just made an arbitrary line. H.264 deserves no special place of being considered irreplaceable versus any other video codec or format.