CasparCG Server - Decklink IP 100G?

Hello,

Recently, I bought a BM Decklink IP 100G (ST-211) for some other projects, and I was wondering if I could use this card with CasparCG. Will CasparCG treat this BM card as a normal SDI card? Has anyone tried this card with CasparCG before? It will be nice to introduce CasparCG to the ST-2110 infrastructure :grinning_face_with_smiling_eyes::laughing: :sweat_smile: . Please let me know about your experience with CasparCG or the idea of using this card as input / output in CasparCG.

I haven’t tested this particular card, but I see no reason it wouldn’t work. The 10G IP Decklinks do work just fine.

One thing to note is that if you need F+K you will need to setup the K output as an additional port inside the decklink consumer in the config, as the card does not support any automatic key output.

So I need to set it up as a second device for the key? Do you have an example how the config should look?

Oh actually the config file examples suggests this is simpler than I remembered:

<decklink>
  <device>1</device>
  <keyer>external_separate_device</keyer>
  <key-device>2</key-device>
  <embedded-audio>true</embedded-audio>
</decklink>

the key-device and embedded-audio lines may not be required depending on your needs.

Or it could be written in the more verbose

<decklink>
  <device>1</device>
  <embedded-audio>true</embedded-audio>
  <ports>
      <port>
          <device>2</device>
          <key-only>true</key-only>
      </port>
  </ports>
</decklink>

The default config file shows a lot more fields that allow for doing a lot more with these secondary ports or the consumer in general

Thank you, Julusian. I will try to let you know :).

At Yle we have had some issues with the compability of Blackmagics implementation of 2110 NMOS. If I remember correctly it had to do with audio-channels.
Usually BlackMagic works well with other BlackMagic devices.
So please report all findings here because all information will be usefull.
br markus

There are quite ok on the 2110 side, some gaps, so orchestrator side to be solved sometimes, only IS-04/05. 100G implementation is better than 10G. At IBC I could point them to a standard issue with all their implementations : If Register set to manual, the insertion of a second register (often happens for testing in dev env for AMWA spec testing, announcing its presence, breaks the manual mode totally, so device resstart needed).Update should happen soon, alongside stream essences discrete stream addresses for V/A/D on 10G (100G has it from the first firmware), so you have for the moment to support SSM, or to be able of staging the flows (What you can do from custom app or from orchestrator).