User guide¶
This guide explains the parts of an FMV application that sit between raw MPEG-TS packets and an operator-facing product. Start with the layer you are building, then follow the links to its timing, failure, and deployment details.
Transport and timing¶
Use the transport layer when you need to receive, demultiplex, transform, or send MPEG-TS while preserving its program structure and media timing.
- Live transform pipeline covers KLV replacement, injection, program selection, signalling, and reconnects.
- UDP transport and RTP transport cover network packetization and receive behavior.
- MISP and UTC timestamps separates the MPEG PTS clock, MISP absolute time, and civil UTC.
- Transport rate and PCR restamping applies when an output must follow a physical constant-rate schedule.
Metadata and media¶
Use these pages when decoding or presenting what is inside an FMV service:
- Audio reconstructs and optionally decodes ST 1001 audio frames.
- Video properties inspects common H.262, AVC, and HEVC sequence information without decoding pixels.
- GeoJSON streams turns current ST 0601 and VMTI geometry into an incremental GIS boundary.
- The API reference covers KLV, ST 0601, ST 0902, ST 0903, range imagery, transformations, and transport types.
Applications and integrations¶
- Reference player is the shortest route to synchronized video, telemetry, mapping, detections, and a timeline.
- AI and VMTI sidecars connects decoded frames to local or remote inference and standards-native detections.
- Adapter guide defines the boundary for model, codec, GIS, network, and application runtimes.
- Web clients explains recorded and live browser timing.
- FFmpeg and GStreamer describes where mature media runtimes fit around the pure-Python core.
- Ecosystem interoperability covers CSV, GeoJSON, native transport, and third-party application boundaries.
Standards and operational boundaries¶
Read common pitfalls before joining timestamps, carrying sparse metadata state, or projecting detections onto a map. The conformance matrix and known limitations state which requirements and deployment profiles are in scope. Use the glossary for unfamiliar transport or MISB terms.