Voice comms, recording, and streaming

Most experienced iRacing drivers mute public-session voice chat entirely and run CrewChief for spotter calls instead. Comments from racers with six years and thousands of laps are blunt: “not for a single race did I have voice chat on.” Public voice is where you’ll hear the abuse; the useful audio comes from spotter apps and, in leagues, a private Discord. Here is the full setup for talking, recording, and broadcasting.

Voice comms in a race

iRacing’s built-in voice — and why most people mute it

iRacing ships voice chat built into the sim: one channel per session, push-to-talk by default. The problem is the public field. A single bad race teaches most people to turn it off, and they never turn it back on. Open it for the spotter callouts and you also open it to whoever wants to argue about a corner. Mute it, run a spotter app for proximity calls, and you lose almost nothing.

Push-to-talk and what gets you protested

You can protest voice abuse, and iRacing acts on it. Slurs, threats, and repeated aggression draw chat bans or account-level action; the offense is reportable, so report it rather than arguing back. Keep push-to-talk on so you’re not broadcasting wheel rumble, pedal clack, and keyboard noise across the field.

League comms on Discord

Leagues run comms on Discord, push-to-talk, separate from iRacing’s channel. Push-to-talk is the etiquette default for the same reason: an open mic in a 24-driver server is noise. The Discord in-game overlay can conflict with iRacing and cause a black screen on alt-tab — if the game gets unstable, disable Discord’s in-game overlay first.

Spotter and engineer apps (CrewChief vs native)

iRacing’s native spotter is genuinely good — real-time proximity and positional calls at low latency, often faster and more accurate than third-party tools. CrewChief V4 is free and adds the engineer on top of the spotter: fuel calculation, pace deltas, “car left,” “three wide,” flag and incident calls, across iRacing, ACC, AMS2, and rFactor 2. Community voice packs exist (Kyle Larson, Bubba Wallace / Freddie Kraft) if you want a named spotter for immersion. Plenty of drivers run both — native for the fast proximity calls, CrewChief for fuel and deltas. CrewChief sits alongside the rest of the common iRacing stack: Garage 61, Race Labs, Trading Paints for paint downloads, and SimHub for dashboards and bass shakers.

Recording your races

The iRacing replay system (free, already running)

Every session is auto-saved to a replay you can scrub, rewind, and watch from multiple cameras — including a “free aim” free-look camera that points anywhere you want. To re-record a moment, load the saved replay, play it back, and capture it. The replay re-runs physics and renders the scene, so it costs GPU like live driving; you’re not pulling a pre-rendered video out of it.

ShadowPlay / NVIDIA app vs OBS local recording

NVIDIA’s app (formerly ShadowPlay, the “Instant Replay” feature) is the path of least resistance: GPU NVENC encode, near-zero performance hit, alt+Z to open. Racers call it “flawless” for capturing replays at 1440p. OBS gives you the same NVENC H.264/HEVC encoder with more control over bitrate, scenes, and overlays if you want them. For raw clips with no editing, the NVIDIA app wins on simplicity.

Making a race film

iRacing Replay Director is a third-party app that builds a scripted multi-camera timeline — you choose camera and driver per moment and it auto-cycles for broadcast-style edits. Combine it with the free aim camera for cinematic angles. When you cut clips, re-encode in HandBrake with H.265 NVENC at CQP ~25-30 rather than rendering short clips at full 1440p quality; the file shrinks hard with no visible loss.

Streaming to Twitch or YouTube

OBS settings that matter

Twitch caps affiliates at 6000 kbps video (Partners can request up to ~8500 through support). Run 1080p60, NVENC H.264, preset P5 or P6 (Quality), keyframe interval 2s, CBR. Add ~160 kbps audio for ~6160 kbps total. Honor the 75% rule — keep stream bitrate under 75% of your upload speed, so a 6 Mbps upload realistically tops out near 4500 kbps. YouTube allows much higher bitrates and 1440p/4K at 9000+ kbps, so it’s the better target if you want archive quality over Twitch’s live audience.

Single PC vs second-PC + capture card

Modern NVENC offloads encoding to the GPU’s dedicated encode block, so CPU usage stays single-digit even while streaming. The catch is the GPU itself: a 3070 driving triple 1440p — about 11 million pixels — already lives on the edge once you stack mirrors, shadows, and traffic, and the stream pushes it over. iRacing only runs on one PC anyway, so a second PC with a capture card handles OBS and overlays and removes the encode load from the gaming rig entirely.

Overlays and the black-screen problem

Overlays from Discord and the NVIDIA app can fight the game and produce a black screen on the stream while the game still runs. Check Task Manager to confirm the game process is alive, then disable in-game overlays one at a time. If OBS itself black-screens a captured game, switch the capture from hardware to software encode.