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 shot-list export.
The Streamer reads the aircraft card, matches each marked shot to the aircraft's own recording, and writes the shot list and one GyroFlow project per request into its own folder on that card. Run end to end on real hardware to finished stabilized clips. The match lands within about five seconds; a frame-exact confirmation step is not built, and only DJI air-unit cards have been tested.
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.
Off, Open, and Invited access for watching and for flight data, local invitation codes, code revocation, guest-device removal, and restart recovery choices. Observed working on a laptop on the house network and on a phone joined to the Streamer's own Wi-Fi. Guest footage review and guest clip requests are separate planned work and cannot be handed out today.
The Streamer recognises the connected monitor, reports its native resolution, and restores the Fit, Fill, or Crop chosen for that exact screen, with a standby photo or looping video between feeds. Driven on a real monitor with the live picture.
Checkout, payment, and the licence email run end to end: a purchase delivers a key to the buyer's inbox, with a link that retrieves it again if the email is lost. The Streamer image is downloadable, the key binds to one Streamer on first activation, activation works with no internet, and a lost or shared key can be revoked. Behind it: batch minting, idempotent claims, durable records, and an append-only audit history.
The shipping image builds, passes 141 clone-safety checks twice, and has been written to a card and booted on a Pi 4 that had never run it: the Wi-Fi network appears on its own, the storage expands to fill the card, the licence activates, and the settings survive a reboot. Updates are signed and installed on the device.
The free MIT-licensed desktop app reads folders and Streamer shot lists, trims per file, queues horizontal and vertical variants, and runs the local Gyroflow CLI. Version 0.9.2, with its full test suite, typecheck, build, and real DJI/Gyroflow export checks passing.
The software exists. Each item names the observation that keeps it out of the completed column.
Every flight is written down once a second on its own, and four views read it: the route flown back in three dimensions, the shared timeline, the link in detail, and the aircraft's own attitude. The data is trusted enough that the Streamer uses it to match a marked shot to the aircraft's recording, which it has done on hardware. What remains is a measurement, not a feature — how smoothly the 3D view runs on a real phone over the Streamer's Wi-Fi, an owner review on hardware, and a check of the flat-map fallback with 3D switched off.
Scan, join, leave, reachability reporting, and channel-safety behaviour are implemented and test-covered. The join itself has never been run on a real Streamer, which is the gate.
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.
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 Windows installer is built, hosted, and downloadable today. The macOS package has not been built. The app is free and needs no key on either platform.
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.
The automatic match is built and lands within about five seconds. The remaining work is the step where the pilot nudges it onto the exact frame, and reading a card deeply enough to tell whether the aircraft already stabilized the footage itself.
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.
Signed updates are delivered and installed today. What remains is the part that only matters when things go wrong: recovering the boot if power is lost partway through an update.
A one-press button that keeps the picture on screen as a full-quality photo, including while reviewing a recording, without any of the surrounding interface in the shot.
Desired directions with an unresolved technical or product choice.
A named, reusable QR code for a place you fly often, that you switch on when you arrive and off when you leave, without setting up access from scratch each visit. It creates a saved credential that outlives a single session, so how it is revoked and what a photographed code can do have to be settled before it is built.
Action-camera and other cards have not been tested. Their file naming, segment behaviour, and whether a request that crosses two files can be resolved are all unproven.
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 bundle now names the aircraft's own file and the range on it, matched automatically. That match lands within about five seconds; the step where the pilot confirms it to the exact frame is not built.
$29.99 USD is settled and checkout is open at store.cosmikstreamer.com/buy, paid through PayPal. No customer has completed a purchase through it, and international sales clearance is not finished.
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.