x266 VVC Encoder

[LigH]

Security via obscurity...

[Balling]

Originally Posted by benwaggoner

At the time (before I was involved in SMPTE) I figured that J2K was used for digital cinema in large part to make it that much harder for pirates to be able to play them on PCs .

There were no such leaks. Only some masters in ProRes.

[Balling]

BTW, funny that you mention it https://docs.nvidia.com/cuda/nvjpeg2000/userguide.html

[benwaggoner]

Originally Posted by Balling

There were no such leaks. Only some masters in ProRes.

Yeah there was sure a lot of belt and suspenders in security for DCI. I'm sure they would have been cracked eventually hadn't much more useful formats like ProRes HQ come out. And which have a lot more threat vectors.

[Dann0245]

https://multicorewareinc.com/news/me...-in-las-vegas/

[nevcairiel]

They have been listing x266 for convention schedules going back 6 months or so (going back to IBC 2021 in November), nevertheless more information has not really been made public in all that time.

[rwill]

Originally Posted by Dann0245

https://multicorewareinc.com/news/me...-in-las-vegas/

I read between the lines and it tells me a lot about the state x266 is in.

[FranceBB]

Ah, so more info and hopefully we're gonna have a date about when it's gonna be officially released.
I look forward to toss VVEnc and integrate x266 'cause so far I've had to work around the VVEnc limitations.

[BuccoBruce]

I'm hoping MCW working on this means VVC won't face as much of an uphill battle with functional rate control or single threaded performance as VP9/AV1 did. Anyone know what their demo at NAB was like?

Originally Posted by lvqcl

AFAIK HEVC decode in Edge Chromium is still broken --

https://techcommunity.microsoft.com/...es/m-p/2077247
https://answers.microsoft.com/en-us/...4-58ec09133984
https://techcommunity.microsoft.com/...ng/m-p/1959752

-- and Microsoft doesn't care much.

That was a side effect of a regression in their HEVC Extension, downgrading it fixed it as soon as the bug was introduced in 2020. I'd know, I still have Microsoft.HEVCVideoExtension_1.0.31823.0_x64__8wekyb3d8bbwe.appx on my NAS for any machines that I forgot to disable Store updates for it on! It does finally work fine now, they did something to either the extension itself or Edge in March (likely both) and finally fixed it, nearly two years later. I wonder if they've actually paid out to HEVC Advance / MPEG LA for all the free HEVC Video Extensions from Device Manufacturer downloads out there.

You used to be able to build Chromium itself using a modified ffmpeg build that could play anything (including HEVC) but the old methods you can find online no longer work.

Originally Posted by benwaggoner

At the time (before I was involved in SMPTE) I figured that J2K was used for digital cinema in large part to make it that much harder for pirates to be able to play them on PCs .

[LigH]

HEVC issues do not belong to this thread... per se. But you are probably right, making a mistake once does not guarantee it won't happen twice, in the area of media technology.

In the meantime, before x266 gets available, uvg266 is about to get useable. When anyone has the time and knowledge to make MABS support it, let's test it together...

[rwill]

Any news?

And does anyone know if x266 will have a deep psycho-visual pipeline? Modern encoders seem to put their focus there.

[Jamaika]

https://www.videoaktiv.de/2022110436...gestartet.html
Anyone tested? Worth the sin? What hardware for the new codec?

[LigH]

I doubt that x266 will be made by Fraunhofer, Jamaika... wrong thread for that link.

[birdie]

Updates on x266.

[DTL]

Originally Posted by rwill

And does anyone know if x266 will have a deep psycho-visual pipeline? Modern encoders seem to put their focus there.

I hope at some stage they will finally actively integrate noise reduction to reuse motion search data in both noise reduction and encoding stages. As I currently know only AV1 of modern enough codecs have more or less good progress to 'temporal noise reduction' with some not very few number of frames used.

[benwaggoner]

Originally Posted by DTL

I hope at some stage they will finally actively integrate noise reduction to reuse motion search data in both noise reduction and encoding stages. As I currently know only AV1 of modern enough codecs have more or less good progress to 'temporal noise reduction' with some not very few number of frames used.

Do you mean FGS or something else?

FGS is really an out-of-band process, not a codec feature per se. An encoder just gets the degrained source and grain reconstruction metadata to include. Which is a perfectly rational approach; grain removal is hard, complex, and advancing quickly. There's lots of benefit in grain removal not being normative, and just having the reconstruction be normative.

[birdie]

The last webinar questions have been answered.

I'm a little bit dumbfounded because seemingly some questions have been misunderstood, some others have very basic and uninformative answers.

[PatchWorKs]

For those who are interested in, latest FastFilx beta added x266 support (through VVCEasy):
https://github.com/cdgriffith/FastFl...es/tag/5.2.0b3

[FranceBB]

Unlikely given that x266 hasn't been released yet for public availability and it's not even available to Multicoreware's partners right now.
Looks like they added VVDec and VVEnc by Fraunhofer, which is still an H.266 Decoder and Encoder, but done by a different company.

Different projects, same goals.

[rwill]

Originally Posted by FranceBB

Looks like they added VVDec and VVEnc by Fraunhofer, which is still an H.266 Decoder and Encoder, but done by a different company.

Fraunhofer is not a company but an registered association.