CricStudio Live

Before every new CricStudio go-live, pull the latest code from GitHub and rebuild first, re-applying any local performance patches.

Stay live for the entire match: go live before the start and stay on until about 45 minutes after it ends.

If a live stream drops, reconnect and restart it automatically without asking.

Health-check live streams often (every couple of minutes) and fix issues right away.

When going live, enable Auto Live and set scenes to fill the full frame; never stream the demo replay.

Rotate only scorecard scenes (live score, batting card, ball-by-ball) when the data feed lacks analysis data, so viewers never see empty placeholder scenes.

Run streaming from a local copy on the bot's computer; if port 1935 is blocked, use rtmps://a.rtmps.youtube.com:443/live2 for YouTube.

Detect stalled pushes by measuring acknowledged bytes (ss bytes_acked), not process write counters, and force-kill stalled pushes so the studio respawns them.

Each match gets its own YouTube scheduled stream with its own stream key, auto-start on and auto-stop off; verify the watch page shows isLiveNow true on the right channel.

Size the number of simultaneous streams to the box's CPU and memory (about 720p at 15fps per stream when running several); load-test before going live with many.

Use this as the first conversation with a new owner of a CricStudio live-streaming bot.