Crew watches the live flight.
Guest or production browser. The optional HDMI live-picture path remains in Validation.
AvailableProduction workflow
From live flight to requested clips.
Give the crew a live picture, record the review copy, mark requested ranges, manage the queue, and move the job to the editing computer.
Current production loop: watch → record → mark → approve → export
Original-media automation: roadmap
Current interface
Review and mark the exact clip.
These are exact product captures, not redrawn screens. Select a stage to bring its working surface forward.
Workflow
Five production steps.
The proxy workflow and post bundle exist. Automatic matching to the gyro-enabled drone original does not.
The flight becomes a review copy.
Recording, thumbnail, playback, seeking, download, and local retention.
AvailableThe operator marks the shot.
Visual In/Out, requester, contact, note, queue status, and CSV export.
ValidationThe proxy mark finds the drone file.
Planned wall-clock correlation to the real SD original and its gyro data.
ResearchOutstanding requests become a post bundle.
One GyroFlow project per request, the shot list, and instructions. The current projects point to the proxy recording.
ValidationAfter the flight
Find the moment before opening the footage.
The Flight Log aligns uplink, downlink, picture, battery, and recording state. A flagged event can open the saved review copy at the same point, so production can inspect the cause without scrubbing the whole flight.
- 918samples recorded during one 15.8-minute hardware-validation flight.
- ELRSbackpack telemetry confirmed on the Raspberry Pi.
- GPS723 fixes recorded, but position freshness was not good enough for a dependable map claim.
- WATCHOpen the matching recording at a moment worth reviewing.
The selection
Drag the handles. Keep the context.
The reviewer sees the recording, selected band, playhead, exact start, exact end, and selected duration together. Their name and edit note travel with the request.
- INMove the first handle or set it to the current playhead.
- OUTMove the second handle and see the duration update immediately.
- WHORecord the client, director, editor, or crew member asking.
- WHYKeep the framing, action, or editorial instruction with the shot.
The queue
Production can see what is still owed.
Requests do not disappear into chat. The library keeps the file, time range, duration, requester, note, and state in one place.
- 01Pending — requested, not yet accepted.
- 02Approved — production intends to deliver it.
- 03Done — the request has been handled.
- CSVExport the pending and approved entries as the current shot list.
During the flight
Choose the right output for each role.
The live browser, clean local protocols, production broadcast, restream targets, and HDMI display are separate surfaces—not one overloaded screen.
DIRECTORAvailable
Open the guest browser and watch the current picture.
No owner-console password is required for the ordinary visitor view.
CREW MONITORValidation
Put the picture on an HDMI screen with its own remembered framing.
The player and presets are built; the final live-feed physical check is still owed.
PRODUCTIONAvailable
Use a separate framed and branded output.
Logo, lower-third, timecode, and Fit/Fill/Crop stay off the ordinary live path.
REMOTEAvailable
Send RTMP, SRT, or MPEG-TS to the next system.
Clean publishers are established. The newer per-destination Branded choice is built and awaiting its end-to-end device check.
LOCAL TOOLSAvailable
Take WebRTC, HLS, or RTSP straight from the device.
Use the clean feed or the production broadcast path where available.
Original media
Automatic original-media matching is not built.
The current request is measured against the Streamer review copy. Reliable matching to the aircraft recording still requires research and validation.
Research
Match by flight time, file time, and offset.
The air unit appears as USB mass storage on Linux. That is proven. Accurate automatic correlation is not.
Known
The proxy recordings and clip marks already carry timing information.
Known
The drone media can be read as files when the air unit is connected by USB.
Must prove
Clock alignment accuracy between the captured proxy and the drone original.
Must map
O3/O4 file naming, recording segments, and a request that crosses file boundaries.
Rule
Drone media stays read-only. Cosmik may reference or copy it, never alter the source card.
Current file handoff · Validation
Export the current request bundle.
Cosmik now creates one GyroFlow project per outstanding request, plus the CSV shot list and a README. The current projects reference the liveview proxy, not an automatically matched drone original.
CosmikZIP bundle
Package
Numbered GyroFlow projects carry each proxy In/Out range. The shot list keeps the requester, contact, note, state, and matching project filename.
GyroFlowProxy ranges
Review
The projects reproduce the requested trim ranges. Because the liveview proxy has no motion data, stabilization still requires the air unit’s original recording.
Current boundary: automatic proxy-to-original matching is not built. The free Cosmik Batch Exporter can import this bundle and run the local Gyroflow queue, but it does not create the missing match.
Free desktop handoff
Open the bundle in Cosmik Batch Exporter.
The Exporter reads the Streamer ZIP, creates one queue entry for each request it can resolve, and passes the selected jobs to the installed Gyroflow command-line tool.
- Accepts the ZIP, extracted folder, or shot list CSV
- Lists unresolved requests instead of guessing
- Exports horizontal and vertical variants together
- Free to use with or without Cosmik Streamer
Operating guide
Read the complete workflow.
The guide covers recording, media review, clip marking, queue states, Batch Exporter, outputs, and troubleshooting.