Thu Dec 13, 2018 5:39 am
Although the ATEM implements the camera protocol which is documented in the camera manual for anyone to implement, the ATEM adds some extra functionality to "remember" what values have changed, where those change were initiated from something connected to the ATEM (BMD software, panels, 3rd party things using the official API).
This allows multiple client applications and control panels to "listen" for updates coming back from the atem when any individual app or panel makes a change, so they can all display the current setting.
The data must be there in the UDP stream but as Daniel says, not support and not guaranteed to follow a pattern the you expect to see.
I do know with the API that you have to register a callback to say what changes you are interested in updates for, otherwise nothing is "broadcast". I remember from writing my API based PowerShell interface for camera control that I could also change the frequency that data was resent to cameras (this overwrites any values that you might manually set through the camera interface).
There is no data ever read back from the camera though.
Regards,
Ian Morrish
Video Integrated Scripting Environment
(Windows PowerShell with ATEM driver + more)
https://ianmorrish.wordpress.com