TeslaCam can capture a remarkable amount of useful footage. Reviewing it should not require handing that footage, your driving history, or your location to somebody else's cloud.
That idea is the reason I built Cammetry, a free and open-source desktop viewer, telemetry explorer, and video exporter for TeslaCam recordings. It runs on your own computer, reads the folders you choose, and keeps its core workflow local.
Cammetry reads vehicle telemetry. It does not send application telemetry.
There is no Tesla login, no background analytics, no anonymous usage tracking, no advertising tracker, and no sale of usage data. Your videos and GPS data stay on your computer unless you deliberately use an optional network feature.
Four or Six synchronized cameras, locally decoded telemetry, an offline route, a searchable event list, and one shared timeline. The street-level location has been removed from this screenshot.
One place to review the whole event
Cammetry understands normal TeslaCam folder structures and can browse Recent, Saved, and Sentry clips. It groups matching camera files by timestamp, reads event metadata when it exists, detects mounted TeslaCam drives when possible, and gives you search, trigger filters, calendar views, and quick event navigation.
Playback stays synchronized across as many as six supported cameras, including front, rear, repeaters, and compatible HW4/AI4 pillar footage. You can let the adaptive layout follow the cameras actually present, switch to a single-, four-, or six-camera view, use the visual Vehicle View camera map, select Fit or Fill, zoom, change playback speed, jump through footage, save a snapshot, and set trim points on the shared timeline.
Ordinary footage still works when a clip has no embedded telemetry. When compatible MP4 metadata is present, Cammetry can decode speed, gear, steering, accelerator, brake, turn signals, heading, acceleration, GPS, and available driver-assistance states. It turns that into a synchronized dashboard, route, timeline, clip insights, and an optional CSV export. Availability naturally depends on the vehicle, firmware, recording state, and what the file actually contains.
Local-first is the default, not a slogan
Playback, camera synchronization, telemetry decoding, snapshots, CSV creation, privacy blurring, route visualization, and video export all happen locally. The default route view is an offline local grid, so even opening a GPS trace does not make a map-server request.
Network features are separated from the core application and require an intentional choice. An optional OpenStreetMap background requests map tiles only when selected. Update checks use GitHub Releases when configured. Temporary sharing needs a deliberately configured service and uploads only the export you choose. None of those features is required to view or export footage.
From raw cameras to a video worth sharing
The exporter can create single-, four-, and six-camera videos with Mobile, Medium, High, or Maximum quality presets. It validates available encoders before offering them and supports NVIDIA NVENC, Intel Quick Sync, AMD AMF, Apple VideoToolbox, and CPU x264 where the system and FFmpeg build allow it. If a hardware encoder fails, Cammetry can fall back to CPU rather than leaving you with a mysterious dead export.
The current build includes Full, Compact, and Minimal HUD styles, adjustable size, opacity, and placement, plus individual switches for speed, driver-assist state, gear, steering, accelerator, braking, blinkers, G-force, timestamp, GPS coordinates, and GPS minimap. You can apply exposure, contrast, saturation, and gamma adjustments without altering the source files, choose framing for single-camera exports, draw persistent privacy-blur zones, and keep working while export progress runs in a floating notification.
The finished export playing in VLC with Cammetry's HUD. I hid the route inset before publishing the screenshot—the kind of decision the app's privacy controls are meant to encourage.
Version 0.5.1 beta is ready to test
The latest Windows test build is Cammetry v0.5.1 Beta. The release page offers a normal installer, a single-file portable executable, and a portable ZIP. This is a public pre-1.0 beta, so preserve your original TeslaCam recordings and expect a few rough edges.
The Windows beta is currently unsigned while SignPath code-signing certification is pending, which means Microsoft SmartScreen may display a warning. The release page includes SHA-256 digests, and the complete source is available in the Cammetry GitHub repository. If you find a reproducible problem, please use GitHub Issues and include your Windows version, GPU, and encoder choice when relevant—without uploading private footage or GPS data unless you consciously decide to share it.
Cammetry is MIT-licensed, free forever, and has no paid edition, subscription, feature paywall, ads, or telemetry-selling model. The interface and export labels currently support 13 languages. It is independent software and is not affiliated with, endorsed by, sponsored by, or produced by Tesla, Inc.
If you have TeslaCam footage and a Windows 10 or 11 system, v0.5.1 is ready for real-world testing. I would especially like feedback on camera detection, playback behavior, telemetry compatibility, HUD readability, and hardware-accelerated export across different GPUs.
Comments
Post a Comment