← All posts
multi-channelbroadcastcase-study

One match, three languages, zero duplication

How a tournament organizer ran the same final across three regions — each with its own sponsors and language — from a single dashboard.

TQ

Team Quadraviz

March 15, 2026 · 7 min read

One match, three languages, zero duplication

Last month an esport league asked us a simple question: can you stream the same final in English, French, and Spanish — each with its own sponsor lineup — without three production teams?

Yes. Here's how.

The problem

Traditional setups duplicate the project. Three OBS scenes, three sets of overlays, three operators changing the same score three times. One mistake on one channel and the streams drift.

The fix: shared state, separate channels

In Quadraviz, every channel can subscribe to the same source of truth. You change the score once; every channel updates. But each channel keeps its own visual layer — language, sponsors, lower thirds.

ts
const match = quadraviz.matches.create({
  teamA: 'Wraiths',
  teamB: 'Hex Foxes',
});

['en', 'fr', 'es'].forEach((lang) => {
  quadraviz.channels.create({
    name: `Final – ${lang}`,
    bind: match,
    sceneOverrides: {
      language: lang,
      sponsorPack: `final-2026-${lang}`,
    },
  });
});

What the operator sees

One dashboard. Three live previews. Score updates fan out to every channel. Each channel's sponsor pack rotates on its own schedule. The operator never opens three projects.

The numbers

  • 1 operator, down from 3
  • 0 score-drift incidents across 18 matches
  • 40% lower production cost vs. the previous season

If you're running multi-region streams and still copying projects, you're paying a tax that doesn't have to exist.