Skip to main content
When dealing with video segments—especially in systems that rely on distributed cameras, cloud storage, and multiple data streams—time synchronization becomes one of the most critical challenges. Without precise timing information, aligning events between multiple feeds (e.g., video, audio, and sensor data) becomes error-prone. Rhombus has implemented a custom timestamp embedding strategy that provides millisecond precision within .mp4/.m4v video segments, going beyond the coarse timing fields traditionally found in standard ISOBMFF (ISO Base Media File Format) containers.
This guide explains what this approach means, why it’s important, and how developers can retrieve and use this timestamp for building time-aligned applications.

Understanding ISOBMFF and the “free” Atom

The ISOBMFF standard (ISO/IEC 14496-12) is the container format underlying .mp4, .m4v, .mov, and many streaming segment formats like .fMP4. Its structure is based on boxes (atoms)—self-contained data units identified by a 4-character code (e.g., moov, mdat, free).
Standard timestamps in ISOBMFF (e.g., creation_time in the mvhd box) typically have seconds-level resolution. This is fine for some media workflows, but insufficient for multi-camera synchronization or high-speed event correlation.
Rhombus solves this by embedding a millisecond-precision timestamp inside a free atom. This is a non-standard, yet fully ISOBMFF-compliant, method.

The Rhombus Custom Timestamp

When Rhombus segments video (and if pulling actual segments, not a live transport stream), a custom metadata signature is written into the free box:
1

Box Type: free

In ISOBMFF, free is normally a placeholder box containing unused space. Rhombus repurposes this to carry timestamp metadata.
2

Signature: rhom

The first 4 bytes are the ASCII string rhom—identifying it as Rhombus-specific data.
3

Millisecond Timestamp

The next 8 bytes are a 64-bit integer representing the start time of the video content, measured in milliseconds since the Unix epoch (UTC).
Binary layout example:

Why This Is Important for Developers

This design choice unlocks precise synchronization capabilities across multiple use cases:

Multi-Camera Alignment

Align video feeds from different cameras to within 1 ms for coordinated monitoring

Sensor Fusion

Merge video with IoT sensor data (access control events, environmental readings)

Forensic Accuracy

Reconstruct events down to sub-second intervals in investigations

Reduced Drift

Avoid errors that accumulate when relying solely on client system clocks or NTP sync
For ecosystem and integration partners, this makes Rhombus video streams highly interoperable with third-party analytics, AI/ML pipelines, and real-time monitoring systems.

Retrieving the Timestamp

Parsing ISOBMFF Files

You can use open-source libraries to read the free box from an .mp4/.m4v segment and check for the rhom signature.

ISOBMFF Parser (C++/Swift)

Professional library for parsing ISO Base Media File Format

MP4Box.js Interactive Viewer

Online tool for visually inspecting MP4 box structures

Implementation Examples

Python Implementation

Advanced Python Usage

Multi-Segment Processing

Real-World Use Cases

Multi-Camera Event Reconstruction

Synchronize footage from multiple cameras to reconstruct security incidents:
Event Timeline Reconstruction

Sensor Data Correlation

Align video with access control or environmental sensor events:
Sensor-Video Correlation

Best Practices for Integration

Always confirm the rhom tag before interpreting the following bytes as a timestamp. This prevents misinterpretation of unrelated data.
The timestamp is UTC-based. Convert it appropriately if your application needs local time.
Combine the segment start timestamp with frame timestamps for frame-accurate alignment.
Store your parsing logic in a modular way in case Rhombus adds new metadata formats.

Performance Considerations

Efficient File Reading

For large files, read only the header portion instead of the entire file

Caching Strategy

Cache extracted timestamps to avoid re-parsing the same files

Batch Processing

Process multiple files in parallel when building timelines

Memory Management

Use streaming parsers for very large video files

Optimized File Reading

Optimized Parser

Conclusion

Rhombus’ method of embedding a millisecond-precision UTC timestamp in the free atom of ISOBMFF segments provides developers with a powerful tool for precise event alignment in multi-stream environments. This approach preserves compatibility with existing video tooling while unlocking sub-second accuracy for analytics, AI, and real-time monitoring—critical for advanced integrations in the Rhombus ecosystem.
Next Steps for Developers:
  • Experiment with the ISOBMFF GitHub library to parse Rhombus segments
  • Use the MP4Box.js online viewer to visually inspect box structures
  • Incorporate timestamp extraction into your ingest pipeline for perfectly synchronized multi-source datasets

Additional Resources

Video Player Guide

Learn how to implement live video streaming with DashJS

API Reference

Explore camera and media API endpoints as well as other video options

ISOBMFF Specification

Read the official ISO Base Media File Format spec

Developer Community

Get help and share implementations in the Developer Community

Support

Need assistance with timestamp extraction or video synchronization?
This advanced implementation guide is regularly updated to reflect the latest best practices for working with Rhombus video segments.
Last modified on July 8, 2026