The question comes up in every OB truck I've worked in, usually from a runner or a junior technician leaning into the EVS island during a quiet passage of play: "So what's the actual difference between EVS XT and LSM?" They've heard both terms thrown around the talkback all morning, often in the same sentence, sometimes referring to the same clip. It's a fair question, and the answer is genuinely useful — but it's also the wrong question to ask first.

If you're new to live broadcast, the vocabulary around replay is genuinely confusing. The kit is sold under one brand, controlled under another name, and people on the truck use both words interchangeably depending on where they're standing. Before you can understand the difference, you need to understand that EVS — the company, the server, and the controller — is a stack, not a single box.

I've been on EVS since February 2009. Seventeen years, across the Premier League, Champions League, Olympics, Wimbledon, Roland-Garros and the Dubai World Cup, working for BBC, ITV, DAZN, Amazon Prime Video, ESPN and UEFA. In that time the hardware has gone through three full generations, but the language on the truck hasn't really caught up. So let me clear it up properly.

The short answer (and why it's a trick question)

EVS is the company. XT is the server. LSM is the controller. That's the whole distinction, and once you internalise it, ninety percent of the confusion on the truck disappears.

When a director says "get that on the EVS," they mean: record it, clip it, have it ready for me. When a colleague says "I did it on the LSM," they mean exactly the same thing — they used an EVS workflow, driven from the LSM controller, on an XT server. The two phrases are shorthand for one system. People pick whichever word matches where they were sitting.

The reason it feels like a trick question is that EVS the company (Belgian, founded in 1994) makes both halves of the system. There is no "XT versus LSM" choice to make on a show. You will use both, every shift, because one is the recorder and the other is how you drive it. The real question isn't which to pick — it's what each one actually does, and how they fit together in a football OB.

What EVS is, what XT is, what LSM is

EVS — the company behind the whole stack

EVS is a broadcast manufacturer headquartered in Liège, Belgium, founded in 1994. They build live production hardware and software, and in live sport — especially Tier 1 OBs — they hold somewhere north of 90% market share. If you walk into a football outside broadcast anywhere in the world, the replay island is almost certainly EVS. Grass Valley, Avid and Adobe have all tried to take slices of it; nobody has, at the top end.

The name "EVS" gets used three ways on the truck: for the company, for the server line, and loosely for the entire replay workflow. Context tells you which one someone means.

XT — the server line

XT is the server product family. The generations I've worked through are XT3, XT4A and now XT-VIA. The XT-VIA is the current flagship. It records multiple video channels in a continuous loop — typically six to nine hours deep per channel — so as an operator you literally cannot "miss" something. The action is always already on disk before you've decided it matters.

XT-VIA supports up to 12 HD or 6 UHD channels, and it handles both SDI and IP (SMPTE 2110). That IP capability is the big shift in the current generation — modern OBs are moving away from coax and into IP fabric, and XT-VIA speaks that natively.

LSM — the controller

LSM stands for Live Slow Motion. It started life as a separate slow-motion product decades ago. Today, when an operator says "LSM," they mean the handheld controller: the panel with the jog wheel, the T-bar and the twelve-plus programmable keys. The current model is the LSM-VIA. This is the thing you actually touch, eight hours a match, both hands on it, eyes on the screen.

If you want to go deeper on what an operator actually does with this kit day to day, I've written a full breakdown here: What does an EVS operator do in live sport?

Inside an XT-VIA: what the server actually does

The XT-VIA's job, fundamentally, is to ingest cameras, record them in a loop, and serve clips to whoever needs them — me, other operators, the highlights editor, the graphics engine. It does this in real time, with no rendering, no waiting, no "give it a second." When a striker hits the post and the director calls for the angle, the clip is already available the moment the words leave their mouth.

A single XT-VIA chassis handles up to 12 HD or 6 UHD channels, with IP I/O on SMPTE 2110 and traditional SDI on the same frame. That's a meaningful jump from the XT4A, which was already good but was fundamentally an SDI box. The current generation is built for the IP truck, and most of the Premier League and Champions League shows I work now are fully IP from camera to server.

The loop is the part juniors underestimate. Six to nine hours per channel, recorded continuously, means you don't need to be "ready" for an incident — you're always ready, because everything is already there. My job isn't to catch the moment. It's to know which of the eight angles the director is going to want, and to have it punched up and trimmed before the talkback call finishes.

From the panel If the server is the brain, the LSM is the muscle memory. After 17 years, I don't think about the jog wheel — my hand just goes.

Inside an LSM-VIA: the controller you'll live on

The LSM-VIA is the controller — the physical panel in front of you. Jog wheel for frame-by-frame shuttling, T-bar for variable-speed playback, twelve-plus programmable keys for marks, clips, playlists and macro sequences. You set the keys up per show, per sport, per director's preference. By the time the match starts, your hands know the layout without you looking down.

This is where the muscle memory lives. The server does the heavy lifting in the background, but the controller is the instrument you play. After seventeen years I don't think about which key marks an in-point — I just hit it. I don't think about jog wheel direction or T-bar pressure; my hand just goes. That fluency is the actual job, and it only comes from hours on the panel under real pressure.

Here's a quick comparison of how the two halves of the system differ — and where the supporting software sits:

  • XT-VIA (server): up to 12 HD / 6 UHD channels; SDI + SMPTE 2110 IP I/O; 6–9 hour loop per channel; runs Multicam(LSM) and the clip database; lives in the rack or the EVS island.
  • LSM-VIA (controller): jog wheel, T-bar, 12+ programmable keys; USB host and ethernet to the XT; one operator, one panel; fully reconfigurable per show; the physical instrument you actually play.
  • Multicam(LSM): the replay application itself — runs on the XT server and is driven from the LSM controller. This is the software that turns incoming feeds into marked, trimmed, named clips ready for air.
  • IPDirector: the separate PC-based UI for logging, tagging, searching and building playlists. Used alongside the LSM when the show needs heavy clip management — longform, highlights, or complex tag structures.

How they talk to each other: Multicam(LSM) and IPDirector

This is the bit most people outside the island never see. The LSM controller doesn't work in isolation — it drives Multicam(LSM), the actual replay application, which runs on the XT server. Multicam(LSM) is where the channels are ingested, where the live loop is visible, and where you mark in/out points, build clips and push them to air or to a playlist.

Alongside that, there's IPDirector — a separate piece of software running on a standard PC. IPDirector is the clip-management and logging interface. If Multicam(LSM) is your instrument for the live cut, IPDirector is your library: it's where you (or a dedicated logger) mark events, tag them, search across the entire afternoon's content and assemble playlists for highlights or for the edit suite.

On a football OB I'll typically have Multicam(LSM) up on my main monitor with the LSM-VIA under my hands, and IPDirector running on a second screen for search and tagging. The two talk to each other through the server — a clip I mark in Multicam(LSM) is immediately available in IPDirector, and a playlist I build in IPDirector is ready to play out from the LSM. It's one shared database, two ways in.

What a Premier League OB looks like on the kit side

A typical Premier League outside broadcast runs three to six EVS operators, each on their own XT-VIA channel pair, all sharing clips across the truck's network — NetCenter or MediaHub, depending on the build. We're not siloed. A clip I cut on my panel is visible to the operator next to me within seconds, and the VT coordinator can pull anything from any of us into a highlights package.

A rough channel plan for a single match might look like this:

  1. Operator 1 — main tactical (Cam 1 + Cam 2): the wide and the main tight. Primary replay angle for the director.
  2. Operator 2 — close-ups (Cam 3 + Cam 4): player close-ups, manager reactions, the angles that sell emotion.
  3. Operator 3 — SSM / Super Slow (Cam 7 + Cam 8): dedicated super-slow-motion cameras at 3x speed (around 150 fps). These need their own channels and their own camera sensors — you cannot fake SSM from a standard camera feed.
  4. Operator 4 — goal / behind (Cam 5 + bee-hole): the low goal angle, the behind-goal tight, anything specialist the director has asked for.
  5. Operator 5 — highlights / IPDirector: logging tags, building the half-time playlist, feeding the edit suite. Often running IPDirector as their primary interface.
"When the director says 'replay angle 3,' it's not a debate. The clip has to be on air two seconds later. That only happens if every operator in the island is on the same network and the same database — which is exactly what EVS gives us."
— Martijn V., EVS operator & VT coordinator, Premier League & Champions League

When that call comes — "replay angle 3" — it means operator 2 in the plan above. They punch the clip up via the LSM, the clip plays to the program feed, and the loop keeps recording the whole time. Nothing stops. For a fuller walkthrough of how the coordination layer manages this end to end, see How VT coordination works on a Premier League broadcast.

Are there alternatives to EVS?

Yes, and it's worth being honest about them rather than pretending the market is a monoculture. Grass Valley makes the K2, Avid makes AirSpeed, and Adobe has pushed Premiere-based live-cut workflows. They all exist, they all work, and in some regional or lower-tier productions they're in regular service.

But on Tier 1 live sport — Premier League, Champions League, the majors — EVS is the default for a reason. The latency from ingest to available clip is effectively zero. The loop is bulletproof. The LSM controller is a mature, physically robust instrument that operators can drive fluently under real pressure. And the shared-clip network (NetCenter / MediaHub) is the thing that makes a six-operator football show actually work — no alternative has matched that workflow at scale. I've turned up to trucks in fifteen countries over seventeen years and the replay island has been EVS every single time.

If you ever hear "EVS servers explained" as a training topic and someone tries to frame it as a competitive comparison, treat it with suspicion. The honest version is: XT is the recorder, LSM is the controller, and together they are the workflow.

Which should you learn on?

Both — because they're the same workflow. If you're starting out, the question isn't "XT or LSM," it's "how do I get hands on an LSM-VIA panel and an XT-VIA running Multicam(LSM), and learn them as one system." The server is theory; the controller is practice. You need both, and you need the connecting software too.

Practically: find a facility, a hire company or a college course with a live EVS island, or a certified simulator, and put in the hours. Learn the jog wheel until it's unconscious. Learn Multicam(LSM) front to back — in, out, mark, clip, playlist, playout. Then pick up IPDirector, because clip management is what separates a junior from someone a coordinator will actually book. I've written the full path — equipment, training, getting the first job — in How to become an EVS operator.

And if you're a production company reading this because you need someone who can actually drive the kit on Saturday: I'm available for bookings, based out of Dubai, and I travel worldwide.