Deltacast Genlock

Hi,

I'm encountering some errors when trying to genlock my capture/playback card, DELTA-12G-elp-h 2C, driver 6.2.1. Using dCare I can see that the card is receiving genlock and can output a genlocked test signal but when I start Axi (2024.1.0) the preview monitor connected to the card isn't receiving it. Also when I then connect a camera to an input on the card it starts showing this error in dCare "Cannot retrieve the genlock offset 0. Result = 0x00000019 (VHDERR_BADREFERENCESIGNAL)" The rest of the devices in the chain are all receiving genlock and I've been in contact with Deltacast support , who say the card is testing fine so the problem is being caused by Aximmetry. Can you help solve what is causing this?

Thanks

tony_the_bone

Eifert@Aximmetry

Hi,

The Deltacast SDK/driver needs to be version 6.21 or higher, but the exact version 6.21 should provide the best compatibility with Aximmetry. Driver version 6.2.1 is too old.

If you have the correct driver, do you still get the error message when the genlock is not connected to the Deltacast card? Also, do you see the input in Aximmetry? Additionally, what is the frame rate of the genlock and Aximmetry's frame rate? You can find more information on Aximmetry's frame rates here: https://aximmetry.com/learn/virtual-production-workflow/preparation-of-the-production-environment-phase-i/inner-workings-of-aximmetry/rendering-settings/#frame-rate

Warmest regards,

tony_the_bone

Sorry that was a typo, driver version is 6.21.

I get the same error message with no genlock connected to the card, but only when I have an input connected, which appears fine in AXI. The card is set to output 2160@50, genlock is 1080@50, Axi is rendering at 2160@50, as is the camera connected to the input, I've also tested with the camera at 1080@50. I can see that my tracker and camera are receiving sync, and I have no issue with the tracking, but my outputs from the card are not genlocked according to the info overlay on the preview monitor output. When AXI starts I can see it takes control of the Deltacast card, and changes the genlock to BlackBurst from Local, but whats causing the error, and why are the outputs not genlocked?

Thanks

Eifert@Aximmetry

Hi,

The letter "G" here:

Only shows genlock if output #2 is set to sync:
Deltacast Genlock

Note that we always suggest using output #1 as your preview and output #2 as the video sent out to production:

Also, the VHDERR_BADREFERENCESIGNAL error indicates "Bad genlock signal or unsupported standard", I would suggest setting everything 1080@50, especially the resolution in the Video Outputs window. Most of the time the resolution shouldn't matter, as most devices can handle different phase locks, but maybe not in this case.

If the error still happens and there is no output image, do you have everything in the ProcessorLoad in the green?
Deltacast Genlock

Also, note that it is sufficient to genlock the camera and the tracking devices to keep them in sync. Connecting genlock to Aximmetry's capture card doesn't provide any additional benefit in this regard. It cannot even confirm if the camera or the tracking is truly in genlock. Genlock is a hardware feature that forces the hardware to output frames at precise intervals matching the genlock signal. It does not influence how these frames are subsequently received or synchronized, as it cannot embed any additional information in the frames.
When Aximmetry's capture card is genlocked, it outputs at the pace of the genlock signal, and that's all the genlock can do. This is helpful in a multi-machine setup with Aximmetry so that different computers output frames simultaneously without varying delays.

For more information on genlock, please visit:https://aximmetry.com/learn/tutorials/for-studio-operators/syncing-and-genlock/

Warmest regards,

tony_the_bone

The letter 'G' does not appear on the SDI output. I have set the project to 1080@50, all the signals are set to this as well, CPU and GPU load are all in the green. I'm trying to configure a multimachine setup so need to get genlock working. The card is receiving genlock until I start Axi, and then monitoring in dCare I can see the "Genlock Status Mask" change from 0x00000000 to 0x00000002 which according to Deltacast support means genlock has been lost, this is with no inputs connected as the "VHDERR_BADREFERENCESIGNAL error" is related to the input according to Delta support.

TwentyStudios

You don’t really need to genlock the Deltacast output, even in a multi machine setup. The signals will be re-clocked in the video switcher anyway, so at best genlock will save you one frame of delay in the total signal chain, which isn’t very noticeable at 50p. Everything will still be aligned and synced up without genlock.the important part is that your tracking system and cameras are genlocked, and that happens outside the Deltacast card and Aximmetry.

Eifert@Aximmetry

Hi,

We have identified the source of the issue, and the next version of Aximmetry will likely resolve the genlock problem with your Deltacast card.

Warmest regards,

Eifert@Aximmetry

Hi,

The issue you were experiencing with Genlock not being accepted with Deltacast cards in certain cases has been fixed in version 2024.2.0, which was released today. Please note that the 2024.2.0 BETA version did not contain this fix.

Additionally, the Deltacast SDK has been upgraded to v6.25.1. So you must update the Deltacast driver to v6.25.1 in order to use your Deltacast board with this version of Aximmetry.

NOTE: For genlocking Deltacast capture cards, interlaced and progressive genlock signals are not interchangeable.

Best regards,

Deltacast Genlock

Cookie consent