IETF RTP Payload Format for JPEG-XS (ISO/IEC 21122) is published!

18.06.18 09:24 AM By Jean-Baptiste Lorent

As part of the rapid progress of TICO in JPEG XS standardization and its road towards interoperability, the IETF RTP Payload Format for JPEG-XS (ISO/IEC 21122) has been submitted. With this first step taken, JPEG XS is making its way to being standardized for Professional Media over IP as mezzanine compression for SMPTE ST 2110-22.

This opens the gates for JPEG XS' usage in Broadcast and Pro-AV systems which are currently under transition to IP based infrastructures and looking for smart ways to efficiently transfer more pixels at the best quality with the lowest possible latency and complexity.

To read more about TICO moving to JPEG XS and intoPIX's involvement and solutions, see intopix.com/jpeg-xs

RTP Payload Format for ISO/IEC 21122 (JPEG XS)

Abstract:

This document specifies a Real-Time Transport Protocol (RTP) payload format to be used for transporting ISO/IEC 21122 (JPEGXS) encoded video. JPEG XS is a low-latency, lightweight image coding system allowing for an increased resolution and frame rate, while offering visually lossless quality with reduced amount of resources such as power and bandwidth.

Discover the new IETF JPEG-XS RTP document

Note about the RTP payload packetization modes for IP Media worflows

Two RTP packetization modes are standardized in the JPEG XS payload offering more flexibility to implementers: A Codestream mode and A Slice-based mode.

The main difference is that the "Codestream mode" is sending the coded data in a raster scan order while the "Slice-based mode" enable to send the coded in a non-sequential transmission.

intoPIX recommends to apply (by default) the "Codestream packetization mode" for XS RTP payload. While it is offering the lowest latency of XS coding & decoding in all implementations: FPGA , CPU & GPU, the codestream packetisation mode offers also the following benefits:

Better quality encoding & efficiency in JPEG-XS keeping on-the-fly constant bitrate coding (few lines of latency , below the frame)
A direct remapping (no latency penalty) between RTP (ST 2110-22) and MPEG2-TS (ST 2022-2) without the need of parsing the codestream.
A direct remapping (no latency penalty) between RTP (ST2110-22) and MXF without the need of parsing the codestream

In contrary : the Slice-based packetization mode might be recommended in case of a non-sequential transmission of the codestream. It has a drawback in interoperability - causing other latency penalties in workflows, but might reduce the latency in the particular usage of some GPU. (This non-sequential benefits has not/never been proven and is difficult to make interoperable with hardware implementation (FPGA) & CPU.)

Contact our experts