Ventuz Forum

Ventuz 4.03 used a method to determine GPU memory that was limited to 32 bit - and therefore 4 GB of memory. With Ventuz 4.04 we use a 64 bit method and report large GPU memory sizes correctly.

Hi Robert, do I get this right? You switch the DVI Input, like mechanically, from one source to another, right? When you say Ventuz freezes, do you mean it stops working completely or do you mean it stops for a second or so, and then continues normally? I see how using an image pro solves the proble...

This message comes when Ventuz tries to pre-load the video and audio for the loop point. Many streams put audio ahead so that it is already decoded when the video gets decoded. So when the video time is at 100 seconds, the audio time may be already 102 seconds. This is better than the other way arou...

The next Ventuz Version - 4.03.03 or 4.04.00 - will contain a bugfix solving this problem with the software keying.

With the deltacast keyer, you can only choose to either loop through all ancillary data from the input or replace all ancillary data with new ones. It is not possible to mix audio. Although the next Deltacast drivers & SDK (5.15) will have a feature that allows selective overwriting of ancillary...

will be fixed in Ventuz 4.03.02. The problem that was fixed occurs when using "move without warping" to move an edge point outwards. Please note that the method we are using for the "move without warping" feature gets more imprecise the more "warped" the image is around...

I can reproduce this and will investigate.

Will be fixed in 4.03.01
At least if the problem I was able to reproduce is the same problem you had.

I was able to reproduce this. I am working on a fix.

We never tested the extreme 4k, but we tested the predecessor, the "DeckLinkHD Extreme 3", which works fine. I am confident that the latest model will work just as well. Please note that when using any of the DeckLinkHD Extreme to output fill & key, the inputs can not be used. If you n...