Metadata Track
The CueCam app adds a .metadata track to recorded videos using an identifier com.cuecam.timeline.v1 - this allows applications like CueCam Play and third party applications to access the data recorded by CueCam whilst still ensuring the video file remains a standard video file that can be shared with anyone without the need for special software to watch it.
Note that the video itself already contains this same information on the image itself, therefore the metadata should generally not be used to overlay data on the video itself, but rather to provide reporting, navigation, and synchronisation tools or for importing into third party applications.
Payload
Each payload is a simply minimised JSON array containing the following in fixed order;
[event_type, cue_list, cue_number, attribute, text, duration, real_time, reserved]
| Parameter | Type | Detail |
|---|---|---|
| event_type | integer | 1 - cue fired 3 - marker 4 - scene |
| cue_list | string | Cue List number (encoded as a string) |
| cue_number | string | Cue number (encoded as a string) |
| attribute | char(1) | When event_type is 3, one of the colours(r, m, o, a, g, t, c, b ,p ,v) |
| text | string | Cue Label, Scene Name, or Marker Text |
| duration | integer | Cue Duration, in ms |
| real_time | string | Eos console time of recording in form YYYY-MM-DD HH:mm:ss |
| reserved [..] | string | additional fields may be present, reserved for future use, and should be ignored |
Example
[3,“1”,“661”,“m”,“Live Move”,“2026-03-01 20:15:19”,“”]
This denotes a marker 3, in cue 1/661, coloured magenta m, labelled Live Move that was triggered at 2026-03-01 20:15:19“
Timing
Event timestamps are aligned to the recording timeline subject to the following;
- CueCam applies an offset of 2 frames to markers
- For strict monotonicity, if a new timestamp is ⇐ the previous event timestamp a 1ms delay is added.
As a result of these, it's possible for a scene marker to be timestamped immediately *AFTER* the first cue of that scene. This is something that any playback application should take into account when positioning scene markers.
Colour Rendering
The JSON metadata uses a single character for colours. For consistency with the CueCam video and applications, these should be rendered within your application as follows;
| attribute value | colour | RGB | Hex |
|---|---|---|---|
| r | █ Red | 162, 25, 31 | #A2191F |
| m | █ Magenta | 208, 38, 112 | #D02670 |
| o | █ Orange | 254, 97, 0 | #FE6100 |
| a | █ Amber | 255, 176, 0 | #FFB000 |
| g | █ Green | 14, 96, 39 | #0E6027 |
| t | █ Teal | 0, 65, 58 | #004144 |
| c | █ Cyan | 0, 83, 154 | #00539A |
| b | █ Blue | 0, 29, 108 | #001D6C |
| p | █ Purple | 73, 29, 139 | #491D8B |
| v | █ Violet | 120, 94, 240 | #785EF0 |
Developer Access
If you want to make your own application compatible with CueCam, please eMail info@qcam.app - we can give you access to our beta track or a license for CueCam to remove the demo limitations.