Video Timings

When outputting video from d3, we can use various timing methods. A timing method is a set of parameters that define aspects such as:

• Horizontal blanking: The interval between the end of one line and the start of the next.
• Vertical blanking: The interval between frames.

The values for these parameters can vary depending on the chosen method.

Considerations for video timings

• The type of timing used may need to be compatible with downstream devices to ensure a specific type of timing will be understood at the other end. For example, some monitors may not display the video at all if the timing format is unsupported.

• The video timing will adjust the amount of data the video stream requires, so if devices are limited on bandwidth then some timing modes may not be able to be used.

Caution

When using IP-VFC cards, we recommend only using IP-VFC cards and not mixing these with other VFC cards, as we cannot guarantee genlock with other cards. We are aiming to address this in future releases.

Timing mode selection in the Feed screen

In the Feed screen, users can select the timing mode for each output, provided it’s an HDMI or DisplayPort VFC, or a direct output (e.g. from the EX range). The available timing modes are:

• SMPTE
• CVT
• CVT Reduced Blanking (CVT RB)
• CVT Reduced Blanking 2 (CVT RB2)
• AUTO

Note

What we refer to as SMPTE in d3 is actually CEA timing. However, it is widely used in the film industry under the SMPTE standards - especially for devices using SDI input/output, where fixed bandwidths are expected.

How AUTO timing works

When AUTO is selected, d3 will test timing methods in the following order until one fits within the bandwidth constraints of the output type:

• DMT (not directly selectable)
• SMPTE (CEA)
• CVT
• CVT RB
• CVT RB2

Each output type has a different bandwidth limit. For example:

• DisplayPort 1.4: ~26 Gbps
• DisplayPort 1.2: ~17 Gbps
• HDMI 2.0: ~14.4 Gbps
• DVI: ~8 Gbps

Higher resolutions require more bandwidth, which can affect which timing mode AUTO selects. A downstream device may reject a high-resolution signal if the required timing mode isn’t supported.

Bandwidth and colour format

The colour format also affects bandwidth usage:

• RGB Full (RGB 4:4:4), RGB Limited, YCbCr 4:4:4: ~3 bytes per pixel
• YCbCr 4:2:2: ~2 bytes per pixel
• YCbCr 4:2:0: ~1.5 bytes per pixel

Important Note

AUTO operates independently per output. It does not consider the timing mode selected on other outputs. This can result in outputs failing to genlock, which is discussed further below.

As of version r30.5, d3 now logs the selected AUTO timing mode in the console when feeds are applied. Previously, this was not recorded.

Passthrough vs non-passthrough VFCs

• With passthrough VFCs (e.g. HDMI, DP), the timing mode set on the GPU output via EDID is passed directly to the connected device.

• With non-passthrough VFCs (e.g. QSDI, QDVI, IP), we convert the GPU timing mode:

  • QSDI: The GPU uses CVT, while the QSDI VFC outputs use SMPTE/CEA, which is standard for SDI devices.
  • IP cards: Typically use CVT RB2, unless running under 25fps, where CVT or AUTO might be used.

We do not currently support genlocking IP outputs with other VFCs, but this is a planned improvement that we hope to make available in future.

Genlock Basics

Genlock is the process of synchronising the display of each frame on each output of a machine to an external clock signal. This external signal is typically distributed to multiple machines, allowing them to stay in perfect sync — essential for multi-display or multi-machine setups.

A similar concept applies to internal genlock, also known as framelock, where one output on a machine acts as the timing master, and the other outputs synchronise to it.

Key Points:

• Synchronisation Scope: Genlock applies only to outputs that are outputting nearly identical amounts of data. This means the resolution, frame rate, and format must match across all outputs being genlocked.

• Resolution Limitations: Attempting to genlock outputs using different resolutions usually results in failure — typically, only one will successfully genlock while others will not.

• Output Type: Genlock operates at the GPU output level, not at the VFC (Video Format Converter) output level. So synchronisation happens before any format conversions applied downstream.

Genlock ensures that multiple displays or machines present frames in lockstep, which is crucial for seamless visuals in video walls, immersive environments, or high-end simulation systems. But to work properly, all genlocked outputs must match in resolution and timing characteristics.

Timing Differences

When using different timings across outputs, the amount of data being transmitted can vary enough that genlock no longer works — even if the resolution is the same. This is because genlock relies not only on resolution, but also on how data is clocked out of the outputs.

It’s common to encounter genlock issues when using different VFCs in the same machine. Different VFCs often default to different timing modes depending on the output type, which can disrupt genlock synchronisation.

Troubleshooting

1. Avoid Mixing Incompatible Timing Modes

Genlock requires outputs to use very similar timings, not just the same resolution and frame rate.

If one output is using SMPTE and another uses CVT, genlock may fail even if resolutions match.

Solution: Manually set a consistent timing mode (e.g. CVT or CVTRB2) across all outputs.

Do not leave any outputs on Auto if you are using different VFC types.

2. Be Cautious When Mixing VFC Types

Some VFC types (e.g. QSDI or IP-VFC) use fixed timing modes internally (such as CVT), while others (like HDMI or DP) allow timing selection.

If mixing passthrough cards (e.g. HDMI + DP):

• Choose a specific timing manually for each.

If mixing passthrough and non-passthrough cards:

• Try aligning GPU timings manually to match the known default of the non-passthrough card (e.g. CVT for QSDI).

3. SMPTE Timing May Not Genlock with Some Cards

If you’re using SMPTE timing on an HDMI output and cannot genlock with other VFCs (e.g. QSDI), try switching to:

• CVT when pairing with QSDI
• CVTRB2 when pairing with IP-VFC

4. Check for Bandwidth Conflicts

For high resolutions (especially with DP1.4 or 4K outputs), the selected timing mode must also be within the bandwidth limits of the VFC.

A timing mode that exceeds the card’s capabilities will fail silently or block genlock.

Tip

If unsure, start testing with lower-bandwidth formats (e.g. 1080p60) and scale up once genlock is successful.

5. Use Consistent Output Settings Across Machines

If synchronising multiple machines, make sure:

• The same timing mode, resolution, and framerate is used across all outputs that require genlock.
• Avoid Auto timing modes in multi-machine setups unless fully matched.