Race live stream preflight checklist: what to test before green flag

A race live stream can be set up correctly and still not be ready for the first session.

The camera may have the right RTMP URL. The Stream Event may be scheduled. The overlay may look fine in the portal. Then the car rolls to grid and you find out the SIM has no data, the microphone is all wind noise, the camera is aimed at the dashboard, or nobody on the team is watching the stream health while the driver is strapped in.

This race live stream checklist is not about choosing every piece of gear. If you are still building the system, start with our guide to building a reliable race car live streaming setup. This checklist is for the next step: testing the stream like you would test the car before a session, so the broadcast has a much better chance of surviving the race weekend.

A good setup still needs a real test

Live streaming problems usually show up when the environment changes. Home Wi-Fi is different from paddock cellular coverage. A camera sitting on a workbench is different from a camera hard-mounted in a vibrating race car. A test with no audience is different from a public stream where friends, family, sponsors, and crew are trying to watch.

That is why the goal of a preflight test is not just to see video once. The goal is to prove the full chain: camera, power, network, MyRaces.Live Stream Event, overlay, race data, destination, viewer link, and the person who will monitor it while everyone else is busy racing.

48 hours before the event: confirm the basics

Do this before you load the trailer if you can. Race weekends have a way of turning small setup jobs into stressful last-minute jobs.

• Create or confirm the Stream Event with the correct start and stop time.

• Check the racing team, driver, car number, and race data source.

• Set the visibility you actually want: public, unlisted, or private.

• Confirm any YouTube or custom RTMP destination is ready and connected to the right Stream Event.

• Make sure the SIM card is active, has data, and is not locked by a PIN.

• Charge the camera, external battery, hotspot, and anything else the stream depends on.

• Make sure at least one crew member has portal access and knows what they are allowed to change.

This is also the time to check anything that needs approval or a waiting period. If you are using your own YouTube channel, live streaming must already be enabled. If you are using a custom destination, do not wait until race morning to discover that the stream key was copied from the wrong place.

At the track: test from the paddock, not just from home

A successful home test is useful, but it does not prove the race weekend stream will work. The network at the track is the real test. Cellular coverage can be good in the paddock, weak near the grid, and terrible on the far side of the circuit.

When you arrive, run a short test from the paddock with the same camera, SIM, antenna, and stream settings you plan to use during the event. If the upload is struggling, lower the resolution or bitrate before the first session. A stable 720p stream is usually more useful than a 1080p stream that drops every lap.

If you are using a MineA5, check the signal bars, data-service indicator, and 4G LED. If the signal does not improve after connecting the antenna, make sure the SIM slot and SMA connector match. On some units, the connector position is not obvious until you check the signal strength.

In the car: check what racing shakes loose

The camera may work perfectly in your hand and still fail once it is mounted in the car. Before the session, check the physical setup like you would check a safety item.

• Camera mount tight enough that it cannot rotate or slide under vibration.

• Lens clean, especially after dusty sessions or open cockpit running.

• Camera aimed at the track, not mostly dashboard or roof.

• Video orientation correct if the camera is mounted upside down.

• Power cable secured so it cannot pull out during a driver change or heavy curb strike.

• Microphone placed away from direct wind if you are using an external mic.

• Auto-stream or stream-on-power-on tested if that is part of your workflow.

This is the boring part, which is exactly why it matters. Loose mounts, dirty lenses, bad audio, and dead power are not exciting technical problems. They are simple problems that can ruin the whole broadcast.

In MyRaces.Live: confirm the stream is really being received

Once the camera is sending video, do not stop at the camera screen. Open the Stream Event in MyRaces.Live and confirm the platform is actually receiving the feed.

• The Stream Event infrastructure should show ready before you start pushing video.

• The camera input should appear in stream health after a short delay.

• The video preview should show the correct camera angle.

• The overlay should show the correct team, driver, car number, session, and race data if you selected a timing source.

• Sponsor logos or custom overlay elements should be readable and not covering the important part of the onboard view.

Overlays are not decoration. They turn a raw onboard camera feed into a race stream viewers can understand. Timing, driver, car, sponsor, session, lap, position, and event context all help people follow what is happening, especially if they join in the middle of a race.

On the viewing page: check what the audience sees

The encoder can say it is live and the dashboard can look healthy, but you still need to open the viewer link. Use a phone or laptop that is not logged into the admin account if possible. That is the closest version of what friends, family, sponsors, and fans will see.

• Confirm the stream is visible to the right audience.

• Listen to the audio for wind noise, clipping, or silence.

• Check that the overlay is readable on a phone screen, not just on a large monitor.

• Make sure the destination is the one you intended, especially if you are restreaming to your own YouTube, Twitch, Facebook, or Instagram account.

• Know what latency to expect so nobody thinks the stream is broken just because it is 15 to 20 seconds behind real time.

If the stream is public, this is also a good moment to check the title and description. A viewer should know what race, car, team, or session they are watching without having to guess.

Assign a stream spotter before the driver gets in the car

Once the driver is in the car, they are not fixing the stream. They are racing. Give the stream to someone else on the team.

The stream spotter does not need to be a broadcast engineer. They just need to know where to look and what to report. Ask them to keep the viewer page and the Stream Event open, especially during the first laps, driver changes, and restarts.

• If the video stops, they can tell the crew before viewers start messaging everyone.

• If the current driver changes, they can update the driver in the portal.

• If the race data source changes, they can update the Race Event source.

• If the car is in the paddock or between sessions, they can pause the stream and show a useful message instead of leaving viewers staring at nothing.

For endurance races, this role matters even more. The stream is not just video. It is also the story of who is in the car, what lap they are on, where they are in the session, and what is happening next.

The five-minute race live stream checklist

Right before the car heads out, run one last quick check. This should be short enough that someone will actually do it.

• Camera powered on.

• Stream started, or auto-stream confirmed if you use stream-on-power-on.

• Stream Event ready and active.

• Camera feed received in MyRaces.Live.

• Overlay readable and showing the correct driver, car, and race context.

• Stream spotter assigned and watching.

If something fails, check these first

Do not start by changing ten things at once. Work through the most likely failure point.

• No video in MyRaces.Live: check the RTMP URL, the /cam1 ending, stream key field, and Stream Event infrastructure status.

• Weak or unstable stream: check SIM data, antenna, APN, signal strength, bitrate, and where the car is parked.

• Stream stops suddenly: check power, overheating, loose cables, platform auto-stop settings, and whether the camera is still pushing video.

• Wrong overlay information: check the selected team, driver, car number, race data source, and custom overlay.

• Viewers cannot watch: check visibility, destination, stream start time, and whether you shared the correct link.

The best time to find these problems is before the car leaves the paddock. The second-best time is before green flag. After that, you are just troubleshooting under pressure.

Make the checklist part of the race weekend routine

Most teams already have a routine for fuel, tires, radios, transponders, and torque checks. Add the stream to that routine. It does not need to be complicated. It just needs to happen every time.

When the checklist becomes normal, live streaming stops being a mystery project someone remembers at the last minute. It becomes one more race weekend system that gets tested, assigned, monitored, and improved.

That is the real goal: give your viewers a stream they can follow, give your sponsors a cleaner broadcast, and give your team one less thing to panic about while the car is already on grid.