Skip to content

Script Configuration

Sync Configuration

The SyncCore system is able to lock to any of the following from any of the following reference clocks:

  • PTP (IEEE-1588)

  • GPS

  • NTP

  • Genlock

Choosing a Sync Reference

Not all Sync Reference types are equal - some provide phase lock (to prevent drift), some provide time lock (to accurately schedule start times), and some provide both. Sync Reference choice depends on your system architecture and requirements.

  • PTP (IEEE-15888) - Phase Lock AND Time Lock

  • GPS - Phase Lock AND Time Lock

  • NTP - Time Lock

  • Genlock - Phase Lock

Because NTP only provides a Time Lock, Sync Core allows you to connect a Genlock source when in NTP mode for a combined NTP + Genlock mode. In this mode the A/V clocks are used from Genlock, and the time of day is used from NTP. When a valid Genlock source is connected while in NTP mode, the Sync Source displayed on the front panel of your device will read "NTP + Genlock".

Locking to a Sync Reference

Within your WinScript Live project, you can configure an external sync reference by accessing the Configuration-->Script menu option and browsing to the Clocks section. Here, you can choose the reference source you want this device to synchronize with and specify a master Frame Rate for the show control system.

If using PTP as a clock source, clicking the gear icon next to the source dropdown box will allow you to configure the advanced settings for PTP. The Announce Timeout defines the number of intervals the controller will wait without recieving a PTP announcement before a timeout occurs. The default is 3 (8 seconds). The Domain setting allows you to isolate the controller from multiple Grandmaster Clocks across multiple networks. The default domain is 0. The Delay Request Interval is the minimum permitted mean time interval between Delay_Req messages. A shorter interval makes the controller react faster to the changes in the path delay. It's specified as a power of two in seconds. The default is 0 (1 second).

The Clock Servo settings let you set the Proportional Gain and the Integral Constant that the controller will use when locking to the Grandmaster Clock. Changing these settings can allow the controller to lock faster, but might decrease the stabiltiy of the clock during steady state.

If using NTP as a clock source, clicking the gear icon next to the source dropdown box will allow you to set the NTP Server Address, as well as the Min Poll Rate and the Max Poll Rate. These polling times define the minimum and maximum amount of time inbetween packets sent to the NTP server. These polling times can be set to a variety of times between 1 second and 64 seconds. The default minimum polling time is 4 seconds, and the default maximum polling time is 8 seconds.

If your application does not require the use of an external reference clock, you can leave this selection at its default value of None. In this mode, the product will generate its own clocks internally.

Distributing a Sync Reference

Not only can this product lock to an external sync reference, it is also capable of distributing sync references as well.

Genlock is always distributed automatically based upon the Frame Rate you have selected for the Master Clock. This is indicated in the Clocks section of the script configuration as well:

Keep in mind that not all frame rates are compatible with the video standards supported by the Genlock output circuit. Supported rates include 59.94, 50, 29.97, and 25 fps. If you choose any other frame rate, WinScript will indicate that the Genlock output is disabled like so:

There's also the option to distribute a clock via network using NTP or PTP. This setting is configured from the Clocks section of the script configuration screen which is accessed using the Configuration-->Script menu option.

As seen in the example above, it is possible for SyncCore-enabled devices to lock to an external reference and simultaneously distribute another type of reference. A common example of this would be configuring a V16X to lock to an external PTP Master (i.e. Ride Control PLC). This V16X may then need to synchronize precisely with RidePlayerX units over a wireless network which does not support PTP distribution. To overcome the limitations of the wireless network, the V16X could be configured to distribute a sync reference as an NTP Server. We would then configure the RidePlayerX units to lock to the V16X via NTP.

If distributing a clock out over the network using PTP, clicking the gear icon next to the source dropdown box will allow you to configure the advanced settings for PTP. All Alcorn McBride SyncCore devices distribute PTPv2. The Priority 1/Priority 2 setting is used in the best master selection algorithm, lower values take precedence. Must be in the range 0 to 255. The default is 128. The TTL setting specifies the Time to live value for IPv4 multicast messages and the hop limit for IPv6 multicast messages. This option is only relevant with the IPv4 and IPv6 UDP transports. The default is 1 to restrict the messages sent by the controller to the same subnet. The Domain setting allows you to isolate the controller from multiple Grandmaster Clocks across multiple networks. The default domain is 0. The Sync Interval setting is the mean time interval between Sync messages. A shorter interval may improve accuracy of the local clock. It's specified as a power of two in seconds. The default is 0 (1 second). The Announcement Interval is the mean time interval between Announce messages. A shorter interval makes the controller react faster to the changes in the master-slave hierarchy. The interval should be the same in the whole domain. It's specified as a power of two in seconds. The default is -1 (500 milliseconds).