๐Ÿš€ Getting Started

RaceLive is an AI-powered live video platform built specifically for endurance events โ€” 5Ks, marathons, triathlons, and everything in between. Race directors use RaceLive to broadcast every participant live using smartphones as cameras. Our AI reads bib numbers in real time, switches between camera feeds automatically, and gives every athlete a personalized live stream their family and friends can watch from anywhere.

Creating an event takes under 10 minutes:

  • Sign up for a RaceLive account at racelive.net
  • Click New Event in your dashboard
  • Enter the event name, sport type, date, time, and venue
  • Choose the number of cameras (1โ€“4) and whether to enable bib tracking
  • Complete payment to confirm

Once created, your event dashboard provides RTMP URLs and stream keys to share with your volunteers, plus a public link for fans.

RaceLive uses per-event pricing โ€” you only pay when you run an event. The price scales based on your event type (sport), the number of cameras, the number of registered participants (if bib tracking is enabled), and any applicable discounts. There is no monthly subscription and no hardware to purchase. Full pricing is calculated and shown at checkout when you configure your event.

๐Ÿ“ฑ Equipment & Volunteers

Just a smartphone with good cellular coverage โ€” iOS or Android, any modern device released in the last 3โ€“4 years will work fine. No dedicated cameras, encoders, or hardware purchases required. Volunteers also need a streaming app (see below) and a mount to keep the phone stable.

One volunteer per camera location. The number of cameras you can add depends on your event type โ€” longer, larger events support more cameras. For most 5K/10K events, 2 cameras (start and finish) is sufficient. Longer courses like half marathons and marathons benefit from additional cameras at key mile markers and course turns.

Any RTMP-capable mobile streaming app works. We recommend:

  • Larix Broadcaster (iOS & Android) โ€” free, easy to configure
  • Streamlabs Mobile (iOS & Android) โ€” popular with good stability
  • OBS Mobile (Android) โ€” advanced controls

Your event dashboard provides the RTMP URL and stream key for each camera. Copy these directly into your chosen app's stream settings.

Minimum: 5 Mbps upload sustained per camera. We recommend 10+ Mbps for reliable 1080p streaming. Test upload speed at each camera location using Speedtest.net at least one day before the event. LTE/4G on major carriers typically provides 10โ€“50 Mbps upload in open areas. Avoid locations where buildings or terrain block the cell signal.

โšก Event Lifecycle

Infrastructure (streaming channels, AI processing pipeline) spins up automatically 1 hour before your scheduled event start time. You'll receive a notification when it's ready. You can also spin it up manually at any time from your event dashboard by clicking Start Infrastructure โ€” useful if you want to run a test stream the evening before the event.

About 60โ€“90 seconds for the AWS MediaLive pipeline to start up. Your Live Monitor page updates in real time โ€” you'll see each camera's status go from Idle to Running as the stream channels activate. Once running, volunteers can start streaming from their phones and viewers will see the feed immediately.

You can end the event manually from the Live Monitor page by clicking End Event. Infrastructure is torn down within a few minutes. If you don't end it manually, the system automatically shuts everything down at the calculated end time based on the event's scheduled duration.

The infrastructure is automatically stopped after the event's scheduled duration has elapsed from the start time. For example, a 3-hour event scheduled for 8:00 AM will be force-shut down at 11:00 AM โ€” regardless of whether cameras are still streaming. This prevents runaway charges. If your event runs long, you can extend it manually from the dashboard before the cutoff.

Recordings are processed within 1โ€“2 hours of the event ending and then available for 90 days. After 90 days, recordings are archived to cold storage. You can download MP4 recordings from your event dashboard before they are archived. Archived recordings can be restored on request (additional fee may apply).

๐Ÿค– AI Features

The AI camera switcher monitors all active camera feeds simultaneously. Every few seconds it scores each camera based on scene activity (athletes in frame, motion, engagement potential) and bib detection events. It then switches the broadcast feed to the camera with the highest engagement score. Cameras that are offline or not streaming are excluded from the rotation entirely, ensuring viewers always see an active feed.

Bib tracking is an optional add-on that uses AI computer vision to read race bib numbers from the live camera feeds in real time. When a bib number is detected, it's logged with a timestamp and camera ID. On the viewer-facing live stream page, spectators can enter one or more bib numbers to track โ€” they'll see a live feed of every time those athletes appear on camera, complete with a timeline of sightings. This is especially popular for family members who want to follow a specific runner without watching the entire broadcast.

Under ideal conditions โ€” stable camera, waist-to-chest camera height, good lighting, athletes facing the camera โ€” accuracy exceeds 99%. Detection quality drops in backlit conditions (sun behind athletes), when bibs are partially obscured, or when athletes are moving very fast and close to the camera. The system assigns a confidence score to each detection; low-confidence detections are filtered out to minimize false positives. Camera placement significantly affects accuracy โ€” see our Best Practices guide for optimal setup.

๐Ÿ”ง Troubleshooting

Infrastructure spin-up normally completes within 2โ€“3 minutes. If it is still showing "spinning up" after 5 minutes:

  • Refresh the Live Monitor page โ€” it polls every 5 seconds during spin-up
  • Check that your AWS region has available MediaLive capacity (rare during peak periods)
  • Try stopping and restarting the infrastructure using the Stop Infrastructure then Start Infrastructure buttons on the dashboard
  • If the problem persists, contact support โ€” include your event ID from the URL

When a camera drops mid-event:

  • On the volunteer's phone: stop and immediately restart the streaming app using the same RTMP URL and stream key
  • The IVS channel will reconnect within 10โ€“15 seconds of the stream restarting
  • The camera status on your Live Monitor will update automatically
  • No configuration changes are needed โ€” the stream key is persistent for the duration of the event

Common causes: phone screen locked (disable auto-lock before streaming), app crashed, cellular handoff between towers. Plugging into power and using Do Not Disturb mode prevents most disconnections.

If viewers report a blank or buffering player:

  • Infrastructure not started: Confirm the event status is "Live" on your dashboard, not "Spinning Up"
  • No active cameras: At least one camera must be actively streaming for the feed to work. Check the Live Monitor for green camera indicators
  • Browser compatibility: The IVS player requires a modern browser (Chrome, Safari, Edge, Firefox โ€” all recent versions). Older Android WebViews may not support it
  • Corporate firewalls: Some corporate networks block streaming ports. Ask viewers to try from a personal network or mobile data
  • Share the correct URL: Use the public event URL from the event detail page, not the dashboard URL (which requires login)

Still have questions?

Our team is happy to help you set up your first event or troubleshoot any issues.

Get Started Today