OA CAST VIDEO · DOCUMENTATION

WebTV control operations guide.

A practical guide to channels, RTMP contribution, media readiness, 24/7 scheduling, FFmpeg playout, HLS delivery and broadcast health.

RTMP ingestHLS deliveryFFmpeg24/7 schedulingHealth monitoring
OA Cast Video dashboard
01 · OVERVIEW

OA Cast Video operations model

OA Cast Video is built for always-on WebTV / OTT channels. It combines live RTMP contribution, scheduled or playlist-driven media, FFmpeg processing, HLS delivery and operational monitoring in one control layer.

LayerPurpose
IngestReceive live contribution from OBS, vMix, Wirecast or compatible FFmpeg/RTMP sources.
MediaManage uploaded/available video assets used for 24/7 programming.
ScheduleBuild ordered programming blocks and channel timing.
ProcessingUse FFmpeg for compatible media/output workflows and channel playout.
DeliveryPublish viewer-facing HLS output.
OperationsMonitor channel state, failures, fallback/recovery and audience activity.
02 · CHANNEL SETUP

Create and configure a channel

Create the channel

Set the channel identity and the public/output configuration required for the service.

Add media or configure live contribution

Prepare the content sources the channel will use.

Build the playout schedule

Order assets and programming blocks for continuous output.

Start the channel

Bring the channel online and verify the output manifest begins producing playable media.

Verify viewer playback

Test the public output from a separate browser/device.

03 · LIVE CONTRIBUTION

Connect OBS / RTMP

For live shows, configure OBS or another compatible encoder with the RTMP server/path and private stream key supplied by the channel.

  • Keep stream keys private.
  • Use H.264/AAC settings compatible with the channel profile.
  • Use a 2-second keyframe interval as a common starting point for streaming workflows.
  • Test contribution before the real programme.
  • Confirm the channel switches cleanly between live and automated/fallback states where configured.
04 · MEDIA

Prepare media for reliable playout

Video automation works best when source media is known to be decodable and compatible with the configured output.

  • Upload or register the programme media.
  • Validate duration and media metadata.
  • Normalise/transcode incompatible assets before marking them ready for broadcast.
  • Use thumbnails/titles so operators can identify assets quickly.
  • Keep quarantined/problem files out of the active playout schedule.
05 · SCHEDULING

Build 24/7 programming

Use schedules/playlists to define the order and timing of automated content.

  • Create a playlist or programming block.
  • Add validated media in the required order.
  • Assign schedule times/days as supported by the deployment.
  • Leave a safe fallback path so output continues if a scheduled item cannot play.
  • Check the compiled/active schedule before going live.
06 · PLAYOUT

Keep the channel continuously on air

The playout layer is responsible for turning source media and live inputs into a stable always-on channel.

Operational priorities

  • Predictable media start/stop transitions
  • Fallback when a source fails
  • Watchdog/self-healing around failed channel processes
  • Clear distinction between channel state and actual output health
  • Minimal client exposure to raw FFmpeg/internal logs
07 · VIEWER OUTPUT

HLS delivery

Viewer playback is normally delivered through HLS so browsers/apps can consume a segmented live manifest.

  • Confirm the manifest returns successfully.
  • Confirm new segments continue to appear while the channel is broadcasting.
  • Test playback from outside the server/network.
  • Use appropriate caching headers so manifests and segments remain live-safe.
A channel process can report “running” while the HLS manifest has stopped producing new segments. Always verify the actual viewer transport, not only the control-panel status.
08 · OPERATIONS

Health, watchdog and recovery

A production WebTV service should monitor the complete chain: source → worker/playout → HLS manifest → HLS segments → viewer playback.

  • Worker heartbeat / process state
  • Media readiness and quarantine state
  • Channel process health
  • HLS manifest freshness
  • Segment generation/continuation
  • Fallback and channel restart/recovery path
09 · DEPLOYMENT

Cloud hosted or self-hosted

OA Cast Video can be presented as a managed OACAST service or a self-hosted deployment depending on infrastructure requirements.

ModeBest fit
Managed / cloud hostedTeams that want the platform and media infrastructure operated for them.
Self-hostedOperators that need control over server capacity, storage, networking and broadcast infrastructure.
10 · SUPPORT

Video troubleshooting checklist

IssueCheck
RTMP encoder cannot connectVerify server URL/path, key/credentials, firewall and channel ingest status.
Channel is “running” but no videoCheck HLS manifest and whether new segments are actually being generated.
Scheduled media failsCheck media readiness/validation and the compiled schedule.
Playback freezesCheck segment continuation, source stability and player/network errors.
Repeated restartsInspect server resources, media errors and self-healing/watchdog triggers.

Need help with OA Cast Video?

Use the project/support contact route for provisioning, migration, platform configuration or a custom deployment.

Contact OACAST ↗