ATEM transport control
Posted: Sun Mar 02, 2014 9:59 amHI, I know the following is not listed as a feature for ATEM, I want to know how to control a video server (EVS XS) from an ATEM panel.
Two ways are normally used: a device protocol like SONY RS422 or VDCP, this would require a certain setup on the server, like a schedule of clips with the first Cued and Still to which the ATEM will send the appropriate Play command. On the ATEM there should be eventually a way of linking the physical input with the communication channel, i.e., when input # is switched on PGM output, the Play command will be sent for the # device. The most used protocol to control video servers is VDCP and it could use RS422 or Ethernet to interconnect the ATEM and the device. My layout is a single server playout, so a single RS422 port on ATEM might be used. However Ethernet could have advantages before wiring DB9 and in case of multiple server devices to be controlled.
The other way is using GPIO, a contact closure when input # is on PGM output made into ATEM will signal the start for the server, another contact closure on ATEM will signal the end of Play when another input # in brought on PGM. And so on, this also is a standard connection but it requires more attention on wiring and GPIO health.
In my opinion the latter is easier to implement because is not a software dependant solution, implementing VDCP consistently is sometimes not easy, so even in case of GPIO's it would be great to make the ATEM like a MCR vision switcher.
What do you think?
Two ways are normally used: a device protocol like SONY RS422 or VDCP, this would require a certain setup on the server, like a schedule of clips with the first Cued and Still to which the ATEM will send the appropriate Play command. On the ATEM there should be eventually a way of linking the physical input with the communication channel, i.e., when input # is switched on PGM output, the Play command will be sent for the # device. The most used protocol to control video servers is VDCP and it could use RS422 or Ethernet to interconnect the ATEM and the device. My layout is a single server playout, so a single RS422 port on ATEM might be used. However Ethernet could have advantages before wiring DB9 and in case of multiple server devices to be controlled.
The other way is using GPIO, a contact closure when input # is on PGM output made into ATEM will signal the start for the server, another contact closure on ATEM will signal the end of Play when another input # in brought on PGM. And so on, this also is a standard connection but it requires more attention on wiring and GPIO health.
In my opinion the latter is easier to implement because is not a software dependant solution, implementing VDCP consistently is sometimes not easy, so even in case of GPIO's it would be great to make the ATEM like a MCR vision switcher.
What do you think?