Slipmat.io Docs

How To Set Up Song Requests ​

During an event your listeners can ask you to play something and send you shout-outs. What they can browse is your own music, so the first step happens well before the event: get your music into Slipmat.

1. Import your music ​

Your Track Collection — https://slipmat.io/artist/collection/ — is where your tracks live. Use Import playlist and pick an export from your DJ software. Slipmat reads CSV, TXT and NML exports from Engine DJ, Rekordbox, Serato, Traktor and VirtualDJ.

Import one big export of everything you own, or keep exports separate — a trance playlist and a house playlist, say — so that at a trance event you can offer the trance one only.

The import uploads, then processes, then it's ready. After that Slipmat quietly matches your tracks against its music database to fill in artist photos and details for the people browsing. That matching takes its time and never holds anything up: a track can be requested as soon as it's imported.

2. Turn requests on for the event ​

Song requests & Shout-outs is in the event form, both when you schedule the event and later under Edit event. Turn it on and you get:

  • Max submissions per listener — 3 by default, 0 for no limit. It counts everything a listener has sent you, so playing or dismissing a request doesn't give them another turn.
  • Anonymous requests — lets people request without an account, from the event's page before you go live. They pick a name and get one request each; voting and audio shout-outs stay for signed-in listeners.
  • Spotify search — off unless you turn it on. Worth it if you can play anything on the spot from Spotify, because listeners can then request tracks you don't own.
  • Tracks people can browse — Track Collection offers everything you own, which is what most artists want. Pick playlists instead to narrow it down to those. If you pick playlists but tick none, there's nothing to browse: people can only write a request in their own words, or send a shout-out.

3. Work the queue during the event ​

Requests live on the Stream Dashboard: the switch on the tool rail opens and closes them, Manage opens the queue.

Each request is Played, Queued (your promise to play it), Unavailable or Dismissed, and anything handled can be reopened. The filters narrow the open list to requesters still in the room (Present), those actively listening right now (Active), people you haven't played anything for yet (Unserved), requests you haven't queued, and requests carrying a shout-out. The same screen holds the per-listener limit, the browsable collection, and Print QR code for a code the room can scan.

Requests close by themselves when the event ends. Resuming an event doesn't reopen them — turn them back on if you want them.