A Shared Time Base for Bluetooth Timecode Ecosystems: PToB Architecture, Compatibility Boundaries, and a Validation Programme

Overview

This architecture study proposes a common time, quality and event contract beneath native app timestamps, vendor-specific Bluetooth interfaces and optional LTC/MTC outputs. It retains exact rational frame/sample mapping and the differences between control, jam and physical capture.

What this paper covers

• Separate shared Bluetooth transport from actual vendor interoperability.
• Map continuous time into exact frame and sample coordinates.
• Define independent recorded-event checks for each adapter and output.

Research scope

No adapter, vendor integration, LTC/MTC generator or new hardware experiment is reported. Commercial interoperability, TAI firmware support, recorded-event accuracy and genlock remain unqualified.

Read it in context

Use this as a media integration research plan. The timing measurements elsewhere concern their named clock references; they do not measure a camera exposure, audio sample clock or timecode input.