Multiviewthe viewer decides

IBC 2026 · AWS Elemental Media Services & Qualabs

The multiview your viewer builds

A tournament runs six matches. Your channel carries one.

AWS Elemental Media Services composes the grid up in the cloud, so it reaches the viewer as one ordinary channel. Qualabs puts it on air and builds the layer your viewer touches to choose what is inside it.

AWS Elemental Qualabs
Pick the events, while it plays Pick the one you hear Pick the shape of the grid

The controls appear when you touch the picture — change the shape, drag one view onto another to swap them, or tap one to choose the one you hear. Five of the platform's seven shapes, drawn from measured geometry: the black between and around the pictures is what the service really leaves. Stock footage, silent, and not the demo's own feeds.

Where a grid earns its place

3 kinds of event this was built for

The players who matter

Fixed cameras on the few people the audience came to watch, and the viewer decides which of them is on screen.

A league, all at once

A round where several matches kick off together. Today you pick one for everybody; here each viewer picks their own.

Sports that are already multi-camera

Motor racing and golf are covered from a dozen positions before anybody asks. The grid is what that coverage was always for.

Under the hoodthe path, the parts, and the traps

What connects to what

Your feeds MediaLive MediaPackage CloudFront The player one per event encoded once composes on request caches each grid our overlay CMAF HLS HLS HLS One stream per combination, each carrying the audio of every event in it

The grid is built at the third block and nowhere else. Nothing of ours sits anywhere in this path.

Five pieces, and no backend of ours anywhere in the path

  1. Your live inputsWhatever you already produce. At the stand, four looping clips.
  2. MediaLiveOne channel per event, encoded once with settings that let the tiles sit together.
  3. MediaPackageBuilds the grid on request, without decoding or re-encoding a single combination.
  4. CloudFrontOne HLS stream out. The cache key carries which composition it is.
  5. The playerhls.js unmodified, plus our overlay. No build step, no framework.

How many different grids four events can make

24two-view grids2 shapes × 12 orders
72three-view grids3 shapes × 24 orders
48four-view grids2 shapes × 24 orders
148in totalplus each event on its own

Position is part of the composition, so the same four events in a different order are a different grid. None of them costs another encode.

Three parts, and one of them is ours

AWS Elemental Media Services composes

One HLS stream per multiview combination, and every one of them carries the audio track of each event inside it.

Qualabs builds it, either way

End to end, or just the part your viewer touches: the experience of moving through a multiview — changing cameras, choosing the audio — lives in the player, and that is the piece we build for your use case.

Your feeds stay yours

We build inside the app your audience already opens, not beside it.

Come and change it yourself

The remote is on the stand

Four channels running live through the platform, and the people who built it standing next to it.

IBC 2026 · Amsterdam Hall 5 · Stand 5.C90

Or tell us what you would put in the grid

Goes straight to the Qualabs growth team.

Message sent. We’ll be in touch soon. ✓

Something went wrong sending your message. Write to growth@qualabs.com and we’ll pick it up there.

Write to growth@qualabs.com
or find us at IBC 2026 — Hall 5, Stand 5.C90.