- Posts: 317
- Joined: Tue Nov 06, 2012 3:16 am
- Location: portlandia
In playing with this, I've come to the conclusion that the paradigm for how chromakey is implemented is wrong (at least for me).
I come from a VFX/post background (not live TV) and I don't really have a received wisdom about upstream & downstream keys, so my assumptions may be completely wrong.
But if I were writing the software, each of the main camera inputs would have the ability to key out the color and attach a background from either another camera source or the media pool behind it.
That way the camera inputs stay as the primary layer and the BG is ancillary, not the other way around. Then you could have custom key settings per camera instead of the one-size-fits-all approach in the Atem software. Since macros can already switch all this stuff instantly, it doesn't seem like you'd really be adding much in the way of system overhead to make this happen.
The way it's currently implemented, it's cumbersome to switch camera inputs and backgrounds without writing macros (that can easily break) to make this happen. Am I missing something?