The managedstreaming. upstream interface accepts audio from any Icecast-compatible encoder. managedstreaming. is part of managedradio. and is also available as a standalone service or in combination with your existing setup. For networks, a fully redundant edge service is available, scaling to large audiences and supporting a long-term custom domain.
| 💡 New to managedstreaming? If you do not have an account yet, request a free trial at here. The setup below works the same way for trial and production accounts. More Infos and pricing you find on our website: deliver.media/managedstreaming and the complete service description at: deliver.media/managedstreaming/servicedescription |
Contents
Supported encoders
The upstream interface uses the Icecast 2 source protocol. Any encoder that can act as an Icecast source client connects to managedstreaming without modification. Encoders known to work include:
Recommanded:
- BUTT (Broadcast Using This Tool), free, Windows, macOS, Linux
- BUTTM, the mobile companion for iOS and Android
- MusicMaster NexPlay / MMPlayer
- StereoTool with the Icecast output module enabled
- FFmpeg
Other options:
- Mixxx
- RadioBoss
- SAM Broadcaster
- Radiocaster
- Liquidsoap
If your preferred encoder is not on this list, check whether it supports the Icecast 2 source protocol. If it does, it will work with managedstreaming.
Recommended encoders
We recommend BUTT for desktop streaming and BUTTM for streaming from a phone or tablet. Both are reliable, well-maintained, and free. Dedicated step-by-step setup articles:
- BUTT (Windows, Mac, Linux): Stream to managedstreaming using BUTT
- BUTTM (Windows, Mac, Linux): setup article coming soon.
Connection parameters
When your stream is provisioned, you receive a credentials sheet containing every value listed below. Keep this sheet alongside your encoder configuration. If anything is missing, contact support before configuring the encoder.
| Field | Description | Typical value |
|---|---|---|
| Server type | Protocol the encoder uses to connect | Icecast 2 |
| Server host | Hostname of your assigned upstream endpoint |
[customername].streaming.deliver.media, for example media1.streaming.deliver.media
|
| Port | TCP port for the source connection | 8000 |
| Mount point | Path identifying your stream on the server | Provided on provisioning, typically /station_format_bitrate
|
| Username | Source account name | source |
| Password | Source account password | Supplied on provisioning |
| Codec | Audio format the encoder sends | MP3 or AAC or LAME |
| Bitrate | Constant bitrate of the encoded stream | 96 to 320 kbps (up to 1,5 Mbit available on request) |
| Sample rate | Sample rate of the encoded stream | 44.1 kHz or 48 kHz |
| 💡 Tip: Only one encoder may connect to a given mount point at a time. If you operate a backup encoder, coordinate failover externally or request a secondary mount point from support. |
Verifying the stream
Once your encoder reports a connected state, confirm that the stream reaches the public listener URL. Open your streaming server in a browser, for example https://[customer].streaming.deliver.media (such as demo.streaming.deliver.media), and locate your stream. You should hear your live audio within a few seconds of the encoder connecting.
You can also check the listener statistics in the deliver.media portal to verify that the server registers your encoder as an active source.
Troubleshooting
If the encoder fails to connect, work through the items below before contacting support.
- Connection refused or timeout. Your local firewall or corporate proxy is blocking outbound traffic on the upstream port. Allow outbound TCP on the port listed in your credentials sheet.
- Unauthorized or 401 response. The source password does not match. Re-enter the password exactly as supplied. Passwords are case-sensitive and contain no leading or trailing whitespace.
- Mount point in use. Another encoder, or a previous session of the same encoder, is still connected. Stop the duplicate session and reconnect.
- Connected but silent. Audio input is not reaching the encoder. Check the input source selection in your encoder and verify that input levels are visible on the meter.
- Connection drops repeatedly. Bandwidth or latency on the local uplink is insufficient. A stable 128 kbps stream requires roughly 200 kbps of headroom on the upstream link.
Still stuck? Write to hello@deliver.media with your account name, the encoder you are using, and a copy of the encoder log. We will help you get connected.
Comments
0 comments
Please sign in to leave a comment.