BeView Sync

BeView Sync · for broadcast & live production

Measure lip-sync with your phone.
To the millisecond.

Is the sound ahead of the picture, or behind it? BeView Sync tells you in seconds. One phone sends a flash and a beep, the other sees and hears what comes out at the end of your chain. No measurement case, no cables to a scope.

≈ 1 mslip-sync accuracy
EBU R37green zone on the meter
> 5 stotal delay via NTP + QR
LTCaudio delay between locations

How it works

Three steps. Works on any chain: encoder, satellite, streaming, IP, a TV with a soundbar.

Generator with LED ring and timecode
1

Generator at the start

One phone sends a white flash and a chirp every second. Picture and sound start at exactly the same moment, thanks to the audio hardware timestamp. Film it with your camera or feed it straight into the chain.

Meter with camera view and round dial
2

Meter at the end

Point the second phone at the monitor at the end of the chain. The camera sees the flash, the microphone hears the chirp, both on one and the same clock.

Measurement: audio 31 ms late, within EBU R37
3

Instant result

The round dial shows whether the sound is early or late, in milliseconds, frames and fields. Green means within EBU R37. Median and spread over the last 20 measurements.

No second phone with the app? Send a link.

With Share generator link in the app you send a link via WhatsApp to whoever is at the camera. It opens the generator in the browser, with exactly your settings. Tap Start, hold the screen in front of the camera, and measure.

Open the generator

Generator in the browser

Beyond lip-sync

Lip-sync tells you whether picture and sound are aligned. But how long are they on their way? And how far behind is the sound between two locations? BeView Sync has two more methods for that, both based on shared time: NTP, the internet clock that puts both phones within a few milliseconds of each other.

NTP + QR

Total delay of your chain

How much time passes between picture and sound going into the chain and coming out? With satellite, streaming or cloud production that is easily several seconds. NTP and a QR code measure it precisely, also beyond 5 seconds.

Generatorflash + chirp on every whole UTC second
QR: beat number + exact send time
→
Your chainencoder · satellite · stream · decoder
→
Meterreads the QR code, sees the flash, hears the chirp
on the same UTC clock

How it works

  1. Both phones get the time from an NTP server (time.google.com by default) and measure how accurate it is.
  2. The generator flashes and beeps exactly on every whole UTC second. After each flash it shows a QR code with the number of that second and the exact send time, to the microsecond.
  3. The meter sees the flash and reads the QR code that belongs to it. So it knows exactly which second this was and when it was sent.
  4. Video delay = time received − time sent. Audio delay = video delay + the measured lip-sync.

Good to know

  • No upper limit: the QR code says which second you are seeing, so 8 or 20 seconds of delay can be measured too.
  • Accuracy depends on NTP: a few milliseconds on good Wi-Fi. The app shows the uncertainty of both phones (± ms).
  • Both phones need internet. Turn on Absolute delay (NTP + QR) in the settings.
  • Several generators in NTP mode run in sync automatically, even at different locations.
LTC

Audio delay between two locations

Commentary lines, remote production, intercom, audio over IP: how far behind is the sound between location A and location B? BeView Sync sends LTC timecode carrying the real time, and measures the delay 25 times per second at the other end.

Location ALTC Generator
timecode = UTC time now
→
Audio linkline · codec · IP · transmitter
→
Location BLTC Reader
compares with its own UTC clock

What is LTC?

LTC (Linear Timecode, SMPTE/EBU) is the broadcast world's standard timecode, carried as an audio signal. Every frame holds hours, minutes, seconds and frames. Because it is just audio, it passes through any audio link.

How it works

  1. The LTC Generator at location A puts the real UTC time in the timecode. Every frame starts exactly on the UTC frame boundary, locked via NTP.
  2. Feed that audio into the link, for example through a USB-C audio adapter as a line output. The level is −6 dBFS.
  3. The LTC Reader at location B hears the timecode (through the microphone or a line input) and compares every frame with its own NTP clock.
  4. Delay = arrival time − time in the timecode. 25 times per second, with a graph of the last 10 seconds.

Good to know

  • Frame rate follows your setting: 25 fps for 1080i50, p25 and p50; 30 fps for 29.97/59.94/60; 24 fps for 23.976/24.
  • Accuracy depends on NTP at both ends. The generator sends its own NTP uncertainty along in the timecode (user bits), so the reader can show the total ±.
  • Hearing the LTC through a speaker? Enter the distance to the speaker: sound takes 2.9 ms per metre.
  • The reader shows min, max and spread, so you also see jitter and dropouts on the link.

Everything you need

Lip-sync

Camera and microphone on one clock. An exposure of exactly one frame and sub-frame flash detection give a spread below one millisecond.

Mirror calibration

Hold the phone in front of a mirror: it measures its own screen and speaker delay and corrects for it from then on.

Total delay

NTP and a QR code on screen: not just lip-sync, but how long picture and sound are on their way. Read more

Between locations

LTC timecode locked to UTC. Generator at location A, reader at location B: the audio delay 25 times per second. Read more

Two generators in sync

One generator listens to the other and then runs in lock-step, including the clock difference between the devices.

Self-configuring camera

The app reads what the camera can do and picks a frame rate that is flicker-free under 50 Hz light. No guessing.

Get started

Download the app for free for Android (10 or newer) and try it for 10 measurements. After that you need a license: request a license.

Free download

Open the file on your phone and allow installing from this source. Each download is logged (IP address, country and device type) so we can count downloads; IP addresses are shortened after 30 days. See the privacy statement.

BeView Sync is a personal project. We do our best to measure as accurately as possible, but give no guarantee of 100% accuracy. Terms