Skip to content

Clocks

The Clocks tab allows you to configure input and output clocks, as shown in Figure 1 (with the V16X as the selected device.)

Test
Figure 1 Clocks - V16X Device Selected

Leader Clock

Source

This section allows you to configure your device to lock to the sync reference of your choice. See the Sync Core section for more information on clock types.

Table 1 below outlines which clock sources are available to each device.

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.

Table 1 Clock Sources by Device

Device Clock Source
V16X Genlock (VSync), GPS, PTP (2x), NTP (4x)
V4X NTP 2x
V16Pro Genlock (VSync)
VCore None
BinloopX Genlock (VSync), GPS, PTP, NTP
RidePlayer Genlock (VSync), GPS, PTP, NTP
RidePlayerX GPS, PTP (2x), NTP (2x)

PTP Settings

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 as shown in Figure 2.

Advanced PTP Settings
Figure 2 PTP Settings

The PTP Announce Timeout defines the number of intervals the controller will wait without receiving a PTP announcement before a timeout occurs. The default is 3 (8 seconds).

The PTP Domain setting allows you to isolate the controller from multiple Grandmaster Clocks across multiple networks. The default domain is 0.

The PTP 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 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 PTP Proportional Gain and the PTP Integral Constant that the controller will use when locking to the PTP master. These clock servo settings can have a drastic impact on PTP performance and clock stability, so it is not recommended to change these values.

NTP Settings

If using NTP as a clock source, clicking the gear icon next to the source drop-down will allow you to set the NTP Server Address, as well as the Min Poll Rate and the Max Poll Rate as shown in Figure 3.

Advanced NTP Settings
Figure 3 NTP Settings

These NTP polling times define the minimum and maximum amount of time between 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.

Frame Rate

This setting specifies the frame rate at which the main system show control clock runs. Select from 23.976, 24.0, 25.0, 29.97, 30.0, 30.0D, 47.952, 48.0, 50.0, 59.94, and 60.0 FPS.

Sample Rate

The RidePlayerX and the RidePlayer have an additional setting for setting the Sample Rate of the device to either 44.1 kHz or 48.0 kHz as shown in Figure 4.

Sample Rate Setting
Figure 4 Sample Rate

Network Audio

This option selects whether audio playback uses the network audio (Dante/AES67) clocks (checked), or the SyncCore clocks for audio playback (unchecked). If you are synchronizing multiple devices using SyncCore, it is recommended that you leave this box unchecked.

Network Audio Setting
Figure 5 Network Audio

This option is only available on the following devices with a network audio output:

  • BinloopX
  • RidePlayerX
  • RidePlayer

Network Clock Out

SyncCore is not only capable of locking to an external sync reference, it can also distribute PTP or NTP. For products with multiple network ports, you can choose which protocol (if any) is active on each port. All SyncCore devices distribute PTPv2.

On devices with multiple PTP-capable network ports (like V16X), it's possible to make the device act as a boundary clock by choosing PTP as the Clock Source and choosing PTP as the Network Clock Out on a different port.

It is also possible for SyncCore-enabled devices to lock to an external reference and simultaneously distribute a different type of reference. A common example of this would be configuring a V16X to lock to an external PTP source (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 re-distribute the sync reference as an NTP Server. You could then configure the RidePlayerX units to lock to the V16X via NTP.

PTP Clock Out Settings

If distributing a clock out over the network using PTP, clicking the gear icon next to the source drop-down will allow you to configure the advanced settings for PTP as shown in Figure 6.

PTP Clock Out Settings
Figure 6 PTP Clock Out Settings

Priority 1/Priority 2 is used in the best master selection algorithm. Lower values take precedence. Must be in the range 0 to 255. The default is 128.

TTL 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.

Domain allows you to isolate the controller from multiple Grandmaster Clocks across multiple networks. The default domain is 0.

Sync Interval 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).

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).

Genlock (BinloopX)

Only available on BinloopX, this section lets you configure the termination and output mode of the Genlock output as shown in Figure 7.

Genlock Settings
Figure 7 Genlock Settings

Note

Termination and output mode are configured via DIP switch on other SyncCore products.

Genlock Out

This section indicates the configured output frame rate of the Genlock Output as shown in Figure 8.

Genlock Output Enabled
Figure 8 Genlock Output Enabled

Genlock is distributed automatically based upon the frame rate you have selected for the Leader Clock. 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 Live will indicate that the Genlock output is disabled as shown in Figure 9.

Genlock Output Disabled
Figure 9 Genlock Output Disabled