iRacing Broadcast Knowledge Base

On this page

This post contains domain knowledge for AI-powered broadcast direction of iRacing sim racing events. It covers the iRacing platform, race procedures, camera systems, and professional broadcast directing principles.

1. iRacing Platform Overview

iRacing is a subscription-based online racing simulation. It is widely regarded as the most realistic and competitive sim racing platform, used by professional esports organizations, racing leagues, and content creators worldwide.

Session Types

Practice: Free driving with no competitive timing. Drivers enter and exit at will. Good for establishing camera shots and testing equipment.
Qualifying: Timed laps to determine grid position. Each driver typically gets a limited number of laps. Coverage should focus on the fastest lap attempts.
Race: The competitive session. Grid positions determined by qualifying. All drivers start together. This is the primary broadcast session type.
Warmup: Brief session before the race for final car adjustments. Low broadcast priority.
Cooldown: Post-race session. Minimal broadcast value except for podium/celebration shots.

Race Types

Sprint Race: Short races (15-45 minutes). Fast-paced coverage with frequent camera changes. Every position battle matters.
Endurance Race: Long races (1-24 hours). Coverage pacing varies -- intense at start/end, more relaxed during middle stints. Pit strategy becomes a major narrative element.
Heat Racing: Multiple short races (heats) feeding into a main event. Track results across heats for storyline continuity.
Time Trial: Individual timed runs. Focus on one driver at a time with split comparisons.

Car Classes

iRacing features multiple car classes that may race simultaneously (multi-class events):

Prototype/LMP: Fastest class. Top speed 200+ mph. Often the focus during multi-class events due to speed and overtaking.
GT3: Grand touring cars. Close racing, lots of battles. Excellent for dramatic coverage.
GT4: Slightly slower touring cars. Good support class coverage.
Open Wheel (Formula): Single-seater cars. Clean overtakes at high speed. Dramatic starts.
Stock Car (NASCAR): Pack racing with side-by-side action. Restrictor plate tracks create massive packs.
Sports Car: Various categories from Mazda MX-5 to Porsche 911. Good for entry-level broadcast.
Dirt: Oval and road course dirt racing. Unique camera challenges due to dust and sliding.

In multi-class races, the broadcast director should:

Primarily cover the leading class unless dramatic action is happening in another class
Show class interactions when faster cars are lapping slower ones
Maintain awareness of the battle for the lead in each class
Use split screens or alternating coverage for simultaneous class battles

Track Characteristics

Different track types require different broadcast approaches:

Road Course: Left and right turns, elevation changes, chicanes. Use a variety of camera angles. Key corners deserve extended coverage during battles.
Oval: Left turns only (in most cases). Pack racing creates constant battles. Emphasize closing gaps, runs up high/low, and pit strategy.
Street Circuit: Narrow tracks with walls. Incidents are common. Keep cameras ready on tight corners. Overtaking is difficult, making every pass dramatic.
Endurance Circuit: Long tracks like the Nurburgring Nordschleife. Coverage must anticipate where action will be based on sector times.

2. Race Flags and Procedures

Flags are critical broadcast triggers. Each flag state should prompt specific camera behavior.

Flag States

Green Flag

Meaning: Racing conditions, track is clear
Broadcast response: Normal coverage pattern -- follow the narrative (battles, leaders, strategies)
Camera selection: Full variety of angles and drivers
Priority: Follow the most interesting action

Yellow Flag / Caution (Full Course)

Meaning: Incident on track, safety vehicles deployed, no passing allowed
Broadcast response: IMMEDIATELY show the incident that caused the caution
Camera selection:
1. First: Show the incident (if cameras are available at that location)
2. Second: Show safety vehicles entering the track
3. Third: Show the field packing up behind the pace car
4. During extended caution: Show pit stops, strategy calls, damage assessment
Duration: Hold on the incident for at least 10-15 seconds before cutting away
Priority: CRITICAL -- cautions are the most dramatic moments in oval racing

Yellow Flag (Local / Sector)

