Support for ST 2110-22 / JPEG XS?

[garethsb]

Most of the NMOS functionality to support description of coded video is already provided by nmos-cpp, but some convenience functions lack support. E.g. nmos::make_coded_video_flow is already provided by the nmos module, but nmos::make_sdp_parameters, which is used in the example nmos-cpp-node to construct an SDP file for the Sender based on the Source, Flow and Sender resources, doesn't work because it assumes a raw video Flow with "components" and therefore throws a json_exception.

It would be great to fill out the missing support for JPEG-XS in ST 2110-22 at least as constrained by forthcoming VSF TR-08.

And provide better error messages for unsupported media types.

Thanks to @David-P-B for the report.

[garethsb]

The I-D for the RTP payload mapping for JPEG XS is here: https://datatracker.ietf.org/doc/draft-ietf-payload-rtp-jpegxs/ The SDP format-specific parameters are covered in the latest draft: https://tools.ietf.org/html/draft-ietf-payload-rtp-jpegxs-09#section-6

[garethsb]

Version 18 looks pretty close to final...

https://datatracker.ietf.org/doc/html/draft-ietf-payload-rtp-jpegxs-18#section-8

[jonvmey]

IANA has a video/jxsv media type registration listed now (referencing draft version 18) which is the actual requirement for ST2110-22.

[garethsb]

RFC 9134 is now published, and we have a Work-In-Progress draft of AMWA BCP-006-01: NMOS With JPEG XS. Comments on that are welcome here: https://github.com/AMWA-TV/nmos-jpeg-xs.