Versatile Video Coding (VVC) / H.266: HEVC successor

[birdie]

And here's a 2023 codec adoption roadmap from Rethink Technology Research:

[vahid]

How about PUs of I frames? extract the 4x4's PUs of each I frame separately in VVCSoftware_VTM?

[Jamaika]

I don't think this is question for this forum. You have to be codec developer.
https://stackoverflow.com/questions/...-identical-mvs
These are the functions for JCTVC HEVC
ctu->getTotalNumPart() == 256
ctu->getDepth(48) == 3
ctu->getPredictionMode(48) == INTER_MODE
ctu->getPartitionSize(48) == Nx2N

https://www.intechopen.com/chapters/52002
extract the 4x4's PUs of each I frame separately in VVCSoftware_VTM?
ptu->getTotalNumPart() == 256
ptu->getDepth(48) == 5
ptu->getPredictionMode(48) == INTRA_MODE
ptu->getPartitionSize(48) == NxN
Your case is definitely Intra mode and depth 5. For VVC max CU is 128x128. I just don't know what the function equivalents are in JVETVVC. Officially JVETVVC isn't PTU function
partitioner.currPartIdx() == 256
partitioner.currDepth == 5

[vahid]

Originally Posted by Jamaika

I don't think this is question for this forum. You have to be codec developer.
https://stackoverflow.com/questions/...-identical-mvs
These are the functions for JCTVC HEVC
ctu->getTotalNumPart() == 256
ctu->getDepth(48) == 3
ctu->getPredictionMode(48) == INTER_MODE
ctu->getPartitionSize(48) == Nx2N

https://www.intechopen.com/chapters/52002
extract the 4x4's PUs of each I frame separately in VVCSoftware_VTM?
ptu->getTotalNumPart() == 256
ptu->getDepth(48) == 5
ptu->getPredictionMode(48) == INTRA_MODE
ptu->getPartitionSize(48) == NxN
Your case is definitely Intra mode and depth 5. For VVC max CU is 128x128. I just don't know what the function equivalents are in JVETVVC. Officially JVETVVC isn't PTU function
partitioner.currPartIdx() == 256
partitioner.currDepth == 5

[birdie]

MSU has released "MSU Video Codecs Comparison 2022".

Tencent-TVC and Tencent266 codecs have beaten everything under the sun but you cannot download or use either.

And here's a August 2023 VVC adoption report from Streaming Media.

Meanwhile there's been no news in regard to x266 but H2 is not over yet.

[Atak_Snajpera]

Originally Posted by birdie

MSU has released "MSU Video Codecs Comparison 2022".

Tencent-TVC and Tencent266 codecs have beaten everything under the sun but you cannot download or use either.

And here's a August 2023 VVC adoption report from Streaming Media.

Meanwhile there's been no news in regard to x266 but H2 is not over yet.

Chinese BS...

[birdie]

Out of tree native VVC decoder for FFMpeg is now complete.

Now idea when it's gonna get merged.

[Jamaika]

Originally Posted by birdie

Out of tree native VVC decoder for FFMpeg is now complete.

Now idea when it's gonna get merged.

Decoder is currently only 10bit 420/422 and doesn't support Intra Block Copy and Palette.

[PatchWorKs]

Originally Posted by MoSal

On the other hand, it's the first time I hear about xin26x which could develop into a good encoder suite if the developers ever get to a stage where some effort is spent on subjective tuning.

Well, just discovered it on GH:

• Xin26x is an univeral video encoder framework, which can accommodate all video coding standard on this planet so far.
• It is optimized for real time video communication, live streaming application and offline video encoding.
• It currently supports HEVC, AV1(I frame), VVC video coding standards.
• It is a very high performance encoder.
• It is well-structured for understandability, maintainability and scalability.
• It is written from scratch and has a plain C API to enable a simple integration into other software.
• It is very small footprint encoder, it takes very small memory requirement under restricted mode.

According to the Git, it's buildable and working (even if not complete -> check Todos)

Does anyone tested it ?

[ShortKatz]

