Production 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 → write the card → stabilized clips Proven end to end on real hardware

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.

Current Cosmik Streamer Flight View with owner-supplied stadium footage
Flight ViewWatch the picture and control the operational live surfaces.
Current Cosmik Streamer Media Library request queue
Media LibraryOpen the saved review copy and keep requests beside the recording.
Current Cosmik Streamer visual clip timeline demonstrated with an owner-supplied stadium-flight frame
Clip timelinePlace In and Out on the picture, then keep the requester and note attached.

Workflow

Five production steps.

Every step below is built and has been run end to end on real hardware, with the aircraft's own card, to finished stabilized clips.

01 / ON SET

Crew watches the live flight.

Guest or production browser, or an HDMI screen on the truck.

Available
02 / REVIEW

The flight becomes a review copy.

Recording, thumbnail, playback, seeking, download, and local retention.

Available
03 / SELECT

The operator marks the shot.

Visual In/Out, requester, contact, note, queue status, and shot-list export.

Available
04 / CONFORM

The mark finds the drone file.

Cosmik reads the card and lines the flight up against the aircraft's own recording. Accurate to about five seconds; a frame-exact confirmation step is not built.

Available
05 / PACKAGE

Outstanding requests become a post bundle.

One GyroFlow project per request, the shot list, and instructions — written to the card by one button.

Available

After 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.

  1. 918samples recorded during one 15.8-minute hardware-validation flight.
  2. ELRSbackpack telemetry confirmed on the Raspberry Pi.
  3. GPS723 fixes recorded, but position freshness was not good enough for a dependable map claim.
  4. WATCHOpen the matching recording at a moment worth reviewing.
Current Flight Log Signal view with controlled demonstration readings
Signal reviewExact current interface · controlled readings; hardware evidence stated separately
Current Cosmik clip timeline demonstrated with an owner-supplied stadium-flight frame
Make the selection on the pictureExact current interface · owner-supplied stadium frame

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.

  1. INMove the first handle or set it to the current playhead.
  2. OUTMove the second handle and see the duration update immediately.
  3. WHORecord the client, director, editor, or crew member asking.
  4. 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.

  1. 01Pending — requested, not yet accepted.
  2. 02Approved — production intends to deliver it.
  3. 03Done — the request has been handled.
  4. CSVExport the pending and approved entries as the current shot list.
Current Media Library with a controlled demonstration request queue
Recordings and requests togetherExact current interface · controlled demonstration jobs

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 MONITORAvailable

Put the picture on an HDMI screen with its own remembered framing.

The Streamer recognises the screen and restores the framing you chose for it. Driven on a real monitor with the live picture.

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

Your mark finds the aircraft's own file.

Cosmik lines the flight up against the recording on the card and names the real file, with the in and out points moved onto it. Here is exactly how far that goes, and where it stops.

Available

Matched from the flight itself, not a wall clock.

The airborne stretch of the flight log is aligned to the card recording that fits it, so the two devices never have to agree about the time of day.

Built

The card is read, every recording on it is measured, and the best fit is chosen automatically.

Built

The shot list names the card, the file, and the in and out points on that file.

Boundary

It lands the moment within about five seconds. That is enough to find the shot, not to cut it frame-exact.

Not built

A confirmation step where the pilot nudges the match to the exact frame.

Not built

Refusing to guess is deliberate: an ambiguous card is left unmatched and says why, rather than naming the wrong file.

Untested

DJI air-unit cards are what this was proven on. Action-camera cards have not been tested.

Rule

Drone media stays read-only while it is inspected. Cosmik writes only into its own folder on the card.

Current file handoff

Export the current request bundle.

Cosmik creates one GyroFlow project per outstanding request, plus the shot list and a README. Press one button and the whole bundle is written into its own folder on the card you already have to carry home.

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: the match is made on the Streamer, while the card is in it, and lands within about five seconds. The free Cosmik Batch Exporter reads that shot list and runs the local Gyroflow queue. Neither one nudges the match onto an exact frame — that step is not built.

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
Current Cosmik Batch Exporter with a stadium preview, version controls, and queued files
Cosmik Batch ExporterVersion 0.2.0 interface · controlled demonstration content · the shipping build is 0.9.2 and this screen has changed since

Operating guide

Read the complete workflow.

The guide covers recording, media review, clip marking, queue states, Batch Exporter, outputs, and troubleshooting.

Read Media & Clips