Your AiM data, on your onboard video.
Paddock Pixel opens your AiM session, lines it up with your video, and renders speed, G forces, lap delta and a track map into the frame, plus the engine channels your AiM logs. It reads the Solo, Solo 2 and Solo 2 DL.
What it reads from your AiM.
Every session with GPS brings speed, G forces, altitude and the track map, and your laps come from your AiM’s own beacon markers. Engine and driver channels come through when your AiM logs them from the car:
Engine
Driver inputs
Chassis
Fuel & electrical
An XRK, CSV or DRK tag marks a channel that only comes from those files.
Bring the file you already have.
- .xrkOpens as is.Solo 2 DL
- .drkKeep the .gpk and .rrk from the same session in the same folder. The track map needs them.SoloSolo 2Solo 2 DL
- CSVExported from Race Studio.Race Studio
Three steps, then go drive.
-
Drop in your session and your video.
Your AiM file and the clip from your camera. GoPro chapters are joined for you.
-
Click Auto‑Sync.
With GPS on in your GoPro, an .xrk lines up on satellite time. Anything else matches on the camera’s motion, or on the picture itself: Mark’s footage above had no GPS or motion data in it, so it synced from the picture.
-
Pick your gauges and render.
Speed, RPM, gear, throttle, brake, steering, G forces, lap timer, lap delta and the track map. Each gauge shows up when your session has its data.
Straight answers for AiM owners.
Why doesn’t my .drk session show a track map?
Drop the matching .gpk and .rrk files into the same folder, then import it again. The track map needs them.
Will my lap times match my AiM?
Yes. Laps come from your logger’s own beacon markers, not from a line the app guesses at.
Which AiM loggers work?
The Solo, Solo 2 and Solo 2 DL. Running a different AiM? Send us a session file and let’s work together to support it.