This document discusses the challenges of implementing uncompressed video over IP in software. It notes that reducing OS overhead is important and can be achieved through techniques like Netmap, PF_RING and Registered I/O. It also mentions that software frame bugs are rare but CRCs can be costly, and format conversions are slow without optimized assembly code. Non-standard line widths can also be annoying to work with. The document concludes by advertising open jobs at the company that works on broadcast video over IP software.

1. Implementing uncompressed over
IP in software and the pitfalls
Kieran Kunhya <kierank@obe.tv>

5. Hardware
• Need to reduce OS overhead (see BBC R&D @
UKNOF)
– Netmap, PF_RING, Registered I/O (Windows)
– Craft packets yourself
• Limits hardware choices, kernel versions, tunings
• 2022-7 (hitless switching) using kernel bypass
directly – two cards at the same time?

6. Software
• SDI frame bugs few have encountered
• CRCs costly and arguably unnecessary
• Many pixel formats (most broadcast specific)
• Slow format conversions without handwritten
assembly code (10x speed boosts)
• Non mod-6 line width (1280x720) annoying
• Written in Upipe (think Apache vs nginx).
• Unicast ARP problems

7. We’re hiring!
Work at the SpaceX of broadcast

8. • Upipe.org
• BBC R&D UKNOF -
https://www.youtube.com/watch?v=yLL8wl8YUwA