xOTTConfiguration map and safe defaults
Find each setting, understand its scope and verify one change at a time—from global policy to a single subscriber output.
On this page
A safe order for a new installation
- Finish installation, activation and administrator access; save a backup and verify time.
- Connect one service/account or one manual input. Use its real region and route.
- Save one channel, keep Original / copy, choose compatible input tracks and inherited/main placement.
- Verify actual HLS playback before enabling additional outputs or optional processing.
- Create one collection, publish one package and test one Access Line.
- Add events, workers, metadata enrichment or automation only after that baseline works.
Use the first channel walkthrough if any of these terms is new.
Where a setting belongs
| You want to change… | Open… | Verify… |
|---|---|---|
| Time zone, event-date display, UI defaults | Settings → App | The visible label changes, not the schedule instant. |
| A source login or account route | Services / Proxies | Correct account, proxy scope and one source test. |
| All future service defaults or event slots | Services → Service Outputs | Scope, saved rules and any explicit per-stream override. |
| One stream’s input/tracks/logo/output/placement | Saved Library → stream settings | Saved effective config and controlled restart where required. |
| Actual encoding profiles/capacity | Settings → Media Processing | Host diagnostics, current profile revision and one encoded output. |
| Device/runtime preferences | Settings → DRM Services | Supported adapter/action and actual account playback. |
| Download storage and worker folders | VOD → Storage / worker storage controls | Mounted writable root, free space and a small test job. |
| What viewers can watch | Collections → Packages → Access Lines | Published package, entitlement and output permissions. |
| Operator alerts | Settings → Notifications | Saved destination and delivered test. |
| Domains/listeners/TLS | Server/network settings | Preview/job log and externally reachable generated URL. |
Do not fight an override
A saved stream’s explicit override can take priority over service and global defaults. Worker placement, processing-device choice, upstream proxy and public delivery mode are separate decisions. A worker pin is not a proxy setting; a GPU selection is not a worker pin. Check the effective values before assuming a global save changed every existing runtime.
Video, audio, subtitles and output formats
Start with a working single video quality. Source preferences choose existing tracks. Transcode explicitly re-encodes one output profile. HLS/DASH, continuous TS and UDP/RTMP/SRT have different multi-track capabilities. Probe exact input track IDs again after source/account migration. See track selection and processing.
Recovery is not one switch
| Mechanism | Purpose |
|---|---|
| Saved-stream recovery | Restores desired running saved channels after supported lifecycle events. |
| Runtime retry | Retries recoverable source/process failures with configured delays and limits. |
| Ordered source backups | Optional verified alternate saved linear inputs for one output identity. |
| Event auto-start | Admits eligible armed scheduled events, respecting slot assignment. |
| Same-event account failover | Opt-in equivalent live event recovery after confirmed account failure. |
Unlimited attempts do not mean a stream should be shown healthy or that a failed proxy can be ignored. Avoid changing retry/timeout/live-edge parameters without observing the actual failed layer.
Routes and public URLs
Keep source routing service/account-specific. SmartDNS does not replace the host resolver. A Public Base URL advertises an address; it does not create DNS, a certificate or a firewall rule. Direct worker delivery requires its media origin to be reachable and browser-scheme compatible. Follow networking setup before changing production listeners.
Media storage and downloads
A native worker destination moves supported download processing/storage. A generic SFTP/rclone destination can still need main-server staging. Per-download subfolders stay inside approved roots. Existing files do not move just because a destination/root default changes. See VOD setup.
Customers, lines and permissions
A Customer is a contact record; an Access Line carries playback credentials and subscription policy. Creating another customer does not repair a missing collection member. Save channels, review collection health, publish packages, then verify the actual line. Staff credentials must not be used in the native player.
After any meaningful configuration change
- Reopen the form and check the saved effective values.
- Confirm the affected host and current main/worker release.
- Watch actual media/guide/subscriber behavior, not only a successful Save toast.
- Check current logs and telemetry freshness; distinguish unknown from a real zero.
- Keep working output identities and tokens unless rotation is intentional.
- Roll back the specific setting or restore the tested baseline—not the whole server by guesswork.