Skip to main content

Event Sync Technical Requirements

Everything you need to know about system compatibility, network settings, and hardware specifications before deploying Event Sync.

Written by Gabrielle Fanning

Overview

Event Sync requires specific hardware, network, and system setups across its Desktop App and Progressive Web App (PWA) components to function effectively. These are summarised below. For more information on how to use Event Sync, consult our Event Sync Help Center.
​

Desktop App

Hardware requirements

SMPTE LTC (Timecode)

A laptop running the Desktop App must be physically connected to the system transmitting the timecode. The setup requires:

  • An audio input device supporting a 16–24-bit / 44.1 or 48kHz sample rate.

  • A physical cable for signal transmission.

  • Correctly installed and configured audio drivers.

  • Timecode signals routed to Channel 0 of the audio device.

  • Alternatively; A virtual sound card for software-based timecode generation.

UDP

A laptop running the Desktop App must have an Ethernet connection to the system transmitting UDP timecode signals. The setup requires:

  • The UDP timecode sender and the Desktop App must be configured to use the same port number.

  • Port numbers between 1 and 1024 are reserved and cannot be used.

  • Firewall and network configurations must allow traffic through the specified port.

Manual mode

No additional requirements.

Internet connection

  • A stable internet connection is required.

  • Minimum recommendation: 4G dongle.

Supported OS

Windows:

  • Windows 10 (64-bit, Intel)

  • Windows 11 (64-bit, Intel)

Note: Compatibility with Windows on Arm computers has not been tested or supported.

Mac:

  • macOS 14 (Sonoma)

  • macOS 15 (Ventura)

Note: Event Sync is compatible only with Apple Silicon (M1/M2). Intel-based Macs are not supported.
​

Unsupported versions:

  • 32-bit operating systems (all platforms).

User requirements

  • Assign a dedicated team member to manage the Desktop App, with consideration to where the laptop needs to be positioned on-site to maintain an internet connection, and connection to the system transmitting SMPTE or UDP messages.
    ​

  • Ensure only one user operates the Desktop App at a time to prevent duplicate triggers.


Audio configuration

Audio files

  • Supported audio format: MP3, MP4, or M4A

    • Ideal setup:

      • M4A, Constant bitrate

      • Have all files used in the event hold the same target bitrate and format

  • Recommended max no. tracks per event: 10

  • Max file size per file: 50MB

  • Recommended audio duration: ≤2 hours

  • To ensure a smooth transition, we recommend adding one second of silence to both the start and the end of your audio files.

Audio configuration

  • Associated SMPTE timecodes per audio file to trigger playback (HH:MM:SS:FF) (FF max 30)

Progressive Web App (PWA)

URL

Decided in discussion between Pladia and the Customer, following a standard format. Custom domains available as an add-on.

Internet connection

An internet connection is required to launch the PWA. However, audio pre-loading on launch ensures audio playback aims to continue even if the connection is unstable.

Recommended Mobile Device & Browser

For the optimal Event Sync experience, we recommend using recent mobile devices running native, updated web browsers, on a reliable Wi-Fi or local network.

  • iOS Devices: Recent iPhone models running the latest version of Safari.

  • Android Devices: Recent Android smartphones running the latest version of Chrome.

Read more here.


PWA Theme and Content

Background image

  • PNG or JPG

  • At least 1920px high and 1080px wide

  • Max 6MB

Event logo

  • PNG

  • 720px wide

  • Max 3MB

Event display name

-

Event description

Max 80 characters

Inactive message (optional)

-

Footer (optional)

  • E.G. Sponsorship logos combined into a single PNG

  • 720px wide

  • Max 3MB

Transcript (optional)

Text content can be edited in a rich text editor in the Console.

Info modal (optional)

Text content can be edited in a rich text editor in the Console.


Related Articles
Did this answer your question?