search

peschuster / casparcg-hyperdeck

Hyperdeck "interface" for CasparCG to enable integration in BMD ATEM switchers.
MIT License
28 stars 2 forks source link

ATEM does not recognice that video stopped #6

Open jokiejo opened 3 years ago

jokiejo commented 3 years ago

The HyperDeck emulation ist working fine. I only have the Problem, that it seems as if the ATEM ist noch getting the info, that the playback from a video is finished. So it stays in playback mode and I cannot start a new one immediatly. I first need to manually stopp the video and than select the new one.

The same is true for loding clips from the CasparCG Client. If I just load a new video I cannot start the playback from the ATEM. If I press first "stopp" in the client and than load the video, the video starts fine when I next take the input live.

Is this a general Problem or only at my setup?

I use CasparCG Server 2.3 and ATEM Software 8.5.1

peschuster commented 3 years ago

I don't recall seeing problems like the one you describe.

What are the values of "enableLoad" and "foreground" in your configuration file (clipserver.json). What command do you use to load clips in the CasparCG client? (what command is send to the CasparCG server)

jokiejo commented 3 years ago

Thats my settings in the configuratione file: "enableLoad": true, "foreground": true

The clip in the client has the setting "Freeze on load" checked and I use F3 to load the clip. This sends this command to the server: LOADBG 1-10 "AMB" CUT 0 Linear RIGHT\r\n

With F1 I give the STOPP Comand: STOP OK\r\n

On the ATEM Software Control Panel the Hyperdeck allways stays in Playback and does not resume to "Ready" after a clip is finished. Using the STOP command at the client, puts the Software pack into "Ready" Mode. Same can be done by clicking on the play button again in the ATEM software. (this sends this command to caspar: REQ sg3jk38 202 STOP OK\r\n)

peschuster commented 3 years ago

Thanks for the detailed description. I will try to reproduce this. I already noticed in the past that the ATEM hardware panels and the ATEM software have a different behavior in regards to hyperdeck control. This might also be the case in this scenario.