Originally Posted by birdie

Out of tree native VVC decoder for FFMpeg is now complete.

Now idea when it's gonna get merged.

Hope this gets merged soon into FFmpeg master. But the thread executor is also still missing.
http://ffmpeg.org/pipermail/ffmpeg-d...st/313669.html
Edit: Now it is not missing anymore.

[birdie]

Probably the first Android ROM with built in VVC support (it's not specified whether it's for encoding or decoding, I guess it's decoding only):

https://forum.xda-developers.com/t/r.../post-88979437

For OnePlus 9.

[benwaggoner]

Originally Posted by birdie

Probably the first Android ROM with built in VVC support (it's not specified whether it's for encoding or decoding, I guess it's decoding only):

https://forum.xda-developers.com/t/r.../post-88979437

For OnePlus 9.

Software decoder or actual hardware one?

[birdie]

Originally Posted by benwaggoner

Software decoder or actual hardware one?

You can bet 100% it's a software decoder. There's been no SoCs for mobile phones with HW VVC decoding support yet.

I have a sneaking suspicion Qualcomm Snapdragon 3 will be the first to support HW VVC decoding. We'll learn about that in just a few months.

[birdie]

More patent pools:

https://www.streamingmedia.com/Artic...ticleID=161147

[benwaggoner]

Originally Posted by birdie

You can bet 100% it's a software decoder. There's been no SoCs for mobile phones with HW VVC decoding support yet.

I have a sneaking suspicion Qualcomm Snapdragon 3 will be the first to support HW VVC decoding. We'll learn about that in just a few months.

Qualcomm wouldn't be surprising. And given the costs and variability of mobile bandwidth, it's the market where new codecs can have the quickest immediate customer benefit.

[hajj_3]

Originally Posted by birdie

}I have a sneaking suspicion Qualcomm Snapdragon 3 will be the first to support HW VVC decoding. We'll learn about that in just a few months.

no vvc in that soc: https://www.qualcomm.com/products/mo...obile-platform

[birdie]

Originally Posted by hajj_3

no vvc in that soc: https://www.qualcomm.com/products/mo...obile-platform

Right, that's a huge bummer (in VVC adoption) :-(

"Hardware-accelerated H.265, VP9, AV1 decoder".

Even SnapDragon 8 Gen 2 can decode 4K@30fps in software mode but battery life will be decimated.

[benwaggoner]

Originally Posted by hajj_3

no vvc in that soc: https://www.qualcomm.com/products/mo...obile-platform

That is somewhat surprising, and disappointing.

[Emulgator]

Well, I wouldn't have expected VVCDec cast into mobile silicon this year.
Not from a chip manufacturer's view: energywise, bugfixwise, IP/patentwise I would have considered it too early days.
The few in business (only 2 or 3 fabs can do that, IIRC) got to deliver perfectly working batches in expensive 4nm for a few hard-earned dollars.
The slightest fault or unkept promise and the market will kill their margin.
Maybe the market will be ready to pay up again for the next feature set, on display end 2024, on the shelves 2025.
VVCDecoding effort will call for 3nm. Encoding ? way out.
Mobile devices can have 1TB on board today, mine from 2021 has 512GB, and I opted for AVC encoding, not HEVC.
No need for compressing the hell out of the private video, battery life will drop as we speak, and that counts as sale argument.

[kurkosdr]

Originally Posted by benwaggoner

That is somewhat surprising, and disappointing.

Nothing surprising here, very few people outside Doom9 have even heard of VVC, except perhaps 8K enthusiasts (all 3 of them) who may have heard it's the format intended for 8K broadcasts over sat or terrestrial (in the oft-chance such broadcasts ever happen). Hardware support for VVC is pretty slim (I am not gonna pretend 8K "Ultra-Ultra-HD" TVs are anything other than a niche, since they are basically an uncut motherglass of four UHD TVs posing as "innovation" that nobody cares about) and so is available VVC content. Everyone out there checks for HEVC and AV1 hardware support for 4K UHD resolutions, so that's what the industry is providing (for now, at least).