Ventuz Forum

Each time we launch the runtime, live inputs initialisation is not certified. Could you fix it please? Very very annoying.

R

Your problem seems to be related to a driver problem with Deltacast boards since Windows Vista. We will update the Ventuz documentation in the next release with the following text:



Sometimes, initializing Deltacast boards will fail with the following error meessage:

Starting video stream failed. Sometimes this can be fixed by setting Deltacast specific registry keys for 'memory preallocation'

This is a problem with Deltacast drivers on Windows Vista, Windows 7 and Windows 8.

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. Please make sure that the file does not have a hidden ".txt" ending:
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. If a board has 2 inputs and 2 outputs, pools 0 to 3 need to be pre-allocated. Blackburst reference inputs don't count.

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.

Wow !
Seems to be something you should put in Ventuz Configuration Editor with a GUI.