fix(playout): strip comments from casparcg.config (parser aborts on them)
CasparCG 2.4.0's config parser aborts at startup (SIGABRT, exit 134) on nearly every launch when the config contains XML comments / blank lines. Proven empirically: identical image + comment-free config = 8/8 stable starts; + commented config = 0/8 (all abort before logging init). Use the compact comment-free form that the known-good image shipped. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
parent
869ae1aa83
commit
3b2f9fe6a0
1 changed files with 0 additions and 7 deletions
|
|
@ -6,11 +6,6 @@
|
|||
<data-path>/media/casparcg/data/</data-path>
|
||||
<template-path>/media/templates/</template-path>
|
||||
</paths>
|
||||
|
||||
<!-- Single logical channel. The output consumer (DeckLink / NDI / SRT / RTMP)
|
||||
is added at runtime over AMCP by the Node shim (playout-manager.js), so no
|
||||
static consumer is declared here. A screen consumer is intentionally
|
||||
omitted — this is a headless server. -->
|
||||
<channels>
|
||||
<channel>
|
||||
<video-mode>1080i5994</video-mode>
|
||||
|
|
@ -18,9 +13,7 @@
|
|||
</consumers>
|
||||
</channel>
|
||||
</channels>
|
||||
|
||||
<controllers>
|
||||
<!-- AMCP over TCP — the Node shim connects here. -->
|
||||
<tcp>
|
||||
<port>5250</port>
|
||||
<protocol>AMCP</protocol>
|
||||
|
|
|
|||
Loading…
Reference in a new issue