Capture and browser live view
DJI Goggles 3 USB capture, clean H.264 path, WebRTC visitor view, and password-protected owner console.
Product status
Available features, remaining validation, planned work, and research are listed separately. Dates and compatibility are not estimated.
Implemented and supported by code plus host or device evidence.
DJI Goggles 3 USB capture, clean H.264 path, WebRTC visitor view, and password-protected owner console.
Auto/manual recording, thumbnails, playback, fast-start finalization, download, and confirmed per-file deletion.
Requester, note, In/Out values, existing-request segments, pending/approved/done states, deletion, and outstanding CSV export.
WebRTC, HLS, RTSP, RTMP/RTMPS, SRT, MPEG-TS, independent publishers, reconnects, and an RTMP-compatible silent AAC track.
Separate hardware-encoded output, 1080p/720p, Fit/Fill/Crop, bitrate control, logo, lower-third, timecode, and live proof.
One owner image or video for the browser and HDMI monitor, browser message placement, Cover/Contain, and time since the last picture. HDMI video looping was physically verified.
First owner account, Argon2id credentials, owner Wi-Fi settings, country selection, an offline licence that binds on first activation, and no default admin.
The free MIT-licensed desktop app imports folders and Streamer shot lists, trims per file, queues horizontal and vertical variants, and runs the local Gyroflow CLI. Version 0.2.0 passes 142 tests, typecheck, build, and real DJI/Gyroflow export checks.
The software exists. Each item names the observation that keeps it out of the completed column.
Request payloads, drag controls, and the existing-request lane are built. The owner still needs to observe and approve the drag and request-selection behavior on screen.
One project per outstanding proxy request, the related shot list, and bundled instructions are implemented and format-tested. The current product branch still needs its device walk-through.
Real hardware recorded 918 samples from a 15.8-minute flight, including ELRS readings and 723 GPS fixes. Timeline, Signal, Attitude, and Flight path views are implemented and fixture-tested. Position freshness and altitude remain named limits, so no dependable map claim is made.
Off, Open, and Invited access per capability, local invitation codes, code revocation, guest-device removal, and restart recovery choices are implemented and test-covered. Guest footage review and live clip requests are separate planned work.
Scan, join, leave, reachability reporting, and channel-safety behavior are implemented and test-covered. A clean customer-image rebuild and physical Wi-Fi test remain after the missing package fix.
The writer, rolling index, memory-backed ring, console controls, off-by-default behavior, and honest status copy are built. Turning a buffered moment into a permanent saved clip is not built.
Each destination can choose Branded or Pilot feed and can start the shared broadcast branch automatically. The end-to-end branded picture has not yet been watched at a real destination from the current Pi build.
Player, still/video idle screen, display identity, and presets exist; video standby is monitor-verified. The final live-feed hardware branch must still be checked.
Unbound keys, first-activation binding, durable records, batch minting, idempotent claims, webhook handling, revocation records, audit history, and an owner command-line tool exist. The buyer checkout and delivery path remain unfinished.
20%, 10%, 5%, safety-floor pause, refusal, delete, and resume logic are host-tested. The complete physical fill-disk exercise remains.
The forced owner/Wi-Fi wizard is implemented. Written legal sign-off must decide whether setup networking ships with the documented setup password or open.
The first image builds, passes 141 clone-safety checks twice, and boots on a different Pi 4 with the hardened network boundary verified. The Wi-Fi-fixed rebuild, storage expansion, clear AP diagnostics, region settings, capture, licence, and recovery remain release gates.
The current Windows installer is built, installed, and locally verified. Public hosting and the macOS release package still need to be completed. The app remains free and has no activation key.
Recorded product direction or backlog. These controls are not available to customers today.
A guest-safe link where a client can browse footage and submit timecoded requests without the owner console.
Resolve each proxy request to the correct O3/O4 memory-card file and exact offset without modifying the source media.
Rework input decoding so DJI Camera View Recording at 1080p60 can coexist with the framed and branded broadcast output.
Add selected, proven flight data to the separate branded branch without changing the clean pilot path.
Finish delivery transport, boot recovery, release signing, and the filesystem work needed to survive field power loss.
Connect the buyer-facing checkout, PayPal availability, software download, email delivery, recovery, and owner administration to the fulfilment core.
Desired directions with an unresolved technical or product choice.
Measure clock accuracy, map O3/O4 filenames and segments, handle boundaries, and prove reliable proxy-to-original offsets.
Auto-detect an Ethernet viewer router, preserve Pi-AP fallback, name the supported router model, and verify final radio behavior.
Bridge multiple Cosmik units, assign pilot identity, pull named streams, and compose a production multiview. The current Fleet page is groundwork only.
The owner intends to support more camera systems. No additional system has been selected or tested, so the roadmap does not name one yet.
Wi-Fi Share Liveview, RTSP/ONVIF/UVC sources, and secondary picture-in-picture remain possibilities that require an input-by-input architecture and hardware proof.
A browser-hosted configurator cannot reach a flight controller attached to the Pi through ordinary WebSerial. A proven Pi-side bridge would be required.
Deliberate exclusions
Order and evidence gates are recorded. Delivery dates have not been guessed.
Future compatibility does not become a product claim until a system is chosen and tested.
A page or database shape is not a working multi-unit product.
The current GyroFlow bundle carries exact proxy ranges; it does not yet identify the matching gyro-enabled drone original.
$29.99 USD is the decided launch price, not an open checkout or completed international sales clearance.
The customer-facing current state
The documentation wiki is generated from the product’s customer guides and includes the actual setup, media, output, power, and troubleshooting steps.