Skip to content

How a live radio audio chain works: From microphone to listener

Listen to Story · 6 min listen
Quick Takeaway · Key Summary

The presenter is speaking and the studio headphones carry sound. A listener connects to the station and hears silence. If the microphone works, how can that happen? Broadcast audio passes through a chain of components between the source and the listener's player.

A typical live internet-radio chain runs from microphones and music sources through a mix, optional processing, an encoder, a streaming server and a player. Setups vary, but understanding each role helps with listening and troubleshooting.

Where do speech and music meet?

A microphone supplies the presenter's voice while a computer or another player supplies music. A mixer or broadcasting application combines the sources into a programme mix. Each channel needs the intended input and an appropriate level. A wrong input or clipping at the source cannot reliably be repaired by simply turning up a later stage.

A producer can listen on headphones to hear whether speech is masked by music. Some systems add processing for level consistency; settings depend on the programme and production arrangement.

What happens after the studio?

The encoder prepares the programme mix for network delivery. A streaming server makes that stream available to listeners, and the player decodes it. Icecast's basic setup documentation explains the separate roles of source client, server and listener connection in its system. Other stations can use different software.

Network conditions and player buffering can introduce delay between the studio and the audience. Hearing the studio output does not by itself prove that the internet stream is reaching listeners correctly.

Where distribution fits at RadioTEDU

RadioTEDU offers a concrete way to picture that division. Its RTSAS project page describes RTSAS as the distribution layer between live or automated sources and listeners. The page assigns source acceptance, stream endpoints and ICY metadata to that layer, while describing scheduling and playout as OnAir’s role.

“What should play?” and “Is the chosen audio reaching the listener?” can therefore lead an operator to different parts of the system. The project description does not diagnose a particular listener’s issue or establish that every station uses the same configuration.

📻
RadioTEDU Live Stream

Listen while exploring this story

Tune into campus radio with non-stop independent music and culture.

Sound in the studio, silence on the stream

Return to the opening example. First check whether the headphones are monitoring the programme output or a separate cue mix. If the programme output contains sound, investigate the encoder's selected input and connection. An encoder may appear connected while receiving the wrong or a silent source.

Then check the intended stream on the server and, where possible, play it from a device on another network. If one listener cannot hear it while another can, the device or connection is another possibility. These observations narrow the investigation; they do not prove a particular fault on their own.

The right server, the wrong stream path

A running server does not by itself establish that a player is connected to the intended stream. In Icecast, one server can host multiple streams, each identified by a separate path called a *mountpoint*. Even versions of the same programme at different bit rates can have separate paths.

For example, imagine one server with `/live` and `/backup` paths. They share a hostname but may carry different sources; a listener on the backup path might not hear the live conversation from the studio. These path names are illustrative.

If two devices behave differently, compare the complete stream address with the authorised team, not just the hostname. Finding a wrong path does not mean the whole server has failed. Icecast’s setup documentation describes this behaviour for its own software; it does not document RadioTEDU’s configuration.

What should the team remember after an interruption?

The time, affected stream and what was heard at each point can help the team understand an incident. Avoid putting passwords or unnecessary listener information in the record. Knowing who can respond and how an authorised fallback is used makes decisions easier during a live programme.

Once sound returns, listen to the audience stream again as well as the studio headphones. A chain works when the sound reaches the intended destination across the whole path, not merely when each device appears to be on.

RadioTEDU monthly

The month in podcasts.

Receive podcast episodes from the latest 30 days and upcoming RadioTEDU ticketed events. No daily mail or unrelated announcements.

This consent covers only the monthly podcast newsletter and ticketed event updates. See our privacy notice.

Live RadioTEDU Pick a station and start listening
0:00 0:00

RadioTEDU · Big5 Türkiye Watch Party

RadioTEDU Live Screening: Big5 Türkiye Watch Party. Thursday 19 November, 18.00, D032. Click for free tickets.