An RTMP live stream is ready for an event only when the source, ingest, and one chosen downstream outcome have been tested together. RTMP is often a practical contribution path from a familiar encoder. The remaining workflow must still say who observes the feed, where it goes, and how viewers receive it.
Start with the operational outcome
Choose one first outcome: operator monitoring, a production handoff, recording, a route to a destination, or browser delivery. This prevents a common failure mode—declaring success after an encoder connects while the team has not tested the module that actually matters.
| If the next job is… | Test this after ingest |
|---|---|
| Monitoring | Current picture, intended audio, and activity state. |
| Recording | Start, duration, playback, and the expected stored asset. |
| Routing | Each configured destination and its independent status. |
| Browser viewing | The separately configured player endpoint, not the RTMP URL. |
Use RTMP where the sender supports it
OBS, FFmpeg, and many encoders can publish RTMP. OBS documents its streaming setup in the OBS Studio Knowledge Base, and FFmpeg documents its supported transport options in its protocol manual. Configure the assigned URL and key, then verify the receiving listener sees a publisher and useful media. The transport choice does not settle resilience, end-to-end delay, or viewer delivery; those depend on the full path and its settings.
Keep contribution and playback separate
RTMP can bring a feed into the workflow. HLS or another configured browser-output workflow is what gives viewers a web endpoint. If your question is “why will this URL not play in my browser?”, use RTMP player and browser playback, not an encoder setting.
Pre-event acceptance checklist
- Confirm the publisher address, key, listener, and access rule.
- Send a known programme source and check receiver activity and bitrate.
- Listen for intended audio and inspect video at the monitoring point.
- Run the single downstream outcome that matters for this event.
- Reconnect the sender once and confirm the team’s recovery path.
Callaba receives the publisher, shows current activity, and connects the feed to the selected monitoring, recording, route, or player workflow.
Next steps
Set up the listener with Callaba RTMP Server, follow the OBS guide for a sender test, or use RTMP to HLS for browser-delivery setup.
