Blackmagic Forum

I read over the SDK, but I'm still not sure what is the process of setting up the Duo 2 to use internal or external keying. Can someone please provide the steps or a code snippet that explains this?

I tried the following:
- set SDI 1 to full duplex
- set SDI 1 to external key
- set SDI 1's keyer level to 255

Code: Select all

configuration->SetInt(bmdDeckLinkConfigDuplexMode, bmdDuplexModeFull);
keyer->Enable(true);
keyer->SetLevel(255);

And, the following returns true which confirms the card supports external key.

Code: Select all

attributes->GetFlag(BMDDeckLinkSupportsExternalKeying, &supportsKeyer)

The result is I can see the video fill out of SDI 2, as I would expect. However, I am not seeing a key signal out of SDI 1. Any suggestions of what I could be missing?

When I set SDI 1 to internal key, the result is SDI 2's output is keyed over SDI 1's input signal. So, internal keying seems to work fine.

Just a guess as I don't have a Duo2 to test, but do you need to set SDI1 as an output or should the duplex mode do that for you? Both internal and external keying work as expected with my Extreme3D card but that does not reverse any connections, of course. Also, have you tried feeding the card a reference signal?

Regards,

Dave.

I have code working for 4k Extreme, but the Duo 2 setup is a little different. It requires setting up SD1 for full duplex. At that point, SD1 should become the key signal and SD2 should become the fill. I don't have reference, but that is not required AFAIK.

Hi Jonas,

I'm facing the exact same issue. Did you find a solution ?

Yes. I was advised by support that I encountered a bug in the 10.9.0 driver. I haven't tried the newest 10.9.X driver which may or may not have a fix. For the time being though, I was also told that the 10.8.5 driver does not have this issue with the Duo 2. I haven't dried the Duo 2 with the driver yet, but I plan to.

Hi Jonas, Frederic,

Just confirming that Desktop Video 10.9.3 contains a correction for this issue.

Sincerely,

-nick

Thanks! That's good to know.