JPEG XS adoption has grown strongly in professional workflows where latency really matters, but when something goes wrong the symptoms can be misleading: sporadic macroblocks, washed-out color, A/V lag, or dropped frames that appear at exactly the worst possible moment. Here we offer a clear guide to diagnose and address the most common errors with JPEG XS in production and Pro‑AV environments.
In addition to the pure technical side of the codec, you have to understand the ecosystem it lives in. AVoIP combines standards and technologies such as IPMX, NDI, Dante AV and SDVoE, and in parallel, a new generation of ITU-T/MPEG codecs (EVC, VVC, and LCEVC) has emerged, influencing architectural decisions. There is also a very active video community, with everyone from dads with camcorders to Super Bowl engineers, including small-venue operators, panoramic screen specialists, LED wall engineers, and electrical video wall engineers. Questions and work sharing are encouraged, with clear rules such as Respect, no for-profit advertising, and zero tolerance for harassmentAll of this, when well-coordinated, helps resolve incidents with discretion.
What is JPEG XS and why you choose it
JPEG XS is a very low latency intra codec designed to preserve visual quality with lightweight compression. Its key advantages are latencies on the order of 1–5 ms End-to-end codec integration, quality stability, and simplicity of hardware implementation. It's ideal as a transport/mezzanine codec for remote production, camera links, room-to-room trunking, and, in Pro-AV, minimal-delay distribution.
On IP, JPEG XS fits perfectly with professional workflows such as SMPTE ST 2110‑22 (compressed video over IP), and is part of the IPMX approach for Pro‑AV. You'll typically see 10-bit 4:2:2 or 4:4:4 profiles to preserve color (including HDR), with bitrates adjusted to the available link, for example, 1080p/60 and 2160p/60 over 1/2.5/10 GbE, as appropriate.
The context of codecs: EVC, LCEVC and VVC vs JPEG XS
New generation codecs have emerged under the ITU-T/MPEG umbrella that are worth knowing so as not to mix up objectives. MPEG-5 Part 1 EVC was launched in 2020 with a reference profile designed to be royalty-free for content producers, and a main profile with more tools—subject to licensing—to squeeze out compression. It's not designed for ultra-low latency, but for distribution efficiency.
MPEG‑5 Part 2 LCEVC is intended as a low complexity enhancement layer which is added to a base codec (AVC, HEVC, etc.). The result is an output that, combined with that separate codec, improves quality and efficiency without replacing the entire stack. This is useful if you want more performance over H.264/HEVC, but not so much for latency-critical links like JPEG XS.
VVC (H.266) comes with a 30–50% improvement Compared to HEVC in terms of efficiency for distributing 4K, 8K, and even 16K UHD content, with very good HDR and 360° video compatibility. Again, its purpose is mass delivery, not low-delay live mezzanine transport.
Although EVC, VVC and LCEVC are still establishing themselves, there is industrial traction: for example, a partner like V‑Nova was key in LCEVC and developed a containerized application that can now be used in a variety of applications. be evaluated and implemented on AMD Alveo PCIe accelerator cards. This type of hardware acceleration is also common for JPEG XS on FPGAs, because ensuring constant latency and stable throughput is critical.
AVoIP and JPEG XS: IPMX, NDI, Dante AV and SDVoE
Several approaches coexist in AVoIP. IPMX was born as an open standard from broadcast, adapted to Pro‑AV, with the aim of achieving better interoperability and be a future-proof bet. IPMX contemplates low-latency compressed streams such as JPEG XS in combination with discovery/control mechanisms.
NDI, on the other hand, is the most popular standard right now, thanks to a market advantage of about six years and a mature SDK. It uses H.264/HEVC to leverage existing SoCs, achieving good cost-benefit on constrained networks, but with higher latencies than JPEG XS.
Dante AV arrived later, leveraging its audio strength to tackle Pro-AV video and compete seriously with NDI. Depending on the profile, it uses codecs such as JPEG 2000 or H.264/HEVC compression; in either case, does not always prioritize the absolute minimum latency as JPEG XS does in IPMX.
SDVoE, on the other hand, is positioned in the high-end range with very high quality, very low latency and high bandwidth over 10 GbE, dominating applications such as control rooms. It typically runs video with little or no perceptible compression, so it requires more generous infrastructure.
There are detailed comparisons of these four approaches from different angles. This is of interest for diagnostic purposes because errors that appear to be codec-related are sometimes caused by a protocol mismatch, multicast configuration or switch capabilities.
Rapid diagnosis: where to start
Before changing advanced settings, make sure the foundation is correct. This order often saves time and avoids chasing ghosts that aren't real; at each step, document what you change so you can reverse safely.
- Red: Bandwidth (1/2.5/10 GbE), loss, jitter, QoS/DSCP, IGMP snooping and PTP if applicable.
- Codec parameters: target bitrate, color format (4:2:2/4:4:4), bit depth (8/10/12), and profile/level support.
- Color and HDR: transfer (PQ/HLG), primary (Rec.709/2020) and range (full/legal), EDID and HDR management on displays.
- A/V Sync: Audio alignment (e.g. ST 2110‑30/31) with ST 2110‑22 video and buffer compensation.
- Interoperability: IPMX/NDI/Dante/SDVoE on gateways, converters and matrices, and how they encapsulate/discover flows.
Network and transport: the invisible cause of many evils
JPEG XS is robust, but if the IP transport degrades, you'll see it on screen. Monitor packet loss, jitter, and end-to-end latency. A sustained loss of 0,1% can cause artifacts or freezes on certain decoders.
Configure QoS with appropriate DSCP to prioritize video and enable IGMP snooping with querier if you use multicast. On switches without this configuration, multicast traffic can flood ports and cause micro-drops that look like 'codec glitches'.
If your stream requires precise synchronization, validate PTP (SMPTE ST 2059/IEEE 1588). A poorly distributed PTP results in lag, frame drops or buffer errors. Check PTP domain, priorities, and the presence of a stable GM.
Size the link with margin. A 2160p/60 4:2:2 10-bit with JPEG XS can move in tens or hundreds of Mbps depending on the target quality. At 1 GbE, this is feasible, but if it coexists with control traffic and other flows, reserve queues and apply shaping policies. In 10 GbE, they provide redundant paths (ST 2022‑7) for resilience.
Codec settings: quality, bitrate and color format
Rate control in JPEG XS tends to be deterministic: you set a target bitrate or quality and the encoder keeps latency ultra-low. If you see banding or contours For gradients, increase the depth to 10-bit and use 4:2:2 as a minimum for demanding chroma content.
For graphics with thin text or interfaces, 4:4:4 can prevent color bleeding. If you detect micro-artifacts On surfaces with fine detail (grass, water) and even during fast movements, slightly increase the bitrate or adjust the profile/level compatible with the decoder.
Remember that JPEG XS is intra: there are no GOPs or long time dependencies, which limits the damping of complexity peaks. In very complex scenes, the encoder may need a higher target bitrate to maintain 'visually lossless'.
HDR, primaries and range: when the color doesn't match
If HDR content looks dull or washed out, check the entire chain: PQ/HLG passthrough, BT.2020/709 primaries, and signaling. Most problems come from mismatch in EOTF (the display expects SDR) or in gamut (BT.2020 interpreted as 709).
Confirm that the encoder and decoder are working at a minimum of 10-bit for HDR and that the display is receiving the correct metadata. In Pro-AV, the EDID sometimes forces unexpected modes; capture the EDID, check if it advertises HDR, and block him if the monitor is the culprit.
A/V Sync: Lip and voice aligned
When the lip is out of sync, measure the offset and consult guides for fix multimedia errors. With ST 2110, audio travels on 2110‑30/31 and video on 2110‑22. Adjust the playout buffers on the receiver or add an audio delay to keep time. Avoid entering compensations by eye; measure with a tool and take notes.
True interoperability: IPMX, NDI, Dante AV and SDVoE coexisting
IPMX, being open and inherited from broadcast, usually gives you the best base for interoperability with JPEG XS. However, please check supported profiles between manufacturers. A 4:4:4 encoder may not work with a decoder that only accepts 4:2:2.
For NDI gateways, remember that NDI uses H.264/HEVC to lower bitrates and facilitate SoCs. When translating to/from JPEG XS, latency and perceived quality can change, which is sometimes mistaken for an 'XS issue' when it is actually a problem. transcoding.
With Dante AV, validate the codec mode of the profile you are using and whether the audio clock synchronization is aligned with the video. In SDVoE, carefully size the 10 GbE and the topology; a momentary saturation may appear to be a codec failure, but pure congestion.
Hardware, acceleration and deployment
For consistent ultra-low latency, FPGAs and accelerator cards are the order of the day. PCIe platforms like AMD Alveo enable containers ready for codec evaluation and deployment. While the most visible example is LCEVC—a containerized app created by V-Nova—the approach remains the same: reproducible deployment, measurement and scaling by module.
On field equipment, avoid blindly mixing firmware revisions. Plan windowed updates, with prepared rollbacks and A/B testing. An encoder with new microcode may resolve a color bug, but introduce a color variation. buffering that affects synchrony.
Typical cases and how they were fixed
Intermittent artifacts in 4K/60 on a shared 1GbE network: The cause was multicast traffic without IGMP snooping and no DSCP. Enabling IGMP, prioritizing video, and isolating control on a separate VLAN eliminated the issues; it also slightly increased the bitrate. target bitrate for complex scenes.
Washed-out color on an HDR LED wall: the encoder was in BT.2020 PQ and the display was interpreting 709 SDR via EDID. The correct EDID was set, 10-bit was forced, and the chain was verified to be maintained. Correct EOTFResult: flawless HDR.
A/V lag when bridging NDI with JPEG XS for remote production: the gateway added a buffer to the audio. The delay was measured and an equivalent delay was applied to the output video. With a stable clock and aligned buffers, the lip returned to its place.
When to choose another codec… and when not to
For OTT distribution, archiving or contribution with very limited bandwidth, codecs like VVC or schemes with LCEVC over HEVC can offer a bitrate savings huge compared to JPEG XS. But if you're looking for imperceptible latency and production quality, keep JPEG XS for the critical part and reserve heavy compression for the edge.
EVC, with its royalty-free reference profile and its main profile with licensed tools, can fit into chains where licensing costs are sensitive. However, its goal is not to replace JPEG XS Live, but to improve distribution.
Good operating practices
Clear port labeling, version documentation, configuration templates, and startup checklists prevent surprises. If possible, implement ST 2022‑7 (redundant paths) to eliminate micro-outages due to occasional network failures.
Monitor with actionable metrics: loss, jitter, latency, busy queues, PTP errors, and encoder/decoder stats. A dashboard with thresholds and alerts lets you see a problem before it becomes noticeable. screen.
The community also helps
In open video communities, everything is shared: questions, photos of setups, experiences, and scripts. The mix of profiles—from those setting up a meeting room to those operating a live LED wall—gives practical vision very valuable. Participate respectfully, avoid commercial self-promotion, and report any harassment.
Essential JPEG XS Checklist
- Network: DSCP, IGMP snooping/querier, stable PTP, 1/2.5/10 GbE capacity with headroom and, if possible, ST 2022‑7.
- Codec: 4:2:2/4:4:4 format depending on content, 10-bit for HDR, bitrate appropriate to scene complexity and profile/level compatibility.
- Color: EOTF PQ/HLG correct, BT.2020/709 primaries, correct range and EDID under control.
- Interoperability: IPMX as an open foundation, beware of NDI/Dante/SDVoE gateways and added latencies.
- Operation: controlled versions, monitoring with alerts and rollback procedures tested.
When you combine a well-managed network, consistent codec parameters, and thoughtful interoperability—IPMX with JPEG XS where latency matters, NDI/Dante AV when cost and flexibility matter most, and SDVoE when quality and 10 GbE matter—problems cease to be mysteries and become repeatable solutions. And if you also understand the role of EVC, VVC, and LCEVC in distribution, you'll be able to choose the right tool for each segment without sacrificing performance. quality, cost or time.