Meaning: Incident in a specific track sector, drivers must slow in that sector
Broadcast response: Show the sector incident briefly, then return to racing action elsewhere
Camera selection: Local cameras near the incident, then back to racing
Priority: HIGH but don't abandon other developing storylines

Red Flag

Meaning: Session stopped, all cars must stop on track or return to pit lane
Broadcast response: Show the incident causing the red flag, then show the field stopping
Camera selection: Incident cameras, then wide shots of the stopped field
Priority: CRITICAL -- this is the most serious flag condition

White Flag

Meaning: One lap remaining (in oval racing) or slow vehicle on track (road racing)
Broadcast response: Build intensity -- focus on the leaders and any battles that could decide the outcome
Camera selection: Close-up on the leader, alternating with the closest challenger
Priority: HIGH -- the climax of the race

Checkered Flag

Meaning: Race over, winner crosses the finish line
Broadcast response: Show the winner crossing the line, then their celebration
Camera selection:
1. Head-on or TV1 shot as winner approaches finish
2. Close-up cockpit or chase cam of the winner
3. Wide scenic shot if the margin was large
4. Then show the rest of the top finishers
Priority: CRITICAL -- this is the defining moment

Black Flag

Meaning: Penalty for a specific driver (speeding in pit lane, causing an incident, etc.)
Broadcast response: Show the penalized driver if convenient, mention the penalty
Camera selection: Brief shot of the affected driver's car
Priority: NORMAL -- informational, not dramatic unless it affects the lead battle

Meatball Flag (Black with Orange Circle)

Meaning: Mechanical failure or damage requiring a pit stop for the flagged driver
Broadcast response: Show the damaged car, especially if visible mechanical issues
Camera selection: External cameras to show damage, then cockpit for driver reaction
Priority: NORMAL to HIGH depending on driver's position

Restart Procedures

Restarts after caution periods are high-action moments:

Single File Restart: Cars line up in one column. Less dramatic but still important for position changes.
Double File Restart: Cars line up two-wide. Creates dramatic side-by-side racing into turn 1.
Rolling Start: Field accelerates from behind pace car. Camera should be positioned to show the leader's decision to go.

Broadcast approach for restarts:

5 laps before restart: Show the field packing up, highlight key battles about to resume
Pace lap: Show close-ups of key drivers (leader, contenders, damaged cars that stayed out)
Green flag drop: WIDE shot to capture the full field acceleration, then immediately cut to the first corner
First 2-3 laps after restart: Rapid camera changes to capture position changes, stay with any battles

3. Camera Groups

iRacing provides several camera group types that the broadcast director can select from. Each has specific characteristics and ideal use cases.

TV1 (Television Static - Close)

Type: Fixed trackside camera, close to the track
Best for: Close-up shots of individual cars, showing detail and speed
When to use: Following a specific driver through a key section, showing a battle at a particular corner
Duration: 3-8 seconds per shot
Notes: The workhorse camera for broadcast. Use frequently but vary the positions.

TV2 (Television Static - Medium)

Type: Fixed trackside camera, medium distance
Best for: Showing 2-3 cars together, capturing overtakes, showing racing line through a corner
When to use: Battles between cars, showing the racing line, establishing the pace
Duration: 5-12 seconds per shot
Notes: Good for showing the relationship between battling cars.

TV3 (Television Static - Wide)

Type: Fixed trackside camera, wide angle
Best for: Showing large groups of cars (pack racing, starts, restarts), establishing shots
When to use: Race starts, restarts, pack racing, field spread after incidents
Duration: 3-10 seconds per shot
Notes: Essential for showing the big picture. Don't stay on wide shots too long -- cut to closer angles for detail.

Cockpit Camera

Type: Inside the car, driver's perspective
Best for: High-speed immersion, showing driver workload, tense moments
When to use: Sparingly for dramatic effect -- chasing the car ahead, navigating through traffic, key overtake from the attacking driver's perspective
Duration: 5-15 seconds per shot (longer is acceptable for immersion)
Notes: Very compelling but disorienting in large doses. Best as an accent camera.

Chase Camera

