What about adding also H.266/VVC?

[yekuiwang]

Indeed, thanks from our side as well for the good job for enhancing the RTMP & FLV specs!

We at Bytedance are interested in adding also the support of H.266/VVC. Is it OK to add that?

[yekuiwang]

OK, let me ask two other questions. Anyone else interested in adding H.266/VVC? Anyone has whatever concern on adding H.266/VVC?

[veovera]

Thanks for the H.266 suggestion. We will take a look and evaluate.

[zenomt]

with the move to fourcc, adding new codecs should be independent of RTMP and FLV now. instead adding new codecs should be with codec-specific docs that give the fourcc and any codec-specific syntax or semantics mapped onto the generic enhanced RTMP (similar to the WebCodecs Codec Registry and e.g. HEVC Registration).

i'm only just starting to look deep at Enhanced RTMP, but i see one hindrance to generality already regarding composition time offsets, which i'll raise in a new issue.

[zenomt]

i opened #9 about the composition time offset issue, and also suggested a separation of syntax from codec registry.

[veovera]

RTMP messages are transferred using a lower level transport layer (i.e. RTMP Chunk Stream). RTMP messages that carry compressed AV data may have associated hint information as part of the message. Correct, you can define any fourcc. It would however behoove to define fourcc plus appropriate set or hints/rules at the same time as part of the Enhanced RTMP to make sure that developers settle on specific set of rules and behaviors for a particular fourcc data format. This assures that a stream behaves the same no matter what tech stack delivers or plays it.

[yekuiwang]

Given the way how H.265/HEVC has been added, the changes needed for adding H.266/VVC can be simple and similar, like the following:

1. Add a Video FourCC value VVC = {'v', 'v', 'c', '1'}.
2. Add VideoTagBody corresponding to VVC, similar as that for HEVC, but with "DATA = [VvcDecoderConfigurationRecord]" and "DATA = [VVC NALU]".

[TroyKomodo]

Out of curiosity is there any playback support in the major vendors for VVC yet?

• Such as browser support (in any browser)
• Desktop Player Support (in any desktop player)
• Encoder Support (in any encoder)

I have not heard much about VVC. I was curious if anyone is currently working on adding support to chromium, vlc or ffmpeg.

Since, well as nice as it would be to supporting the codec using RTMP I dont understand what device will end up consuming the stream if there is currently no support anywhere else

[yekuiwang]

@TroyKomodo You can find information on the deployment status of the VVC standard from this document: https://www.jvet-experts.org/doc_end_user/current_document.php?id=12630.

[mypopydev]

Any progress?

[veovera]

Thanks everyone for your patience and for the constructive input on this much anticipated feature.

Now is a good time to revisit support for H.266/VVC in E-RTMP. We’ve actually made progress on the documentation side, and there’s already a draft spec covering the required FourCC, tag structure, and configuration record format. The remaining questions largely center around testing and making sure that implementation makes its way into key open-source projects such as FFmpeg, etc.

We’ve spoken with several stakeholders who are deeply interested in VVC support, and I’ll be reaching out directly to some of you to continue the discussion and share where things stand.

More to come shortly!

P.S. @mypopydev @yekuiwang — would you be interested in collaborating on this feature?

[yekuiwang]

P.S. @mypopydev @yekuiwang — would you be interested in collaborating on this feature?

Sure, absolutely.

[veovera]

Please take a look at #49. I started a discussion on the VVC topic as it pertains to E-RTMP. Posting here for situational awareness.