Skip to content
Disguise User Guide
⚠️ If you use IP-VFC cards, we recommend updating to r29. This will also require a firmware update which you can perform using the IP-VFC firmware updater tool on the Resources page under the VFC Firmware Update tab.

IP-VFC - FAQs

How reliable are the SFPs that have been tested with IP-VFC?

As part of our QA processes, the SFPs outlined in the list of supported SFPs have been used alongside the IP-VFC in the same testing environments, often over several days at a time with no issue. Long range SFPs draw more power and so are likely to run hotter during operation.

How can I update the firmware of the IP-VFC?

We have put together documentation on how to update the firmware of the IP-VFC. This is available here.

What’s the behaviour of Port 2 on the IP-VFC when running redundancy in ST 2110 mode, and will it impact the GPU load on the server by running a redundant video stream?

There is no difference in GPU load. The redundant video stream is completed internally to the IP-VFC

When using ST 2110 mode in multicast, can you use the boundary clock on the on the fabric for timing instead of a PTP grandmaster?

Fabric by default will act as a boundary clock so that will most often be the case.

Can you use a fabric in the same configuration for RenderStream on one port/VLAN and ST 2110 on another?

We will look to test this.

Why can’t the IP-VFC support 2160p60 at RGB 4:4:4 10-bit in SDI mode?

The IP-VFC is limited in SDI mode by 12G SDI, which means that it has a bandwidth of 12 Gbit/s. We offer YUV 4:2:2 support up to 4K DCI 60p in 10-bit which reaches around 11.2 Gbit/s. We are therefore restricted by bandwidth constraints and would have to consider lower framerates (i.e. 24p) on a case-by-case basis.