Ventuz Forum

You can use a ToText node to convert one or more floating point values into a more human-friendly form. This node is controlled by a "Format" string that is a bit cryptic. In your case, the format string "{0:0.0000}" will convert 0.00099999 to 0.0010. The zeros after the ':' are ...

Hi, I assume you are using internal hardware keying. I just checked the code, and I found a bug in Ventuz: When using AJA boards, the button to switch between additive and multiplicative keying is inverted. So in order to get multiplicative keying, you must set it to additive. At least until we fix ...

The SDI input should not effect the Ventuz output framerate unless you check the box "synchronized". On an input that box should only be checked when input and output are genlocked together. On an output, it should always be checked. Above the lists of outputs, there is a box labeled "...

A new machine? Check if you set the "memory preallocation"! That's a couple of registry keys that make the Deltacast board allocate large amounts of continuous memory during the boot sequence. With the default amount of buffers this makes no big difference, but with lot's of extra buffers ...

Ventuz 4.06.01 fixes the problem. Both V1 and V2 boards where effected - in slightly different ways.

There is no official way to boost black levels in certain regions, unfortunately. The edge blending can only make things darker (the color from the ramps is multiplied, not added). The color correction only works on the whole screen.

The new Deltacast 5.17 SDK that came with Ventuz 4.06.00 has a changed behavior when setting the dual link flag. No driver update will be required to fix this. I haven't had the opportunity to check this on a V2 board (with dual link), but I could reproduce something similar on the V1 board (without...

I will try to reproduce the problem. I assume both input signals are 1920x1080 @ ~60 Hz?

If the first input is configured to dual link the second input can not work.

Please check the AV configuration. Click on the sprocket above the Deltacast DVI Board and check the Video Norm settings.

Setting these to HDMI can often resolve a lot of problems.

We talked about this on the phone, did changing the "Video Norm Input X" setting fix the problem?