Synchronizing VP320/VP330 Players for Simultaneous Startup

The VP320 and VP330 media players by Waves System are designed for flexible and reliable multimedia playback. In environments like multi-screen setups (museums, shopping malls, control rooms), it is critical for multiple players to start simultaneously to ensure perfect content synchronization.

This guide explains how to configure synchronized startup across multiple VP320/VP330 players using RS-232 (Daisy Chain) or TCP/IP protocols, along with best practices to avoid desynchronization.

Why Synchronize Multiple Players?

Synchronization is essential in the following scenarios:

• Coordinated Display: Multiple screens must display the same content at the same time (e.g., advertisements, synchronized announcements).

• Live Events: Simultaneous playback for presentations or shows.

• Redundancy: Ensuring backup systems start at the same time as the primary system.

Without synchronization, even minor delays can negatively impact user experience or visual consistency.

Synchronization Methods

1. Synchronization via RS-232 (Daisy Chain)

The Daisy Chain method allows multiple players to be connected in series via their RS-232 ports. Data received on the Rx input of a player is retransmitted identically on the Tx output to the next player. This allows chaining multiple players and transmitting playback commands in a synchronized manner.

Configuration Steps

1. Connect Players in Series:

   • Use an RS-232 cable to connect the Tx (OUT) port of the first player to the Rx (IN) port of the second player.

   • Repeat for additional players (up to the hardware limit of the protocol).

   • Note: Ensure communication settings (baud rate, data bits, etc.) are identical on all players.

2. Enable Daisy Chain Mode:

   • In the Advanced Configuration menu of the player, enable "Daisy Chain Mode" to allow data retransmission.

3. Send a Playback Command:

   • The master player sends a playback command (e.g., play a folder or file).

   • Thanks to Daisy Chain mode, this command is automatically retransmitted to all slave players connected in series.

4. Verify Synchronization:

   • Run a test with a short content (e.g., 10-second video) to confirm all players start simultaneously.

   • ⚠️ Warning: If many players are connected this way, a slight delay may occur at the end of the chain.

Example Wiring Diagram

2. Synchronization via TCP/IP

For networked installations, the TCP/IP protocol offers a more flexible and scalable synchronization method. Unlike RS-232, synchronization via TCP/IP relies on tags in file names rather than direct commands.

Configuration Steps

1. Connect Players to the Network:

   • Ensure all players are connected to the same local network (Ethernet recommended).

   • Configure a fixed IP address for each player (or a DHCP reservation via MAC address).
     Example of static configuration:

     • Player 1: 192.168.0.1

     • Player 2: 192.168.0.2

     • Gateway: 192.168.0.254

     • Subnet Mask: 255.255.255.0

2. Configure the Synchronization Port:

   • The default port for synchronization is 44830 (configurable in Scenario Settings > Synchronization of Playback Start).

   • All players in the same group must use the same port number.

3. Configure the Master Player:

   • Create folders as for normal playback.

   • Add the [SYNCHROxxx] tag to files that should trigger synchronization (e.g., Lion1 [SYNCHRO001].mp4).

     • How it works: When a file with this tag is played, the master player sends a playback command to the slaves.

4. Configure Slave Players:

   • Create a synchro folder at the root of the storage medium.

   • Place the files to be played there, numbered (e.g., 001 lion2.mp4, 002 chien2.mov).

     • How it works: When a synchronization command is received, the slave player plays the corresponding file in the synchro folder.

5. Test Synchronization:

   • Start playback on the master player: slaves will automatically start the corresponding file.

   • Use a network monitoring tool (e.g., Wireshark) to verify commands are received.

Example Network Topology

Best Practices

1. Minimize Latency

• Use short cables for RS-232 connections (max 15 meters to avoid signal loss).

• Prefer wired networks (Ethernet) over Wi-Fi for TCP/IP, as they are more stable.

• Avoid slow hubs/routers: Use gigabit switches to reduce latency.

2. Hardware Synchronization

• External Relays: For ultra-precise synchronization, use an external relay controlled by the master player to simultaneously trigger power to all players.

• Time Signal: Use an NTP server to synchronize the internal clocks of the players (useful for scheduled programming).

3. Pre-Startup Checks

• Identical Content: Ensure all players have the same files in the same folders (e.g., 000, 001).

• Updated Firmware: Verify all players are running the same firmware version to avoid incompatibilities.

• Real-World Testing: Perform a test with the final content and final configuration before deployment.

Common Issues and Solutions

For further reading:

• Advanced Control: RS-232/TCP-IP

• Scheduled Programming