User Manual

Getting Started

OSRTIME Sync-Box TCR transforms your Android device into a professional timecode generator and sync box for film, broadcast, and live production.

Installation & First Launch

After installing the application (currently available via Private Beta), launch it to begin. On first start, you will be asked to grant the required system permissions.

The App at a Glance

After granting permissions, the app opens on the Master page showing a running Time of Day (TOD) timecode. The bottom navigation bar provides access to all major areas of the app:

Master page at first launch — TOD mode, 24 fps

Master Clock

The Master page is the primary output display of the timecode engine. It shows the current timecode in a large seven-segment format, optimized for visibility on dark sets and at a distance.

Display Elements

The Master display consists of several information layers:

• Timecode Display — HH:MM:SS:FF in large green digits. The labels H M S and the frame rate indicator are shown above.
• Date Line — Day of week and date below the timecode.
• Mode Chip — Shows the current source mode: TOD, CUST, JAM, SLV, or WIFI SLV.
• Action Buttons — Fullscreen toggle, LTC audio output (mute/unmute), and Record toggle.

Timing Sources

The timecode generator can operate in four distinct modes, each selectable from the Control page:

WiFi Slave Display

When the device is operating as a Wi-Fi Slave, the Master display updates to reflect the remote source:

Master display in WiFi Slave mode — the mode chip reads "WIFI SLV"

Control

The Control page is the central configuration hub. It provides direct access to all timecode sources, jam status, and external input monitors.

Control page — TOD, Custom timer, and Jam Status sections

TOD Section

Shows the current Time of Day timecode with status (RUNNING), selected frame rate, and an info button for technical details. Use SET TOD TO NOW to resynchronize with the device clock.

Frame-rate selector — standard and high-frame-rate options

Frame Rate

For Time of Day (TOD), select the timecode frame rate from the frame-rate menu. The selected rate determines how the running TOD timecode is represented.

The Custom timer has its own frame-rate selector and can therefore run at a different frame rate from TOD.

When synchronizing from an external timecode source, manual frame-rate selection is normally not required. OSRTIME detects the incoming timecode format and uses the corresponding rate for synchronization.

High-frame-rate modes use an appropriate LTC transport rate, shown in parentheses in the selector — for example, 50 fps (25LTC) or 60 fps (30LTC).

Custom Timer

An independent free-running timecode generator with its own frame rate selector. Provides preset buttons for quick start values:

• 00:00:00:00 — Reset to midnight
• 01:00:00:00 — Jump to one hour

Jam Status

Displays the currently jammed timecode value and its source. When no jam has been performed, it shows NO JAM VALUE with placeholder dashes.

External Input Sources

Below the Jam Status, two additional monitors appear when external sources are available:

Full Control view — LTC Input Monitor and WiFi Input both visible

• LTC Input Monitor — Decodes incoming Linear Timecode from the audio input. Shows lock status, detected frame rate, LTC channel selector, and a JAM FROM LTC button.
• WiFi Input — Displays timecode received from a network Master device. Shows the Master identity, frame rate, confidence level, and signal age. Provides a JAM FROM WIFI button.

Jam Result

After performing a Jam (from either LTC or WiFi), the Jam Status section updates to confirm the operation:

Jam Status after successful WiFi Jam — shows "MASTER / JAMMED FROM REMOTE"

Audio & Routing

The Routing page configures which physical audio input the app uses, and how its channels are assigned for LTC reception and audio recording.

Built-in Microphone

By default, the app uses the device's built-in microphone in Auto Mode. This can be used for receiving LTC signals acoustically from a nearby source. For a direct wired LTC connection, use a compatible audio input or USB audio interface.

Routing page with built-in microphone — 1 channel (LTC), level meter active

USB Audio Interface

When a class-compliant USB audio interface is connected, additional channels become available. OSRTIME supports up to 4 input channels simultaneously.

USB interface connected — 4 channels with individual level meters and cross-point arming

Cross-Point Routing & Arming

The lower section shows the available recording tracks. Each channel can be individually armed (enabled) for recording:

• CH1 — Typically assigned to LTC. Armed by default.
• CH2, CH3, CH4 — Additional audio channels from the USB interface. Enable by tapping the checkbox.

Recording

The Record page manages BWF (Broadcast Wave Format) field recording with embedded timecode metadata. All recordings include precise timecode stamps for seamless post-production sync.

Record page showing a saved session — CH1 (LTC) recorded, CH2–CH4 (Audio) available

Channel Layout

Each armed channel from the Routing configuration appears as a separate track card:

• CH1 · LTC — The primary timecode track. Shows AUDIO RECORDED when data has been captured.
• CH2–CH4 · Audio — Additional audio tracks. Each shows the source device and channel number.

Level meters on each card show real-time signal strength during recording.

Starting a Recording

Recording is controlled via the REC button visible on both the Master page and the persistent header bar. You do not need to be on the Record page to start or stop recording — it works from any page in the app.

Recording with a USB interface at 24 bit

Connecting a USB audio interface or having it automatically selected does not automatically enable 24-bit recording. For 24-bit recording, you must explicitly manually select the interface and configure the bit depth in settings.

1

Connect a compatible USB audio interface

Before connection, the Routing page typically shows the built-in microphone in Auto Mode.

Before connection: Auto Mode with built-in microphone

After connection, Auto Mode may automatically display two input channels. This is not a manual selection yet and does not confirm 24-bit operation.

USB connected in Auto Mode: Not yet manually selected

3

Explicitly select the USB interface

Open Physical Input Routing and explicitly select the named USB interface (e.g., "USB Audio Input – USB-Audio – UAC-232") instead of Auto Mode.

