iRacing endurance broadcast setup for 6, 12 and 24 hour races

A sprint race broadcast can get away with a basic setup. Endurance racing cannot: over 6, 12 or 24 hours the show has to stay readable while the field spreads out, drivers swap, incidents happen overnight and the crew gets tired. You need reliable OBS scenes, readable overlays, camera direction support, a replay workflow, commentator handovers, race-control messaging, a way for trusted people to help remotely and enough PC headroom to run for hours.

Why endurance broadcasts are harder

Endurance events have more moving parts than short league races. Multiclass traffic, pit strategy, driver swaps, damage repair, safety cars, full-course yellows, split strategies and fatigue all create race stories. Those stories can be hard to spot manually, especially once the field spreads out after the first hour.

The first 20 minutes of a 24 hour race usually has plenty of obvious action. Cars are close, the grid is compact and the producer has lots to choose from. Six hours later, the race may be decided by a class battle two laps down, a fuel number, a driver swap mistake, a slow repair or a car quietly catching the leader by half a second per lap. That kind of story needs better tools than a simple camera hotkey.

Long runtime. The broadcast system must stay stable for hours, not just survive a short session.

Multiclass racing. Viewers need class context, not just overall position.

Pit cycles. Strategy can matter more than on-track position.

Crew fatigue. The workflow must reduce manual admin and allow people to hand over cleanly.

Remote help. Longer races need a way for trusted team members to help without being in the same room as the broadcast PC.

Plan by event length

The longer the event, the more structure you need. Test the exact app version, class mix, remote roles and event rules before a major race.

Six hours

One producer and one commentator can succeed with stable tools, a clear break plan, Auto-Director support and a second person able to cover short absences. Focus on clean overlays, camera direction and replay basics, and rehearse the whole show once.

Twelve hours

Plan formal commentary and camera handovers, meal breaks and two complete operator states. Add sponsor loops, a stronger incident workflow and a backup operator. Fatigue becomes an operational risk.

Twenty-four hours

Use producer shifts, written handovers, remote backups, overnight graphics and a recovery plan for every critical source. Keep the admin load low and PC resource usage stable. Nobody should be the only person who knows the scene.

The core endurance broadcast setup

The core setup should be boring in the best way: stable, repeatable and easy to hand over. Use OBS for the stream output, browser-source overlays for race graphics, and a production tool to help with camera direction, replay and race-control messages.

Part	Why it matters
OBS scenes	Live race, replay, break, sponsor and results scenes need to work without fuss.
Overlays	Class colours, gaps, flags, driver info and pit context help viewers follow the long race.
Auto-Director	Helps find battles and race stories when the field spreads out.
Remote control	Lets trusted team members help with camera direction or production duties from another machine.
Replay workflow	Shows incidents and key moments without losing the live race.
Crew plan	Commentary and production handovers stop the show falling apart late in the race.

Remote control and shift work

The biggest problem with a 24 hour broadcast is not always the overlays or OBS. It is the human workload. One person should not have to sit awake for an entire 24 hour race just to keep the cameras moving.

24 hour production rule. Run a 24 hour broadcast in shifts. The host PC can stay live, but the people controlling cameras, watching battles and managing the show should be able to rotate.

How remote camera control should work

The safest model is not to move the whole broadcast to someone else’s computer. The host machine stays the centre of the show because it is connected to iRacing, OBS, the overlays and the stream. Remote team members control the broadcast through a limited production surface, not through a messy screen-share setup. In EDR Broadcast this is remote browser control, part of the League plan.

Host PC stays in control. iRacing, OBS and the main broadcast output remain on the local broadcast machine.

Remote controllers help direct. Trusted team members can assist with camera direction, battle selection and race monitoring.

Auto-Director still helps. Remote control does not replace automation; it gives humans a way to guide or override it.

Access should be controlled. Only trusted users should be allowed to control cameras or production tools.

Plan the access. A short broadcast may need one remote helper, while a 24 hour event run in shifts needs several. Decide who has control access for each shift before the race.

Example 24 hour camera-control roster

Not every team will have a full broadcast crew, but even two or three people sharing camera direction is better than one exhausted producer trying to do everything alone.

Role	What they do
Host producer	Keeps OBS, stream output, scenes and the main production workflow stable.
Remote camera director	Helps choose cars, battles, class leaders and camera focus during their shift.
Commentator	Calls the race and explains what the camera is showing.
Race monitor	Watches timing, incidents, pit cycles and Discord messages for things the director should show.
Relief operator	Takes over camera control or production duties while another team member sleeps.

For role definitions and handover habits, see the remote crew workflow guide.

Protect CPU and GPU headroom

Long race broadcasts can chew through resources if you stack too many heavy apps, browser sources and capture tools on one machine. Always test the full workflow before race day, not just the game.

Keep scenes clean, avoid unnecessary sources and make sure your overlay system is built for the job. If the broadcast PC is close to the limit before the green flag, it will not feel better after hours of racing.

This is also why controlled remote access beats running the whole broadcast through screen share. A browser-based production surface lets team members help direct the race without moving the iRacing capture, OBS output or overlay rendering away from the host PC.

What to show during quiet periods

Every 24 hour race has quiet periods. That does not mean the broadcast should feel dead. During long green-flag runs, rotate through class leaders, close battles, cars on different strategies, pit stops, damaged cars recovering through the field and team stories that give viewers a reason to keep watching.

• Show class battles, not just the overall leader. The multiclass broadcast guide covers class-first graphics and traffic.
• Use lower thirds to remind viewers who is driving and why the car matters.
• Follow pit cycles when strategy becomes the main story.
• Use remote team members to call out battles the main producer might miss.
• Bring back replays when incidents or major position changes happen off camera.

Where EDR Broadcast fits

EDR Broadcast was built by endurance racers who needed a cleaner way to manage cameras, overlays, race control and the replay workflow. For endurance events, the value is less about putting graphics on screen and more about reducing the load on the producer.

• Free covers the core overlays: leaderboard, lower thirds, ticker, flags, grid intro and podium.
• Pro adds the Auto-Director to help find race stories, replay, incident detection and the incident log, and race control with Auto Race Control.
• League adds remote browser control, so trusted team members can share camera direction and production duties across a long race, plus remote stewards and public live timing.

You can rehearse the Pro features on the 14-day Pro trial, started inside the app with no card required. Compare plans before you build the shift roster around remote control.

For the scene layer, read how to broadcast iRacing with OBS, then the iRacing broadcast production workflow guide and the iRacing Auto-Director guide.

Endurance broadcast checklist

• OBS live, replay, break and results scenes tested.
• Timing tower, lower thirds, flags, grids and results readable on stream.
• Auto-Director settings tested before race night.
• Remote control access planned for trusted team members.
• Commentary and camera-control shifts planned before the green flag.
• CPU, GPU and network load checked during a full workflow test.

Frequently asked questions

What makes endurance broadcasts harder?

They run longer, often include multiple classes, need pit-cycle context and require a workflow that can survive fatigue.

Do 24 hour broadcasts need remote camera control?

It is very useful, because trusted team members can direct the broadcast in shifts instead of one producer staying awake for the full event.

Do 24 hour broadcasts need Auto-Director?

An Auto-Director is useful because it helps find battles, incidents and race stories once the field spreads out.

Can team members help control the broadcast remotely?

With EDR Broadcast League, trusted team members can use remote browser control for camera direction and production duties, and remote stewards can review incidents, while the host PC keeps OBS and iRacing running locally.

What should I test before an endurance broadcast?

Test OBS scenes, overlays, audio, the replay workflow, remote control access, CPU and GPU load, commentary handovers and race-control messaging.