Set up a Custom RTMP/RTMPS on LiveU Studio (LiveU.tv)
This guide explains how to use LiveU Studio (liveu.tv) to send your live output to a custom RTMP/RTMPS destination (CDN, video platform, or private server) by creating a Publishing Point of type Custom RTMP/RTMPS.
1) Requirements & needed details
From your destination provider (CDN or video platform), gather:
- Server / URL (RTMP or RTMPS): e.g.
rtmp://host/apporrtmps://host/app - Stream name / Stream key: e.g.
channel1orchannel1?token=ABC123 - If required: username/password or token (depends on the destination)
- If the port is not 1935: the specific port (e.g.
:443,:1936)
Server / URL: rtmp(s)://HOST[:PORT]/APP
Stream name / key: STREAM_KEY (or STREAM_KEY?token=...)
Credentials in URL (only if required)
rtmp://<username>:<password>@<host>/<app>
Your Stream key is like a password. Don’t share it or paste it into public tickets.
2) Add a “Custom RTMP/RTMPS” Publishing Point
2.1 Open the Publish tab and “Add or edit publishing points”
- Open your event/project in LiveU Studio.
- Go to the Publish tab.
- Click Add or edit publishing points.
2.2 Select RTMP/RTMPS and add a publishing point
- In the Manage Publishing Points window, select RTMP/RTMPS.
- Click Add publishing point.
2.3 Choose “Custom RTMP/RTMPS” and fill in the fields
- Select Custom RTMP/RTMPS.
- Fill in:
- Nickname: a label to recognize the destination (e.g. “Event CDN”).
- Server / URL: paste your RTMP/RTMPS URL.
- Stream name / Stream key: paste the key/name provided by your destination.
- Save with Save.
If your destination uses a different port, include it in the URL (e.g.
rtmp://host:443/app or rtmp://host:1936/app).3) Select the output bus and enable the publishing point
LiveU Studio lets you choose which output bus (from P1 to P4) is sent to the destination. Select the correct bus, then enable the publishing point.
- On the publishing point card, select the desired bus (P1–P4).
- Enable the publishing point by clicking the card (or the enable/toggle icon, depending on the UI).
4) Start test and publish
- Close the “Broadcasters / Publishing points” menu.
- Click Start test to enter test mode (recommended).
- When ready, start publishing to your destinations using Start publishing & record (or Start publishing).
5) Recommended settings (compatibility)
Settings depend on your RTMP destination. As a safe baseline with high compatibility:
| Parameter | Recommendation | Notes |
|---|---|---|
| Video codec | H.264 | Most compatible for RTMP ingest. |
| Bitrate | Based on upload (e.g. 3.5–6 Mbps for 1080p30) | If unstable, lower bitrate or switch to 720p. |
| Keyframe / GOP | 2 seconds | Commonly required/recommended by CDNs. |
| Audio | AAC 128–192 kbps @ 48 kHz | 160 kbps is a good balance. |
| Rate control | CBR when possible | Helps with ingest stability. |
Keep total bitrate (video+audio) within 60–70% of real measured upload to avoid saturation.
6) Troubleshooting
Connection error / not publishing
- Re-check Server/URL and Stream key (no extra spaces/characters).
- Verify the URL includes the correct path/app (e.g.
/live) as provided. - If the port is not 1935, ensure it’s included in the URL (e.g.
:443). - If the destination requires RTMPS, use
rtmps://and confirm destination compatibility.
Choppy stream / buffering on the player
- Lower bitrate or switch to 720p30.
- Ensure outbound network is stable and not saturated (avoid concurrent uploads).
- Try a closer ingest/endpoint region (if your provider offers regions).
I don’t see anything on the destination platform
- Make sure you started Start publishing (not only Start test).
- Some platforms show preview with delay: wait a few seconds and refresh.
- Confirm the publishing point is enabled and assigned to the correct bus (P1–P4).
7) FAQ
RTMP vs RTMPS: what’s the difference?
RTMPS is RTMP over TLS (encrypted). If available/compatible, it’s preferred.
Do I need to put the Stream Key in the URL?
Usually no: put the URL in Server/URL and the key in Stream name/Stream key. If a provider supplies a single long URL with tokens, follow their instructions (sometimes part of the token belongs in the key).
Can I publish to multiple destinations?
Yes: you can create multiple publishing points (e.g. CDN + social) and enable them as needed, considering bandwidth and resource requirements.
LiveU reference: LiveU Studio Support — Custom RTMP