Input menu opened

UAC-232 manually selected

4

Check for Manual Lock

Check that the routing field confirms MANUAL LOCK for the selected interface.

Routing confirmed with MANUAL LOCK

5

Find Bit Depth in Settings

Open Settings and find Bit Depth in the recording section. It may still show "16-bit – Aktiv" (16-bit – Active).

Settings showing 16-bit – Active

6

Select 24-bit

Open the Bit Depth menu and select "24-bit – Unterstützt" (24-bit – Supported).

Menu showing 24-bit – Supported

24-bit option selected

Note: The final image illustrates the selection inside the dropdown, which is not yet a completed runtime confirmation.

Important Operation Notes

• Supported vs Active: “Supported” means the option is offered by the system, whereas “Active” confirms the currently used output format.
• Auto Mode: Auto Mode and Auto USB Select are not a confirmation of an active 24-bit recording. For the 24-bit workflow described above, the interface must be selected manually.
• 16-bit Fallback: If Android rejects the requested higher-resolution recording mode, the app displays the fallback to 16-bit. Always check the active format.
• Disconnecting USB: When you disconnect the USB interface, its audio path is terminated. In the tested configuration, the remaining audio input falls back to 16-bit. Not every fallback input on every Android device is strictly limited to 16-bit, but you must manually check the device selection and active format after reconnecting.
• Channels: The number of opened input channels and the number of recorded channels are separate—only armed channels are saved. Two input channels do not automatically represent a fixed Left/Right stereo pair (they are simply CH1, CH2, etc.).
• PCM Format: 24-bit recording over this path uses Integer PCM. Version 1.0.2 does not provide 32-bit float recording.

Troubleshooting 24-bit USB Setup

• Interface is missing: Check the connection and use "Rescan Audio Devices".
• 24-bit is not offered: Check your manual device selection. 24-bit support depends on both the audio interface and the Android device.
• Only “Supported” is shown: You must select the 24-bit format and wait for the subsequent "Active" status confirmation.
• True 16-bit fallback: If Android rejects the 24-bit request and falls back, continue working with the confirmed 16-bit format. OSRTIME Syncbox TCR does not guarantee universal 24-bit compatibility for every device.

Network & Sync

OSRTIME features a wireless synchronization engine that allows multiple devices to share a common timecode clock over standard Wi-Fi networks.

How It Works

Sync Lifecycle

A sync operation progresses through three stages:

Before sync — Drifting

After sync — Synced

Jam Sync

Jam Sync is a one-time clock copy from an external source. Unlike Slave mode (which continuously chases), a Jam copies the current timecode value and then free-runs independently using the OSRTIME Virtual Precision Oscillator (VPO).

Jam Sources

OSRTIME can Jam from two sources:

Performing a Jam

LTC Lock

When a valid LTC signal is being received, the LTC Input Monitor turns blue and displays the decoded timecode with the detected frame rate:

LTC Input Monitor showing "LOCKED @ 24 FPS" — ready to Jam

Slave Mode

In Slave mode, the device continuously tracks an external timecode source in real time. Unlike Jam (which copies once and free-runs), Slave mode keeps the display locked to the incoming signal.

Selecting the Slave Source

When switching to Slave mode, a modal prompts you to choose the timecode source:

Select Slave Source — choose between LTC Input and WiFi Network

Active Slave State

Once Slave mode is active, the Control page reflects the new state:

Slave mode active — Jam Status shows "INACTIVE (SLAVE MODE)", SLV chip highlighted

The Master display will also update its mode chip to indicate the slave source — for example, WIFI SLV for Wi-Fi slave operation.

Settings

The Settings page provides global configuration options for language, audio behavior, and recording preferences.

Language

Settings — interface language selection

OSRTIME supports the following interface languages:

• System Default
• English
• Deutsch
• Español
• 中文（简体）
• العربية
• עברית

Audio

• Auto USB Select — Automatically switches to a USB audio device when one is connected. Disable this to keep using the built-in microphone even when a USB device is plugged in. (Note: Auto USB Select does not enable 24-bit recording. You must explicitly select the interface manually for 24-bit workflows.)

Recording

• Recording Folder — The storage location for recorded BWF files. Tap CHANGE to select a different directory.
• Sample Rate — Default: 48.0 kHz. This is the standard broadcast sample rate for professional audio.
• Bit Depth — Configures the audio resolution (16-bit or 24-bit). 24-bit options require explicit manual device selection in Routing.

Troubleshooting

Common solutions for sync, audio, routing, and timecode workflow issues.

LTC Signal Not Detected

• Ensure the Microphone permission is granted.
• Check the Routing page — is the correct input device selected?
• Verify the LTC source is active and the cable connection is secure.
• Try pressing RESCAN AUDIO DEVICES on the Routing page.

Devices Not Discovering Each Other

• Confirm all devices are connected to the same Wi-Fi network or hotspot.
• Check that Local Network permissions are granted.
• Some public or enterprise Wi-Fi networks block device-to-device communication. Use a mobile hotspot instead.

Sync Status Stuck on "Drifting"

• Tap SYNC CHAIN to initiate synchronization manually.
• Ensure one device is set as MASTER and the other as SLAVE.
• Enable Auto-Sync to maintain continuous alignment.

USB Audio Not Recognized

• Only class-compliant (driverless) USB audio interfaces are supported.
• Use a USB OTG adapter if your device has a USB-C port.
• Press RESCAN AUDIO DEVICES after connecting.
• Check Settings → Auto USB Select is enabled.

Recording Not Starting

• Check that Storage permissions are granted.
• Verify the recording folder exists and has sufficient space.
• Ensure at least one channel is armed on the Routing page.