Your stream address

One address for any encoder — OBS, Moblin, Larix, Streamlabs. We take the feed, show you a preview, and fan it out to the platforms when you say so.

You stream once to our address — TEASE receives it, burns in your captions and fans it out to every platform. No third-party dashboards involved.

The address lives in the Stream tab → RTMP button in the header.

Any encoder works

The receiver is plain RTMP and does not care who publishes. Anything that can push RTMP will do:

From	Examples
Phone	Moblin, Larix Broadcaster, PRISM Live Studio
Desktop	OBS Studio, Streamlabs, vMix, XSplit
Hardware	any encoder with an "RTMP URL" field

Don't tie yourself to one app

The same address goes into your phone or into OBS. Publishing from two places at once is not supported — whoever connects last owns the stream.

Connecting

Stream tab → RTMP → Copy. The key is already inside the address, so it is ONE line — no need to fill two fields.

Paste it into your encoder's address field and hit "go live".

The preview window above the cockpit comes alive within a couple of seconds. No page refresh needed.

Happy with the frame and the captions? Hit "Go on air" in the cockpit. Only then does the feed reach the platforms.

If your encoder wants server and key SEPARATELY

Some do (certain OBS versions, for instance). The card shows server and key as separate values right below the address field — use those.

No app needed: the browser camera

Don't want to install anything? Stream tab → Камера (Camera) button.

Turn the camera on. The browser asks for permission and you see your own frame. This is local — nothing has been published yet, so fix your light, angle and sound here.

Go live. The frame reaches our ingest, and from there it is exactly like the phone: preview, overlays, the «В эфир» button in the cockpit.

You can switch camera or microphone mid-publish: only the track is replaced, the publication is not interrupted.

Two sources can run at once

The browser camera and your app (Moblin/OBS) are SEPARATE inputs — they do not evict each other. When both publish, the card offers a choice of what goes to the platforms: the app, the browser camera, or whichever arrives.

That is also the safety net: if the phone loses signal, the frame moves to the camera on its own and the show does not drop.

Browser caveats

The panel must be on HTTPS and camera permission must be granted — otherwise the browser hands over nothing.
Resolution adapts to your connection automatically: on a weak uplink the browser lowers the picture instead of tearing it. The card shows what actually arrived.
Close the tab and the publication ends. For a long show, the phone or OBS is the safer source.

Signal ≠ on air

Two different states, and the panel never conflates them:

"signal" (blue) — we are receiving your feed but NOT fanning it out. You are the only one seeing it.
"on air" (green) — we are fanning out. Turned on by the cockpit button.

The split is deliberate: the first frame, while you are still fixing a caption or your angle, must not reach your viewers.

What the preview window tells you

The window itself plays the composed frame — the same thing your viewer sees (if you built a scene; otherwise the raw source). That is what the program chip means: such a picture lags by a second or two, and that is encoding, not lag. Your own camera with no delay is in the Camera card.

Overlaid on the frame are facts about the incoming feed, not about the fan-out:

signal 4:12 — how long we have been receiving (live ticking timer);
1920×1080 — resolution;
60 fps — frame rate, exactly the one you set in your encoder;
2.5 Mbps — real incoming bitrate;
camera — the signal comes from the browser, not from an encoder.

Bitrate is your diagnostic instrument

If the picture stutters in your encoder and the bitrate in the panel dips at the same moment, the bottleneck is your uplink. If the bitrate holds steady and the picture still breaks up, it is the device (heat, camera, codec settings).

Rotating the key

The "rotate key" link in the address card. The old address stops being accepted immediately, so copy the new one into your encoder right away — otherwise your next attempt to go live hits an auth refusal.

Rotate it whenever the address could have reached someone else's screen: during a screen share, in a screenshot, in a chat. That is also why the key is masked by default inside the card.