The issue occurs on two different systems: Perhaps relevant: during normal playout (before the freeze) clips sometimes show multiple 'Received EOF' messages. After the clip which freezes the clips that follow in the logs no longer show ffmpeg_input Received EOF and Shutting down ffmpeg_input messages Only when we turned on trace level in the logs we found some pointers that something changes when the channel freezes. If you would look at only the standard logs you would think CasparCG was still playing out fine on the frozen channel. Strangely however, incomming commands from a connected node.js client (connected before the freezing) are executed seemingly fine by casparcg according to the logs. Overlays like html templates also freeze.Ĭommands (like PLAY, CLEAR, INFO) issued from a telnet client connected after the freezing do nothing (no response at all, empty commands still give a 400 ERROR). If we play the same clip manually in a seperate channel everything also goes fine. are included).Īll clips that freeze have been played out without issue many times before. The complete composited output of one channel freezes (ie. We haven't succeeded in manually reproducing the problem. It doesn't happen often Once every few days on a 24/7 playlist. We are experiencing complete freezing of channel output when playing a list of clips.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |