IBC 2026 · RAI Amsterdam · 11–14 September 2026
We work inside your pipeline. SRT and RIST contribution, ffmpeg and GStreamer transcode, HLS and DASH packaging, playout automation, and the storage and compute underneath all of it.
IBC Accelerator · Q-Stream project
Four things teams call us in for.
SRT and RIST across links that drop packets. We size latency budgets and retransmit windows against the loss pattern a link actually has, and we read the pcap when the encoder’s own bitrate reporting disagrees with the switch.
ffmpeg and GStreamer pipelines built to survive a production week rather than a demo. Per-title encoding ladders, HLS and DASH packaging at the segment durations low latency actually needs, and a packager we wrote ourselves when the vendor’s would not go low enough.
Channel origination and playout automation: schedule ingest, as-run logging, graphics and subtitle insertion, and the failover path that has to work the one time it runs.
S3-compatible object storage, transcode capacity that scales with the queue instead of sitting idle between events, and deployments on Scaleway and OVH for teams whose media has to stay in the EU.
IBC Accelerator 2026
Q-Stream: Trusted Live Media Infrastructure
The IBC Accelerator programme puts vendors and broadcasters together to build something real against a show deadline, in public, with the results demonstrated on the floor. We are one of the engineering participants.
Q-Stream is about video that degrades gracefully instead of failing: adapting the stream from predictive network insight, compressing semantically rather than uniformly, and prioritising the parts of the picture that carry the meaning — so a feed stays usable at bitrates where it would normally fall over.
Who we have done this for, and what the work was.
Cloud platform services
IPTV / digital signage platform
VLC / VideoLAN
Video and cloud engineering, as their team rather than as a vendor at arm’s length.
Three shapes. The operational answers are below them, because that is what actually stalls a deal.
Two to five of our engineers inside your team: your sprints, your repo, your standups. You direct them the way you direct your own people.
You keep the client relationship and the spec. We take a defined slice of the delivery and hand it back tested, under your name.
Fixed scope, named outcome. Worth it when the problem is well understood and you need it built without adding permanent headcount.
Small team, all in one office. You talk to the people writing the code, and the person who scopes the work is the person who reviews it.
Thirty minutes, no deck. Tell us what the pipeline is doing and we will tell you whether we have fixed that before.
