Live Streaming
Members go live from the browser (camera, screen or voice only) with no streaming server: Auto quality for slow connections, live chat, a news ticker, sponsor banners, player ads, and the live saved as a video afterwards.
The Live Streaming plugin lets members go live like Facebook Live or YouTube Live, straight from the browser: camera, screen or voice only. There is no streaming server and no RTMP: the browser records short pieces (2 to 4 seconds) with MediaRecorder, uploads them one after another, and viewers follow the list of pieces in the AIO Player. It is built for slow connections: a live can run on about 150 kbps (Data saver) or 32 kbps (Voice only), and the quality goes down by itself when the upload falls behind.
Going live
- Where: the Live video button in the post box, Go live in the + (create) menu, or the address
/live/new. - Before going live: a title and description, who can watch (Public, Friends, Only me), what to show (Camera, Screen, Voice only), which camera and microphone, and the quality:
- Auto (adapts to your connection) - starts at 360p, measures how long every piece takes to upload, goes down one step when the upload falls behind and back up when the line is free again.
- Data saver 240p - about 150 kbps video + 24 kbps sound.
- 360p about 350 kbps, 480p about 650 kbps, 720p about 1.5 Mbps (the admin decides the highest).
- Voice only - about 32 kbps, for very slow links (an audio-only live with a microphone picture).
- Test my connection uploads two small test files and suggests a preset (for example Upload speed: about 195 kbps. Suggested: Data saver 240p). Below 150 kbps it suggests Voice only.
- A 3-2-1 countdown, then you are live. A post of kind live appears in the feed with a red LIVE badge, and your followers get a notification (Rahim is live now: Evening news).
- Pieces that fail to upload are retried; while the connection is gone they wait in a queue (about the last 90 seconds) and are sent when it comes back.
- Only one live at a time: starting a new live ends the one you left running.
Streaming from OBS
There is no RTMP address to send to. In OBS press Start Virtual Camera, then choose OBS Virtual Camera as the camera on the Go live page. Scenes, overlays and screen layouts made in OBS go live that way.
The studio
While you are live the page shows the preview with what viewers see, and a panel (on a phone a bottom sheet you pull up):
- Live bar: time, viewers now, the quality now, upload kbps and the line health (good / slow / trouble), microphone and camera on/off, copy the link, End live.
- News ticker: messages one a line, they scroll right to left one after another like a TV news crawl. Label (LIVE, NEWS...), position (bottom or top), speed and colours. Start ticker / Stop at any time.
- Sponsor banner: a lower-third with an optional logo, a text, a link and a button (Order now). Show banner / Hide at any time.
- Live chat: read and answer comments.
The ticker and the banner are drawn by the viewer's page over the video, so they cost the streamer no upload and every viewer only a few bytes.
Watching
/live/<number>- the AIO Player follows the live with a small request per piece and stays a few seconds behind live. The ticker, sponsor banner and floating reactions stay on the picture in full screen.- Live chat beside the player (under it on a phone) with reactions 👍 ❤️ 😂 😮 👏 🔥 that float up over the video.
- Viewers now counted by a heartbeat every 20 seconds (the streamer is not counted).
- Data saver button for viewers when the admin turns on Data saver copies: FFmpeg then makes a 240p copy of every piece. It is chosen by itself when the browser asks to save data or the connection is 2G.
- Live now on the home page (only while someone is live), the Live videos page
/live(live now + recent lives), the side menu, and a Live now row on the Smart TV app. - The browser starts muted when it does not allow sound by itself; Tap to unmute turns the sound on.
Ads during a live
- Player ads from the Ads plugin (the same contract as Live TV:
aio_player_adswith where = live-stream): a pre-roll before the live starts, and a mid-roll every N minutes of watching (live has no end, so a clock runs), after which the player jumps back to the newest picture. - Sponsor banners from the streamer (see the studio) work even when the Ads plugin is off.
- With the AIO Player off, lives play in the browser's own player without player ads.
After the live
- With FFmpeg: the cron job Join and compress live recordings joins the pieces into one H.264 MP4 (at most 720p by default, CRF 28) and the post becomes an ordinary video post.
/live/<number>then leads to the post. - Without FFmpeg: the pieces stay and the live replays on its page from the pieces.
- The streamer can edit the title, delete the recording (the post goes too) or go live again.
- Keep recordings off: the pieces are removed when the live ends; the post stays as Was live. With Remove recordings after N days, old recordings are removed by the cron job.
Admin
Admin → Plugin pages → Live Streaming
- Live now / Ended: title, member, length, viewers (now and peak), size, recording state; Stop a live, Make the video now, Delete (live, recording and post).
- Banned from going live: ban a member by username (their running live ends at once) and lift the ban.
- Storage used and whether FFmpeg is found.
Live Streaming settings
| Setting | Default | What it does |
|---|---|---|
| Who may go live | Every member | Every member / Verified members only / Members whose package includes it (Pro) |
| Longest live | 120 minutes | A package can set a lower limit (live_stream.max_minutes) |
| Highest quality | 720p | Auto never climbs above it |
| Piece length | 3 s | 2-4 s: shorter is closer to live, longer suits slow lines |
| Largest live | 1024 MB | The live ends when it gets this big |
| Keep recordings / remove after | on / never | |
| Compress recordings, CRF, largest saved size | on, 28, 720p | FFmpeg settings for the saved video |
| Data saver copies for viewers | off | A 240p copy of every piece (uses CPU on every piece) |
| FFmpeg path + Test FFmpeg | the site's setting | Shows the version and whether VP8 and H.264 are there |
| Live chat, Live now row, notify followers | on | Notifications go to at most 1000 followers by default |
| Ticker defaults | red, white, 80 px/s, bottom, LIVE | What a new ticker starts with |
| Pre-roll, Mid-roll every N minutes | on, 10 | Player ads from the Ads plugin |
Packages (Wallet → Pro → features): Go live (live_stream.go_live) and Longest live (live_stream.max_minutes). Admins can always go live; banned members never can.
Cron jobs: End lives that stopped sending (every minute: no piece for 60 seconds ends the live), Join and compress live recordings (every 2 minutes, one live at a time), Clean old live pieces (hourly).
Data use
Measured in Chrome with its built-in test camera (a simple moving picture; a real camera uses up to the preset's figure):
| Preset | Target | Measured upload |
|---|---|---|
| Voice only | 32 kbps | - |
| Data saver 240p | about 175 kbps | 112 kbps |
| 360p | about 380 kbps | 177-185 kbps |
| 480p | about 700 kbps | 473-477 kbps |
| 720p | about 1.5 Mbps | 532-551 kbps (the test camera is 640x480) |
A viewer downloads the same amount (or the Data saver copy), plus about 0.3 KB of JSON per piece for the playlist, chat and overlays.
Browsers
Going live needs MediaRecorder: Chrome, Edge, Firefox, Opera, Samsung Internet, and Safari 15+ (Safari records MP4, the others WebM). Watching needs Media Source: every desktop browser, Android, and iPhone with Safari 17.1 or newer.