This page summarizes the various brands of video input and output devices supported by Ventuz. This includes
Ventuz will run on any graphics card that fully supports Direct3D 9.0c under Windows 7 or higher.
|AMD|| FirePro Series (recommended) |
Radeon Series (with limitations)
Ventuz supports the ATI FirePro™ S400 Synchronization Module to synchronize multiple GPU's in a cluster of Ventuz installations.
|Nvidia|| Quadro Series (recommended) |
Geforce Series (with limitations)
The NVIDIA Quadro Digital Video Pipeline is currently not supported by Ventuz. The SDI output of these board family can be used as monitor output. External key, Audio and other features of this product line are not address by Ventuz.
|Intel||Intel integrated graphics|
While Intels integrated graphics solutions are becoming better and better, they generally can not compare to the capabilities of the GPU's from AMD and Nvidia. Intel GPUs are not recommended for production. Often, however, they are the only choice for tablet- or laptop-based productions. In these cases, be sure to verify your performance and build Ventuz scenes carefully.
|Direct3D||Windows 7 compatible graphics board|
If there are any other vendors left Ventuz can't state any technical information about them. Ventuz may run on such boards without any promises!
Ventuz allows you to use multiple SDI boards from different vendors at the same time. The amount of simultaneous streams depends on the used boards, the video formats and speed of the main boards PCI-Express slots.
Series audio k+f keyer multi multiformat bypass dual link 3G 4k Timecode AFD Specials More Info DELTA-HD yes yes5 no yes timebase no no no yes8 yes yes More Info DELTA-3G yes yes5 no yes timebase no yes2 A & B yes8 yes yes More Info DELTA-KEY yes yes5 yes yes timebase yes no no no yes yes key-delay, key-input, softkey, tracking More Info Centaurus II3 yes yes yes4 yes full yes yes no no yes yes softkey More Info Centaurus II3 LT yes no no yes full yes no no no yes yes softkey More Info Atomix3 yes yes no yes full yes yes A & B no yes yes softkey More Info Blackmagic Decklink yes yes5,12 yes1,4,12 depends6 no no yes2 B bm7 yes no More Info Blackmagic UltraStudio yes yes5,12 yes1,4,12 depends6 no no yes2 B bm7 yes no More Info VisionAV-SDI2 no no no no no no no A & B no no no More Info VisionSC-SDI4 no no no no no no no A & B no no no More Info VisionSC-HD4+ no no no no no no no no no no no More Info AJA Corvid 88 yes yes (4k)11 yes yes10 no no no A yes8 9 no no More Info AJA Kona 3G / Kona 4 yes yes yes yes10 no no no A yes8 9 no no More Info AJA Kona LHe+ yes yes yes yes10 no no no A no9 no no More Info AJA Kona LHi yes no no yes10 no no no A no9 no no More Info AJA Io XT yes no no yes10 no no no A no9 no no More Info AJA Io 4K yes no no yes10 no no no A yes no no More Info
|Deltacast|| Delta-HD series |
The Deltacast HD and 3G SDI boards have been designed for real-time video IO in television broadcast. They provide precisely the feature set required for reliable SDI IO and VANC processing. Neither more, nor less. The Deltacast product range are recommended for use with Ventuz. Please contact Ventuz sales or your Ventuz Broadcast Integrator for details.
Ventuz 5.02.00 uses a patched version of Deltacast SDK 5.19. Please use the drivers in the driver folder of the Ventuz installation director and not the drivers from the download page.
We support the following deltacast products:
Currently not supported are:
Matching Deltacast Drivers with Ventuz Versions
For Deltacast boards, the driver version must match the SDK version perfectly. Use the drivers that are installed in the Ventuz directory, usually at "C:/Program Files" in English windows installations.
The fitting Deltacast Drivers are bundled with Ventuz. For reference, here is a table that matches Ventuz version, Deltacast SDK version and the driver version as displayed in the device manager. A different driver version will be displayed for the Gen1, Gen2 and DVI boards, fortunately they are easy to discern:
|4.05.02||5.16patch||22.214.171.124||126.96.36.199||188.8.131.52||Ventuz 4.05.02 is also compatible with the unpatched 5.16 driver.|
|4.08.00||5.19patch||184.108.40.206||220.127.116.11||18.104.22.168||There is no official 5.18 SDK|
The following boards support 4k modes:
Deltacast uses four HD or 3G links to transport a quarter of the image each. These links are ordinary SDI signals without any additional hidden tagging, swapping two of the links will swap the quarters of the image.
It is not recommended to use two boards and implement keying using one board as input and the other as output.
If there is trouble with a Deltacast keyer if genlock is set to Internal, program the genlock manually to the input port of the background signal or external reference! (Ref)
This only applies to PCIe "gen 1" boards. The info-box you can open with the 'i' button at the board icon will tell you which PCIe generation the board supports. The "gen 2" hardware has this problem fixed and memory pre-allocation is not required.
Sometimes, initializing Deltacast boards will fail with the following error message:
Starting video stream failed. Sometimes this can be fixed by setting Deltacast specific registry keys for 'memory pre-allocation'
This is a problem with Deltacast Gen1 drivers on Windows Vista and later (7, 8.0 8.1 and Windows 10).
This problem arises when the computer is running for some time and can be solved by restarting the Computer. A permanent solution is to set a few Windows registry keys. This can be done by copying the following text into a file named "xxx.reg", and then double-clicking on the file. This will set the registry keys:
Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\DELTA-hd] "PreallocPool0Size"=dword:03000000 "PreallocPool1Size"=dword:03000000 "PreallocPool2Size"=dword:03000000 "PreallocPool3Size"=dword:03000000 "PreallocPool4Size"=dword:00000000 "PreallocPool5Size"=dword:00000000 "PreallocPool6Size"=dword:00000000 "PreallocPool7Size"=dword:00000000 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\DELTA-dvi] "PreallocPool0Size"=dword:03000000 "PreallocPool1Size"=dword:03000000
download this registry file from www.ventuz.com
The problem arises when the Deltacast driver can not allocate enough continuous memory for the video buffers. Using this registry file will reserve 288 MBytes of memory at boot time, making it unavailable for other purposes. You might want to tweak this a bit to save memory:
Each pool is associated to an input or output of the HD/DVI board. The hexadecimal number "03000000" equals to 48 MByte, which should be more than enough for a reasonable amount of HD buffers.
The number of pools to pre-allocate is the number of SDI inputs plus number of SDI outputs. Blackburst reference inputs (genlock) do not count. Example: a 2 in 2 out board needs pools 0 to 3 pre-allocated, a 2-in card needs pools 0 and 1 pre-allocated.
The way these "preallocation pools" are mapped to the individual input and outputs is rather complicated, so it's best to pre-allocate for all available inputs and outputs even if some of them are not used.
The file above will work for a hd-e-key 22 and a dvi-e 20 board. For a hd-elp-d 44 or 80, also set the pools 4 to 7 to 03000000.
|DVS|| Centaurus II (LT)|
DVS boards have been designed for very reliable and stable video IO between the SDI and PC worlds.
Both supported boards use up to 8 PCI-Express lanes. When inserted into a 4 lane PCI-Express slot, data transfer between Ventuz and the board works only at half speed. Please check for correct installation of the card by checking the Video Device Information.
|AJA||Kona / Corvid|
The following AJA SDI Boards are officially supported:
The Corvid 88 is unique as it allows to output a 4K 60Hz stream with key and fill.
The small boards LHe+ and LHi only support one stream with audio.
Our implementation for AJA boards has currently the following limitations:
The Kona 3G (and some other modern AJA boards) can operate in two modes: in Normal mode they have 2 inputs and 2 outputs, can operate 2 streams simultaneously and features an up/down converter. In Quad mode the up/down converter is not available, but the 4 connectors can be switched freely between input and output, allowing for a 4:0 or 0:4 configuration, or everything in between, and 4 streams can be operated simultaneously.
This is possible because the central chip in all SDI boards is an FPGA. This chip contains thousands to millions of hardware logic cells that can be re-wired by uploading a bit-file to form whatever hardware is desired. When programming an FPGA, it is not only a software that is changed, but the hardware itself. Sometimes vendors do not manage to fit all features into the limited logic cells and supply different bit-files for different feature sets.
As Ventuz can not use the up/down converter but greatly benefits from individually switching inputs and outputs, it is strongly recommended to flash the Kona 3G into "Quad" configuration.
The required flash program can be downloaded at our web page. After the end of the flashing process, the software will ask you to power down your computer. You really must power down your computer, or the update will no take effect.
If you have problems installing the driver package, uninstall it completely using the control panel, programs & features. Then install it again. This should make the driver installer re-scan all hardware and install the drivers correctly, as you can verify with the device manager.
|Datapath|| VisionAV-SDI |
The VisionAV-SDI can capture a single channel SDI signal. Currently we do not support audio with Datapath boards.
|Black Magic Designs|| Decklink series |
Blackmagic Design provides several (cost-effective) solutions for SDI output (Fill+Key). The boards have been designed for connecting a tape deck to a PC for recording and playback to tape. Therefore, the product name is Decklink and the boards can either output or input SDI signals - but not both.
Some of the Decklink boards have an internal keyer hardware on-board which make them a cost-effective solution for downstream applications. Please note that Decklink boards do not provide any watchdog or power-fail options!
All models with '4k' in the name are capable of independent input & output. (Ref)
|Datapath|| VisionRGB |
Datapath have developed a sizeable portfolio of capture cards providing HD video capture or HDMI capture capabilites as well as a number of high resolution video capture modes.
Ventuz supports the Vision-AV and Vision-SC series, including the VisionSC-HD4+ board.
|Black Magic Designs|| Decklink series |
As of Ventuz 4.04.00 the input source can be selected in the AV configuration. Only one input can be used at a time.
Ventuz currently supports camera tracking data input from various camera tracking systems vendors - see below.
| Trackmen |
| VioTrack |
German vendor Trackmen develops various camera tracking systems using various technologies. Trackmen uses in all cases the same consistent protocol for tracking data transfer, so all Trackmen systems can be connected to Ventuz, regardless of the tracking technology used. Currently Trackmen collaborates with crane manufacturer Egripment to offer sensorized cranes and pedestals - since these systems use Trackmen technology, they are also supported by Ventuz.
British manufacturer NCam develops Optical Camera tracking solutions that use a lightweight sensor bar attached to the camera to track natural features in the environment, allowing the camera to move freely in all locations - that makes this system especially well suited for shoulder-held or steady-cam shots, or for augmented reality projects outside of the studio.
|Stype Kit||Stype Kit|
Croatian manufacturer Stype offers a sensorizing kit with auto-aim functionality, called Stype Kit, for existing cranes and jibs. The system does not require any additional external sensors or infra-red cameras and there is no need for any physical modifications of the camera crane.
British manufacturer Mo-Sys is a traditional vendor of solutions for remote heads & motion control, broadcast robotics, mechanical and optical camera tracking for AR and VR, and on-set visualization. One of the latest additions to their portfolio is an optical camera tracking system called StarTracker, which features a small sensor camera tracking a cloud of markers placed on the ceiling - that makes it mostly usable for permanent in-studio setups
|HTC Vive integrated through Open VR|
|Oculus Rift integrated through Open VR|
iVGA is a network protocol that can be used to send video streams from Ventuz to a Tricaster. The two configured outputs are reachable under the following address:
1. http://127.0.0.1:49480/AirSend.mpg 2. http://127.0.0.1:49481/AirSend.mpg
|NewTek NDI||Network Device Interface|
NDI, or Network Device Interface, is a technology developed by Newtek that allows creating or receiving video streams over a standard computer network. You can use NDI Streams as an INPUT or create an OUTPUT and broadcast the output via NDI. Please refer to the how to use NDI documentation.
This is rendered to an invisible buffer on the GPU. The purpose of this is to transmit this buffer to the Ventuz Director or other applications, to display a preview of the rendering pipes.
|Windows Media Foundation|
Webcams and other devices often ship with Windows Media Foundation drivers. This is currently only supported for inputs. Some older devices come with Video for Windows or DirectShow driver. Windows Media Foundation wraps these drivers into a WMF filter.