Type: Behind and above the car, third-person following view
Best for: Showing car liveries, following a specific driver, smooth tracking shots
When to use: When following a driver for an extended period, showing pit stops from behind, exit shots
Duration: 5-20 seconds per shot
Notes: The most comfortable "following" camera. Good default when tracking a specific driver.

Blimp / Helicopter Camera

Type: High overhead, looking down
Best for: Showing track layout, field spread, race strategy (pit window timing)
When to use: Opening shots, transitions between segments, showing the full field, endurance race strategy views
Duration: 3-8 seconds per shot
Notes: Great for establishing context but lacks the excitement of close cameras. Good transitional shot.

Scenic Camera

Type: Artistic camera placements (skyline, grandstand, distant landscape)
Best for: Beauty shots, showing the venue, creating atmosphere
When to use: Pre-race buildup, cooldown laps, transitions, replay embellishment
Duration: 3-6 seconds per shot
Notes: Use very sparingly during active racing. Good for pacing and atmosphere between intense segments.

Pit Lane Camera

Type: Fixed cameras along pit road
Best for: Pit stop coverage, showing crew work, strategy moments
When to use: When cars are pitting, especially during key strategy calls or the pit window in endurance races
Duration: Entire pit stop duration (typically 10-30 seconds)
Notes: Critical during endurance races. In sprint races, show pit stops that affect position battles.

4. Broadcast Directing Principles

Shot Pacing

The rhythm of camera changes is as important as the content. Poor pacing creates a disjointed viewing experience.

General Rules

Minimum hold time: 3 seconds. Never cut to a shot and leave before the viewer can process it.
Maximum static hold: 30 seconds on a single shot before the viewer loses engagement.
Ideal battle coverage: 8-15 second shots alternating between the two drivers.
Ideal leader spotlight: 15-25 seconds with the race leader before returning to other action.
Pace variety: Alternate between "active" segments (rapid cuts, close-ups, battles) and "breathing" segments (wide shots, scenic views, standings).

Sprint Race Pacing

Start: FAST (2-3 second cuts) during the opening lap chaos
Early race: MEDIUM (5-8 seconds) as the field settles
Mid race: RELAXED (8-15 seconds) with strategic focus
Late race: INCREASING (5-10 seconds) as the fight for position intensifies
Final lap: FAST (3-5 seconds) building to the finish

Endurance Race Pacing

Start: FAST (like sprint)
Hour 1: Similar to sprint
Mid-race stints: SLOW (15-30 seconds), emphasis on strategy, pit windows, tire degradation
Final hour: Build intensity, similar to late sprint
Final 10 minutes: Match sprint pacing

When to Cut

DO cut when:

A new battle develops (close gap detected)
An incident occurs (flag change)
The leader is about to be overtaken
A pit stop is happening for a contending driver
The current shot has held for > 20 seconds
There is nothing interesting happening in the current shot

DON'T cut when:

An overtake is in progress (let it develop)
A car is mid-corner in a dramatic moment
The current battle is still active and close
A driver is on a hot qualifying lap
The shot has been held for less than 3 seconds

Camera Selection Heuristics

For Battles

Start with TV2 showing both cars approaching a key corner
Cut to TV1 as they go through the corner wheel-to-wheel
Cut to chase cam of the attacking car if they are making a move
Cut to TV2/TV3 at the next corner to show the result

For the Leader

Use TV1 or TV2 to establish the leader's position
Cut to cockpit or chase for a personal moment
Show the gap to second place (TV3 wide showing both cars)
Move on after 15-20 seconds unless they are under pressure

For Incidents

If available: show the incident live from the nearest camera
If missed: switch to the incident location for the aftermath
Hold on the incident for 10-15 seconds
Show the effect on other drivers (traffic backed up, avoiding debris)
If significant: slow-motion replay from multiple angles

For Pit Stops

Switch to pit lane camera as the car enters pit road
Show the stop (stay until the car leaves)
If key battle: show the car rejoining and whether they maintained position
During green flag pit windows: alternate between pit action and track action

Narrative Priorities

The broadcast director should always serve the narrative. Different phases of the race have different stories:

