How scanner audio is made

ThinLine Radio does not generate radio traffic. An operator puts up an antenna, digitizes the signal with an SDR, decodes it with software they chose, and only then does audio reach a server they run. This page is the chain, the programs, what it usually costs — and why that audio should stay yours.

  1. 1 Antenna RF in the air. Discone, yagi, mag-mount, or a mast on a roof.
  2. 2 SDR tuner USB stick or Airspy turns radio into I/Q samples the computer can read.
  3. 3 Decoder SDRTrunk, Trunk Recorder, and others demodulate P25, analog FM, DMR, NXDN.
  4. 4 Call files Each transmission becomes audio plus talkgroup, radio ID, and time.
  5. 5 ThinLine Radio Ingest, delay, accounts, alerts. Same family of API as Rdio Scanner.
  6. 6 Listeners Web player, iOS, and Android. The app is a client. It is not the radio.
Generated illustration of a rooftop wideband scanner antenna on a short mast
Audio starts in the air. A wideband antenna on a mast, with coax to the radio, is the first piece of a feed — not the app store listing. Generated illustration. Not a photograph of a specific antenna or installation.
Generated illustration of generic USB software-defined radio dongles next to a small computer
Operators typically use USB SDR tuners into a hub or a small PC. Digital trunking often wants more than one receiver. Generated illustration. Not Nooelec, RTL-SDR Blog, Airspy, or any other branded product photo.
Generated illustration of a generic trunking-decoder screen with a talkgroup list and waterfall
Decoder software watches the control channel, follows voice frequencies, and writes one audio file per call. ThinLine Radio is not this program. Generated illustration. Not a screenshot of SDRTrunk, Trunk Recorder, DSDPlus, or any other decoder.

What ThinLine Radio is in this chain

Steps 1–4 belong to the operator. They buy the antenna and the tuners, they pick the decoder, they decide what talkgroups get recorded and how long audio is delayed. ThinLine Radio is the platform that receives those files, stores them, applies the delay the operator configured, and serves the web player and the mobile apps.

That is why a quiet county in the app is almost never “the app broke.” It is an antenna, a dongle, a computer that went to sleep, or an operator who stopped the recorder.

Once those files exist, you choose where they go. Keep them on a server you run — or hand them to a third-party network that did not pay for the roof. Run yours is that choice.