Four vehicle cameras. One trip timeline.

Update 663.10 Changed What the Vehicle Could Do

A software update installed on July 28, 2026 added several visible camera features to the test vehicle. The release notes identify Surround Vision Recorder, which records, watches, and saves video from the vehicle's cameras; Security Recording, which can begin when the alarm is triggered while parked; and Cabin Glance, which shows a live view of the seating area.

A meaningful OTA feature expansion

The same installed camera hardware gained a recorder, parked-event capture, and an interior camera view through software. That is useful, but it is also a concrete reminder that connected vehicles can gain materially different sensing behavior after purchase.

The update also lists camera responsiveness and reliability fixes. ABSG's test footage came from a 2025 Chevrolet Tahoe Z71 after this update.

The USB Drive Is Useful. The Folder Is Not.

The vehicle writes separate H.264 MP4 files for each camera angle. In the footage ABSG examined, each camera produced a 1280 by 768, 30-frame-per-second clip approximately every five minutes. Four cameras recording one drive quickly become a folder full of similarly named segments rather than a coherent trip.

That is the problem GMSurroundVision Viewer & Exporter solves. It scans the selected folder, recognizes matching camera timestamps, assembles contiguous segments into trips, and gives the user one wall-clock timeline for the entire drive.

Review a Trip Instead of Managing Clips

The viewer keeps all four camera feeds frame-locked as playback crosses file boundaries. A user can move through the drive at normal speed or accelerate review up to 8x, hover over the timeline for thumbnails, and set in and out points around the moment that matters.

Export is handled by FFmpeg. The project can create a single-camera clip, all four independent angles, a quad grid, several production-oriented arrangements, picture-in-picture, or a stitched surround view. Exported footage goes to a separate folder and the source recordings remain untouched.

The Connected-Vehicle Question

This update demonstrates that software can unlock new uses for cameras already installed around and inside a vehicle. GM also documents that eligible vehicle software updates can arrive through the built-in data connection or Wi-Fi. It is therefore reasonable to ask what future updates could technically enable and what data paths exist behind the dashboard.

Could a future system transmit camera events through a connected-services channel? Could onboard vision identify plates, roadway objects, or recurring locations? Could a fleet of connected vehicles become a distributed sensor network? Modern hardware makes ideas like these technically conceivable. That does not make them confirmed behavior.

The right standard is transparency. Owners should be able to understand what is recorded, where it is stored, when it can leave the vehicle, how long it is retained, and which features require explicit consent. Useful connected features and privacy protections are not opposites; good engineering requires both.

Research Notes and Limits

The implementation details in this article come from the GMSurroundVision source repository and footage tested by ABSG. The update features are transcribed from the vehicle's 663.10 release note shown above. GM's official vehicle software update documentation explains how eligible OTA updates use a built-in data connection or Wi-Fi. The OnStar services consent describes categories of connected-vehicle data and should be reviewed alongside the terms applicable to a specific vehicle and account.

Other GM models may produce compatible footage, but ABSG has not verified every vehicle. Security Recording clips also need broader testing. The project is intentionally local-first so vehicle footage can be reviewed without sending it to another service.