Supported sources · RaceChrono
Your RaceChrono session, on your camera’s video.
RaceChrono times and logs; YouMetry puts that data on the picture from whichever camera you like, on a big screen, with every gauge placed where you want and the lap replayed in 3D.
What YouMetry reads
- RaceChrono CSV exports (formats 2 and 3) and .vbo.
- RaceChrono’s own laps and sectors, taken as they are: lap number, start/finish and split crossings.
- Speed, altitude, lateral and longitudinal acceleration, roll, satellite count and GPS accuracy.
- The OBD channels logged by RaceChrono: RPM, accelerator pedal, coolant temperature, gear.
- Session details — track, driver, date — available as text gauges.
How to do it
- In RaceChrono, export the session (or a single lap) as CSV or .vbo.
- Give the file the same name as the video and put both in the same folder: they will open together.
- Line the data up with the picture by dragging the file’s strip under the playback bar — a standing start or a hard braking point make good markers.
- Export the video, or a transparent layer for your editing software.
What you get
- Timer, current lap, last lap, delta to best lap, sector.
- A corner-by-corner table: minimum speed, braking speed, lateral G, lap after lap — and a “corner” gauge that shows it on screen.
- Rev counter, pedals, G-meter, track map, the lap replayed in 3D over terrain.
Good to know
- A 1 Hz phone GPS gives an angular track: YouMetry smooths it, but an external 10 Hz+ receiver changes everything — for RaceChrono and for the video alike.
- RaceChrono counts lateral acceleration as positive to the left; YouMetry converts it to its gauges’ convention, nothing for you to do.
- With no lap file, YouMetry can also detect laps by itself from a plain GPS track.
Questions
RaceChrono already exports video with data: why YouMetry?
To work on a computer with full-quality video from any camera, place each gauge freely, output a transparent layer for editing, and replay the lap in 3D over terrain.
Which export format should I choose in RaceChrono?
CSV (format 3) or .vbo: both are read, laps and sectors included.
See also
DJI drones and camerasSRT file or embedded telemetry: speed, altitude, flight in 3D.
FPV: Walksnail Avatar and blackboxThe goggles’ OSD and the Betaflight/INAV log: battery, sticks, true horizon.
GoProThe GPS and sensors already inside your MP4.
Insta360The remote’s GPS and the gyroscope inside the .insv file.
Lap Legend (Dauntless)Laps, G-forces and DauntlessOBD data, on the video.
Paragliding (free flight)Your vario’s IGC flight: vario, glide ratio, wing in 3D.
IGC fileFree flight’s own format: two altitudes, wind, air speed.
OBD-IIRPM, throttle, temperatures: the engine’s own data.
Dragy, VBOX and GarminThe .vbo, CSV and FIT files of performance meters.
Bike and e-bike (Bosch eBike Flow)Speed, power and cadence from the Bosch FIT; heart rate from a Garmin watch.
GPX trackWatch, phone, bike computer: any GPS track.
CarSpeed, G-force, OBD, lap timer and corner table.
MotorcycleLean angle, cornering speed, lap timer.
DroneAltitude, speed, battery and the flight replayed in 3D.
Bike and e-bikePower, cadence, heart rate and ride summary.
Hiking and runningHeart rate, pace, climb, figure over the 3D terrain.
Ski and snowboardSpeed, gradient, detected runs, skier in 3D.
SailingKnots, wind, point of sail, heeling sailboat in 3D.
The mobile app: lap timer, OBD, Android Auto
RaceRender alternative
DashWare alternative
Garmin VIRB Edit alternative
Several files can be combined in one project: position from one, engine data from another. See the comparison with other software.