iRacing broadcast software: the EDR Broadcast production workflow
Why EDR Broadcast puts overlays, cameras, incidents, replay and race control in one Windows app, and how it compares with other iRacing tools.
EDR Broadcast is iRacing broadcast software for leagues, endurance teams and solo producers: 45+ overlays and 15+ themes for OBS or vMix, with Auto-Director, incident detection, replay and race control in the same Windows app. This guide explains why we built it and what we think good production software should do. For a vendor-by-vendor review, read the iRacing broadcast software comparison.
What is breaking on your race night?
The camera keeps missing battles
Start with Auto-Director and manual override. Graphics cannot rescue a broadcast that is looking at the wrong car.
Viewers cannot understand the race
Prioritise readable class timing, focused-driver context, flags and replay labels before adding more decoration.
One operator is doing five jobs
Look for an integrated control room, remote helper access and safe automation. That workload problem is the reason EDR Broadcast exists.
Why EDR Broadcast was built
EDR Broadcast came from a real team problem. The team behind it runs long iRacing endurance events, including 24 hour races, where the broadcast can be almost as demanding as the race itself. Getting good camera angles, following the right battle and keeping viewers informed took too much manual work.
During endurance races, every extra app and every extra manual task matters. Heavy broadcast setups can use precious CPU resources, operators get overloaded, and the best race moments are easy to miss while someone is switching windows, chasing cameras or trying to find the right replay.
So members of the team built their own tool. The goal was simple: an iRacing broadcast control room that handles the repetitive, time-sensitive parts of the show, so league organisers and commentators can focus on telling the story of the race.
- Problem: camera direction was too manual during long endurance races.
- Problem: race admin, steward messages, replay and production tasks were spread across too many windows.
- Problem: heavy broadcast setups could chew through CPU resources during already demanding iRacing sessions.
- Solution: one purpose-made iRacing broadcast tool for overlays, cameras, replay and race-night workflow.
What makes good iRacing broadcast software?
Choosing iRacing broadcast software is not just about finding a timing tower. A proper league broadcast needs clean graphics, smart camera direction, replay control, incident awareness, sponsor space and a workflow that still holds together when the race gets chaotic.
A good broadcast tool should make the race easier to follow. Viewers need to know who is fighting, what class they are in, what lap the race is on, when penalties happen and why the camera has moved to a certain battle.
For iRacing league broadcasts, a tool has two jobs: give the league visual ownership and reduce the operator workload behind the show. A clean timing tower alone still leaves the operator switching cameras, watching incidents, triggering replay graphics, checking Discord, typing race-control messages and feeding information to commentators.
That is why EDR Broadcast is built around production control rather than just visual output. The graphics matter, but the real win is reducing the amount of work needed to keep the broadcast moving.
Why EDR Broadcast is different
EDR Broadcast is designed as a control room rather than a simple overlay pack. It combines OBS-ready browser sources with live race tools, Auto-Director logic, replay workflow, incident awareness and league operations features. The WYSIWYG Theme Editor removes the old choice between deep visual customisation and an integrated control room: build the league look, send coordinated overlays to OBS or vMix, let Auto-Director find the racing, log likely incidents and control the replay from the same Windows application.
- Browser-source overlays for leaderboards, lower thirds, tickers, flags, grid intros, podiums and other race graphics, in OBS or vMix. NDI output is available on request with Enterprise.
- Auto-Director to help follow battles, leaders, incidents, restarts and closing-lap pressure.
- Replay workflow so producers can identify incidents, jump back, show the moment and return live cleanly.
- Race control and Auto Race Control for steward messages and race-admin workflows.
- Lower admin load so race teams are not trying to run cameras, overlays, Discord, replay and stewarding from five different places.
- Endurance-first thinking because the tool came from long race nights, not a generic streaming overlay idea.
Plan availability. Free (A$0) runs on 1 machine with 2 looks and the core overlays: leaderboard, lower thirds, ticker, flags, grid intro and podium. Pro (A$19.95 a month or A$215.46 a year excluding GST, 2 machines) adds Auto-Director, replay, incident detection and log, race control and Auto Race Control, and all 15+ public themes. League (A$45 a month or A$486 a year excluding GST, 5 machines) adds the Theme Editor, cloud relay, remote stewards, Data Link, league schedule, League Profiles (coming soon), remote browser control and public live timing. Enterprise adds custom themes and overlays, NDI output on request and priority support. Check current plan details before choosing a workflow.
iRacing broadcast software comparison
Checked 22 August 2026.
Different iRacing tools suit different jobs. Some are excellent for timing. Some are strong for analysis. EDR Broadcast is focused on the live production side of league and endurance racing.
| Tool | Best fit | Main strength |
|---|---|---|
| EDR Broadcast | League and endurance broadcast production | Full race-night control room with OBS overlays, Auto-Director, replay workflow and race-control messaging. |
| ATVO | Experienced manual broadcast crews | Established iRacing broadcast workstation for teams who already know the workflow. |
| SDK Gaming | Polished timing and streamer overlays | Strong live timing, HUD and viewer data surfaces. |
| JRT | Timing, strategy and analysis | Detailed timing data and useful information for drivers, commentators and race review. |
| Native iRacing plus OBS | Simple DIY streams | Cheap and flexible, but the operator handles cameras, graphics, replay and comms manually. |
Sources: ATVO, SDK Gaming, JRT.
For the full market view, read the iRacing broadcast software comparison. For direct alternatives, read the ATVO alternative guide and the SDK Gaming alternative guide.
Why overlays alone are not enough
Most league broadcasts start with overlays. A timing tower, relative display and flag graphic immediately make the stream look more professional. But as soon as the racing gets busy, overlays are only one part of the job.
A proper broadcast needs story selection. Who is closing in? Which class leader is under pressure? Has an incident changed the race? Is a penalty coming? Should the replay go now or after the pit cycle? This is where a tool built around production control has an advantage over a basic overlay package. The overlay guide covers what the graphics themselves should do.
Built for OBS, leagues and 24 hour races
EDR Broadcast is built around browser-source graphics so it can sit cleanly inside an OBS production. That matters because OBS is still the common base for Twitch, YouTube and Facebook streams.
The app is also shaped by endurance racing. In a 24 hour race, the broadcast tool has to keep working when the field spreads out, drivers swap, incidents happen overnight and the operator needs quick access to the important moments.
That is why the goal is not to replace the producer. The goal is to reduce the workload, surface better race stories and make it easier to produce a professional-looking iRacing broadcast with a smaller crew. The value sits behind the graphics: one production surface for the decisions that keep a race understandable.
Who should use EDR Broadcast?
- League admins who want their race nights to look more professional.
- Solo producers who cannot manually run cameras, overlays, replay and race control at the same time.
- Commentary teams that need clean driver information, timing and race moments.
- Endurance event organisers who need multiclass information and consistent graphics.
- Sim racing communities trying to attract sponsors with better broadcast presentation.
Production rule. The right iRacing broadcast software is the one that keeps the show readable when the race gets messy. Clean graphics matter, but workflow matters more.
Frequently asked questions
What is EDR Broadcast?
EDR Broadcast is a Windows app for iRacing broadcasts, built for live league racing and endurance production. It helps with OBS overlays, camera direction, replay workflow and race-control messaging.
Who built EDR Broadcast, and why?
Members of the iRacing endurance team behind EDR Broadcast built it because camera direction, replay control, race admin and overlays took too much manual effort during 24 hour and other long endurance races.
Which iRacing broadcast software suits a league?
It depends on what the league needs beyond a timing overlay. EDR Broadcast is built as a race-night production tool with OBS overlays, Auto-Director, replay workflow and race-control features. Compare it with other tools in the iRacing broadcast software comparison.
Does EDR Broadcast work with OBS?
Yes. EDR Broadcast is designed around OBS browser-source workflows so graphics can be added to a live stream cleanly. The same transparent browser-source overlays also work in vMix.
Is EDR Broadcast only for professional broadcasters?
No. It is designed to help solo producers, league admins and commentary teams create a more professional show without needing a large crew.