Recupy

How Recupy Works: From Media to Listener

Technical Details
How Recupy Works: From Media to Listener

Understanding the broadcast chain makes every other setting in the panel click into place. Here is the journey your audio takes:Media + Playlists → AutoDJ → Broadcast server → Mount point → ListenerTh

Understanding the broadcast chain makes every other setting in the panel click into place. Here is the journey your audio takes:

Media + Playlists → AutoDJ → Broadcast server → Mount point → Listener

  1. Media - the music and audio library you upload.
  2. Playlists - the rules deciding what plays when: rotations, schedules, jingle insertions.
  3. AutoDJ - the automatic broadcast engine. It compiles media and playlist rules into one continuous stream, and gives priority to a live DJ whenever one connects.
  4. Broadcast server - distributes the AutoDJ signal to everyone listening.
  5. Mount point - the specific stream address a listener connects to, at a defined format and bitrate.

Stations, roles and access

One Recupy account can run multiple stations, each with its own media, playlists, DJs, mounts and statistics. Team members see only the management screens their role allows, and DJ accounts have deliberately limited access - they can broadcast live, nothing more.

Where everything else plugs in

  • Distribution: the embed player, your public listening page, mobile apps and PWA, plus TuneIn and social integrations - all consume the same mount points.
  • Content: podcasts and listener requests live alongside the stream.
  • Measurement: live listener counts and historical reports observe the chain end to end.

When something misbehaves, walk the chain from left to right: is media present, is the playlist enabled, is AutoDJ running, is the mount defined? Nine problems out of ten reveal themselves on the way.

Rate this