Start here
How Evenings works
Updated
This page is the map of Evenings: how audio gets in, what decides what's on air, where your recordings go, and where people listen. The question we hear most from new stations is "what's actually playing on my station right now?", so we wrote this to answer it before you set anything up.
Ways in
There are three ways to send audio to Evenings. They all end up in the same pipeline and sound the same to your listeners, so use whichever matches the gear you already have.
- Your browser. Open the Go Live page and use Go Live from your Browser to broadcast a browser tab, your computer's audio or a mic, with nothing to install. Chrome and Edge can do all three. Firefox can only send a mic, and Safari isn't supported yet. Start with your first broadcast.
- RTMP. This is what OBS (free, from the OBS Project, for Windows, macOS and Linux) and Audio Hijack (from Rogue Amoeba, for macOS) use. The server is
rtmp://s2.evenings.co/evenings, shown as Stream Url on the Go Live page, and your stream key goes in the tool's stream key field. RTMP uses port 1935. - Icecast. This is for BUTT (Daniel Nöthen's free broadcaster), Mixxx, Traktor, VirtualDJ, Liquidsoap and ffmpeg and anything else that speaks Xiph.Org's Icecast source protocol. The server is
s2.evenings.coon port8001, and your stream key goes in the mountpoint field. We ignore the username and password, so fill them with anything your tool accepts. The Go Live page doesn't show these Icecast settings yet, so keep this page or the BUTT guide handy.
Your stream key
Your stream key is the only thing that tells us which station a broadcast belongs to. Whatever arrives with your key goes out on your station, so keep it as private as a password. You'll find it under Stream Key on the Go Live page, with a copy button next to it. You can't reset it from the dashboard yet, so if you think someone else has it, email us and we'll issue a new one.
When two things use the same key
Only one broadcast can use your stream key at a time. What happens when a second one connects depends on how it connects:
- A browser or Icecast connection takes over. The broadcast that was already live gets dropped, whatever it was using. We built it this way because encoders sometimes crash and hang on to the connection on their way down, and we didn't want that to lock you out of your own station. You reconnect and you're back on air.
- An RTMP connection is turned away. While your key is live, a new connection from OBS or Audio Hijack is refused and the current broadcast carries on. If an encoder crashed without closing its connection, we drop that connection after 60 seconds with no data, and then you can connect again.
What's on air
Your station plays one thing at a time, and every listener hears the same thing. Here's how Evenings decides what that is:
- You live, or a prerecorded show. Whichever started most recently is on air. If you go live while a prerecorded show is playing, your broadcast takes over and that show doesn't resume. If a prerecorded show is scheduled to start while you're live, it starts on time and ends your live broadcast, so check your Calendar before a long show. Your recording up to that point is still saved.
- Always On. If it's turned on and nothing else is playing, Evenings picks a track from your Library, plays it, and picks another when it ends. It steps aside for live broadcasts and scheduled shows and comes back when they finish. More in the Always On guide.
- Nothing. If no one's live, no show is playing and Always On is off, your station is offline until something starts.
A scheduled show doesn't have to be prerecorded. You can put a live slot on your calendar so listeners know when you'll be on. A live slot doesn't start anything by itself, but when you go live during it, your broadcast takes the show's title and cover. You set show times in your browser's time zone, and the scheduling form shows which one it's using. See how to schedule a live show and how to schedule a prerecorded show.
When one source hands over to the next, listeners stay connected and the audio changes over without them pressing anything.
Where your recordings go
We record every live broadcast while it happens, as a 192 kbps MP3. When you stop, the recording appears in your Library as a track. If you went live during a scheduled show, the first recording from that show takes its title, cover, tags and description. A connection that never sent any audio isn't saved, so a false start doesn't clutter your Library.
Each recording is written to disk on our server before it's uploaded. If the upload fails, we keep the file and retry every few minutes until it lands, because we know a show you've already played is one you can't record again.
Your Library holds every track you have: recordings, plus anything you add with Upload Audio, through your Upload Page, or with the Tracks API. From the Library you can tick Publish to Explore to make a track public, schedule it as a prerecorded show, or leave it for Always On. Published tracks can also be exported to SoundCloud once you connect your account.
Always On picks at random from your whole Library, and it doesn't check whether a track is published. This one catches stations out. If you choose tags in the Always On settings, it only plays tracks with at least one of those tags, so tags are how you keep a recording you'd rather not air out of rotation.
Where people listen
Evenings works like a radio station: everyone tuned in hears the same moment, so someone who arrives halfway through a song hears the second half. Everything goes out as a single 160 kbps MP3 stream, which almost anything that plays audio can handle.
- Your station page, at an address like
evenings.fm/sample-radio. It shows Live whenever anything is on air, including Always On, and lists your published tracks plus anything added in the last 24 hours. Listeners can press Subscribe and leave a phone number to get a text when you go live, at most once a day. - Your schedule, at
evenings.fm/sample-radio/schedule. It lists your public shows. Each one has its own page that listeners can share and use to sign up for a text reminder 15 minutes before it starts. The event pages guide covers RSVPs and text blasts. - Your player URL, shown as Player Url on the Go Live page. It's the raw audio stream, so you can use it in anything that plays audio. When nothing is on air it returns an error instead of audio, so if you build a player around it, have it try again after a short wait.
- Your own site. The API quickstart covers the API, and we have walkthroughs for building a player in plain HTML or in Framer.
Next, set up your station. If anything here doesn't match what you see on your station, email contact@evenings.email and we'll correct the page.