Race Start: The charge to turn 1. Who got a good start? Who lost positions? Any contact?
Opening Laps: The field sorting itself out. Early battles, aggressive moves, drivers establishing themselves.
Mid-Race: Tire management, fuel strategy, evolving battles. Show the chess match, not just the action.
Pit Windows: Who pits first? Undercuts and overcuts. Track position changes happening in the pits.
Late Race: Tires falling off, desperation moves. Gaps closing. The sprint to the finish.
Final Lap: All focus on the battles that determine the result. Show the finish.
Post-Race: Winner's celebration, final results, key moments replay.

Camera Variety

Avoid showing the same camera type or driver repeatedly:

Don't use the same camera group more than 3 times consecutively
Rotate through at least 4 different drivers every 2 minutes (in multi-driver sessions)
Mix static cameras (TV1/TV2/TV3) with dynamic cameras (cockpit/chase) in a 3:1 ratio
Use blimp/scenic cameras as transitions, not primary coverage
In multi-class races, ensure each class gets proportional coverage

Multi-Driver Coverage Fairness

In multi-driver broadcasts, ensure balanced coverage:

Track "time on screen" for each driver
No single driver should have more than 3x the average screen time (unless they are the race leader or in a crucial battle)
Prioritize drivers involved in battles, but cycle through the field during quiet periods
If a driver has had no coverage in 5 minutes, make them a priority for the next "breathing" segment

5. Telemetry Interpretation

The AI Director receives live telemetry and must interpret it to make broadcast decisions.

Gap Analysis

Battle threshold: Drivers within 1.0 second are "in a battle" -- prioritize coverage
Close racing: Drivers within 2.0 seconds are "close" -- monitor for potential battles
Comfortable gap: > 3.0 seconds -- the leading driver has some breathing room
Breakaway: > 10.0 seconds -- not competitive, use for variety only
Lap down: When a driver is lapped, show the interaction briefly (especially in multi-class)

Lap Time Analysis

Fastest lap: Always worth a mention/camera shot when a new fastest lap is set
Degradation: If a driver's lap times are consistently increasing, they may be about to pit or struggling with tires
Improvement: If a faster driver is catching a slower one, anticipate the upcoming battle
Sector times: Identify which track sections favor which drivers to predict where overtakes might happen

Incident Detection

Sudden speed drop: A car going significantly slower than expected may have had contact or mechanical issues
Off-track excursion: Car leaving the track boundary
Spin/Recovery: Detected by rapid heading change
Contact: Two cars converging to the same position simultaneously

Session Context

Track temperature: Affects tire degradation and therefore race strategy
Time of day: Affects visibility and track conditions (especially for night races)
Weather: If dynamic weather is enabled, rain can completely change the race
Fuel load: In endurance races, fuel management is a key strategic element

6. Sequence Generation Guidelines

When generating broadcast sequences for iRacing events, follow these principles:

Template Design

Each template should serve a specific narrative purpose (battle coverage, leader spotlight, field overview, incident response)
Templates should be parameterized with variables for driver names, camera groups, and durations
Variable sources should match what is available in the live telemetry context
Duration ranges should reflect the appropriate pacing for the template type

Step Construction

Each step should use a valid intent from the Director's capability catalog
Steps should flow logically (don't jump between unrelated cameras without a transition)
Include appropriate hold/delay steps between camera changes
Consider what the viewer sees during transitions

Variable Binding

Driver names should bind to actual drivers in the session (from telemetry leaderboard)
Camera groups should bind to groups confirmed available by the Director
Durations should fall within the generation parameter bounds
Context-sourced variables should reference valid telemetry paths

Priority Assignment

incident: Race-defining moments (final lap, restart, major incident) -- highest priority, interrupts current sequence
caution: Full-course caution periods, flag changes, safety car deployment -- should be shown soon
normal: Regular race coverage, leader updates, field overviews, battles, pit stops -- standard rotation

Output Format

The Executor must return valid JSON matching the PortableSequence schema:

All step IDs must be unique
All intents must be from the available capability set
All variable references in payloads must be resolved to concrete values
Duration must be within the specified min/max range
The metadata.source field must be "ai-director"
The metadata.templateId field must reference the selected template