The PodSlate guide

Everything about recording a remote podcast with PodSlate: setting up once, starting a session, the soundboard, getting the sounds into your DAW, and what to do when something isn't right.

How PodSlate works

In a remote podcast, everyone usually records themselves in their own DAW (Logic, Pro Tools, Reaper and so on) while you talk over a call. The tracks then have to be lined up by ear, and a clap at the start is the usual trick.

PodSlate does it for you. It runs in your browser next to the call. One person hosts a room and the others join with a four-letter code. When the host presses Record, PodSlate presses Record in every DAW at the same moment, using a small MIDI message on each computer. Stop stops them all together too.

It also has a soundboard: sound effects and music everyone in the room hears together, logged to the millisecond while you record, so you can drop them into your DAW in exactly the right places afterwards.

Your audio never goes through PodSlate. Each person's DAW records them on their own computer, as it always has. PodSlate only presses Record and Stop.

Why PodSlate?

There are good services that record everyone in the browser and send you the files afterwards. PodSlate takes a different approach, for people who'd rather record in their own DAW:

  • Most people record a full-quality copy in their DAW anyway. If you're on a call with a mic and an interface, you're probably already recording yourself in Logic, Pro Tools or Reaper as a backup. PodSlate makes that copy the one you use, and lines everyone's up.
  • Nothing squeezed to travel. Call audio is compressed heavily to get across the internet in real time, and anything recorded in a browser is limited to what the browser can capture and has to be uploaded afterwards. Your DAW records straight from your interface, at whatever quality you set: 48 kHz, 24-bit, or higher.
  • Your own setup. Your interface, your plugins, your monitoring, your project template, exactly as you use them every week. No new recorder to learn.
  • No uploads to wait for. The files are already on each person's computer the moment you stop. A dropped connection doesn't touch the recording: the DAW carries on.
  • It starts everyone together. The one thing recording separately used to cost you was lining the tracks up by ear. PodSlate presses Record on every computer at the same moment, so they line up when you drop them in.

Use whichever call you like alongside it. PodSlate never touches the audio: it only presses Record and Stop, and plays the soundboard.

Setting up your computer

Everyone does this once, on each computer they record on. PodSlate walks you through it step by step the first time you open it, and Settings → MIDI → Set up again goes through it again any time. Here's what it covers.

1. A virtual MIDI port

Macs have one built in, the IAC Driver. It just needs switching on:

  1. Open Audio MIDI Setup (in Applications → Utilities).
  2. With it in front, choose Window → Show MIDI Studio from the menu bar.
  3. Double-click IAC Driver, tick Device is online, and check there's a bus in the Ports list (usually Bus 1).
  4. Quit your browser with ⌘Q and reopen PodSlate, so it sees the port.

Windows needs a small free app, loopMIDI:

  1. Install loopMIDI and open it.
  2. Click + at the bottom left to add a port.
  3. Leave loopMIDI running (it sits by the clock), then close every browser window and reopen PodSlate.

Most Linux systems have Midi Through already. If PodSlate can't see it:

  1. In a terminal, run aconnect -l. If there's no Midi Through, run sudo modprobe snd-seq-dummy.
  2. Close your browser completely and reopen PodSlate.
  3. A Flatpak or Snap browser may not be allowed to see MIDI. If so, use your distribution's own Chrome or Firefox.

2. Allow MIDI in your browser

Use Chrome, Edge or Firefox. Safari can't send MIDI yet. When PodSlate asks, click Allow. PodSlate only sends Record and Stop, to the port you pick.

3. Teach your DAW Record and Stop

PodSlate sends a Record note and a Stop note (the very lowest notes, on channel 16, so a keyboard you play can't set them off). Your DAW learns them once. In PodSlate, Test Record and Test Stop (in setup, or Settings → MIDI) send them for the DAW to learn.

Logic Pro
  1. Click on Logic, press ⌥K for Key Commands and search record.
  2. Select the plain Record command under Global Commands (not Record Toggle).
  3. Click Learn New Assignment, then click Test Record in PodSlate.
  4. Do the same for the plain Stop command with Test Stop.
  5. Close Key Commands, arm a track and click Test Record to check.
Pro Tools

Pro Tools uses MIDI Machine Control instead of notes, so there's nothing to learn:

  1. Choose Setup → MIDI → Input Devices and tick your virtual MIDI port.
  2. Choose Setup → Peripherals → Machine Control. Under MIDI Machine Control Remote, tick Enable. Leave the Master side off.
  3. Arm a track and click Test Record in PodSlate. Stop works the same way.
Ableton Live
  1. Open Settings → Link, Tempo & MIDI. Under MIDI Ports, switch Remote on for your virtual port's input.
  2. Press ⌘M / Ctrl+M for MIDI Map Mode, click Arrangement Record, then click Test Record in PodSlate.
  3. Click the Stop button and click Test Stop. Leave MIDI Map Mode.
  4. Recording in Session View? Map the Session Record button instead.
Reaper
  1. Open Settings → Audio → MIDI Inputs, right-click your virtual port and turn on Enable input and Enable input for control messages.
  2. Open Actions → Show action list, find Transport: Record, click Add… under Shortcuts, then click Test Record in PodSlate.
  3. Do the same for Transport: Stop with Test Stop.
Cubase / Nuendo (12 and later)
  1. In the MIDI Remote tab, click + to add a surface with your virtual port as its input.
  2. In the surface editor, click Test Record to add a button for it (and Test Stop for a second one).
  3. In the Mapping Assistant, map them to Transport → Record and Transport → Stop.
FL Studio
  1. In Options → MIDI settings, select your virtual port under Input and click Enable.
  2. Right-click the Record button, choose Link to controller…, then click Test Record in PodSlate.
  3. Do the same for Stop with Test Stop.
GarageBand

GarageBand can't learn MIDI commands, so a small helper app turns PodSlate's notes into its R (record) and Space (stop) keys. PodSlate's setup walks you through it.

Something else

Most DAWs can map a MIDI note to Record: look for MIDI Learn, MIDI Remote, Control Surface or Key Commands. Make sure it listens to your virtual port, start learning on the transport's Record command (not a track's record-arm), and click Test Record. Then the same for Stop.

4. Turn off count-in and pre-roll

A count-in delays the moment recording really starts, so if one person has it on, their file starts a bar or two later than everyone else's. None is best. If you do use one, everyone needs the same length at the same tempo.

5. Sample rate and buffer size

  • Sample rate: 48 kHz for everyone, in the project and the audio device (mic or interface). A mic left at 44.1 kHz in a 48 kHz project records slightly fast and drifts out of sync.
  • Stuck at 44.1 kHz? Some DAWs (GarageBand) can only record at 44.1 kHz. That still works: everyone else stays on 48 kHz and that one recording is converted when you edit. More on 44.1 kHz.
  • Buffer size: the same for everyone. We suggest 64. If anyone crackles, everyone moves to 128 together: matching matters more than going small.
  • Direct monitoring on your interface, if it has it, means no delay in your ears whatever the buffer.

Starting or joining a room

Open PodSlate and you're straight into the studio. A box asks you to start or join a room. You can close it and play with the soundboard first: your board comes with you into the room.

Hosting

Type your name and click Start a session. You get a four-letter code (like KTVQ). Click Copy invite and send the link to your guests. The host presses Record and Stop, and their soundboard is the one everyone shares.

Joining

Click the invite link, type your name and click Join the session. Or type the code in the Join box. Guests never need an account, and never pay.

It works best when you're already on a call together. Everyone keeps the PodSlate tab open while you record. Guests on a phone can join to hear the soundboard, but a phone can't press Record in a DAW.

A test recording first

Before your first real episode (and whenever something changes), record a short test to check everything starts together:

  1. One person turns their speakers on (not headphones).
  2. Start a recording. Someone else counts “1, 2, 3, 4” out loud, or claps.
  3. Stop, then put the speakers person's recording into the other person's project. Their mic also picked up the count through the call, so the same count is in both.
  4. The counts should sit in nearly the same place (the call adds a slight delay). If they're well apart, see the recordings don't line up.
  5. Delete the test takes.

Test recording (bottom of the window) is made for this: it stops by itself after 3 minutes.

Recording

  • Record (the round red button) starts a short countdown, then every DAW starts recording at the same moment. The time shows next to it.
  • Countdown and beeps: click the time display to choose 3, 5 or 10 seconds, and whether it beeps each second (there's no beep on the start itself).
  • Stop (the square) stops everyone. It asks for a second click so a stray click can't end a take. You can turn that off in Settings → Recording.
  • People are shown as tracks under the soundboard. Each take shows there as a timeline of the sounds you played. No audio is recorded within PodSlate: everyone's own DAW does the recording. A green light means connected. R means PodSlate can press Record on that computer.
  • Guests pressing Record and Stop: off by default. The host can allow it in Settings → Recording.
  • If someone's connection drops mid-recording, their DAW carries on recording. PodSlate reconnects them, and stops them as soon as they're back if you've stopped meanwhile.

The soundboard

  • Adding sounds: click + Sound, drop sound files (WAV, MP3, M4A, FLAC, OGG) straight onto the board, or add them from Google Drive. Sounds are kept in your browser for next time and exported exactly as they are, so use WAV, ideally at 48 kHz (why not MP3?).
  • Saved to your account: once you own PodSlate and are signed in, every sound you add or play is also saved to your account (up to 200 MB), so your boards are ready on any computer you sign in on, without finding the files again. A sound you haven't played for 30 days is removed from your account (we email you a week before, and its pad says when). It stays on your own computer, and playing it again saves it again. Your account page shows what's saved.
  • Playing: click a pad, or press 1–0 for the first ten. Esc stops every sound. A playing pad shows pause and stop buttons.
  • Fades: the Fade picker in the soundboard bar sets how every sound fades out when stopped (1, 3, 5 or 10 seconds, or a cut). ⋯ on a pad gives that one sound its own fade. Everyone in the room hears the same fade.
  • Saving boards: Save next to the Board picker keeps the board under a name. Pick it from the Board picker to load it again. Settings → Soundboard can also download a board file to move it to another computer.
  • Adding a set: + Add a set adds a saved board's sounds to the one you're using, keeping what's there. As a guest you can add your own board to the room.
  • In a room, everyone hears the host's board and anyone can play it, unless the host turns that off (Settings → Soundboard). Wear headphones, so your mic doesn't pick the sounds up.

Getting the sounds into your DAW

Everything played during a recording is logged. Click Recordings · Export sounds at the bottom left, pick the recording and choose how to save it:

One WAV

One file the length of the recording, with every sound already in its place. Drop it at the very start of your project. Works in any DAW, and it's the best choice for Pro Tools.

A file per sound

Each sound as its own file, stamped with where it was played. Logic, Cubase and Reaper can snap them all into position at once.

Sounds you stopped early

Choose to fade them out (with each sound's own fade, or one fade for all), cut them where you stopped them, or make no edits and keep the whole file.

Placing a file per sound

  • Logic: drag the files in (on one new track if asked), and with them still selected choose Edit → Move → To Recorded Position.
  • Cubase: drag them onto an audio track, select them all, then Edit → Move → To Origin.
  • Reaper: drag them onto a track, select them all, then run the action Item: Move items to source preferred position (used by BWF).
  • Pro Tools: it can only place them one at a time (Spot mode → the arrow by Original Time Stamp), so use One WAV instead.

Your project's start time

A file per sound is stamped from your project's start. PodSlate uses your DAW's default (01:00:00 in Logic, 00:00:00 in most others). Leave it unless you've moved your project's start. If it doesn't match, every sound lands early or late by the difference.

Record from the very start of the project, with no count-in or pre-roll, so the sounds land where you heard them.

Around the studio

  • Your setup (top right) shows your DAW and MIDI port, with a green light when PodSlate can press Record. Click it for Settings → MIDI.
  • Settings (the cog) has General, Recording, MIDI, Soundboard, Export, Connection and About tabs.
  • Help (the ?) has quick answers, a search, the tour, and the technical log to send us if something's wrong.
  • Every part folds away with its ▾ button, it works in light or dark, and it squeezes down for a small window.

Keyboard shortcuts

Shift R records on every computer and Shift S stops (with Shift, so a stray key can't end a take). T starts a test recording, 1–0 play the first ten pads and Esc stops all sounds. [/] turn the soundboard down and up, E opens your recordings and I copies the invite link. Press ? in PodSlate for the full list.

Free trial and buying

Open beta: until the end of 13 October 2026, everything's free for anyone signed in, with no limit on sessions. After that, the free trial below applies.

  • Sign in (Google, or an emailed link) and your first 3 sessions are free. A session is a room you start: its code works for 12 hours, with as many recordings as you like. Reloading or rejoining the same room code in that time doesn't use another; starting a new room does.
  • That's enough to make real episodes with your guests before you decide.
  • Guests always join free, with no account. Only the host needs PodSlate.
  • After that, PodSlate is £19 once, no subscription. With PodRaven it's £24 for both. See pricing.

Common problems

Recording

Someone's recording didn't start
  1. Their DAW needs a project open with a track armed. It doesn't need to be the front window.
  2. Ask them to open Settings → MIDI and click Test Record. If their DAW doesn't start, the mapping needs doing again: Settings → MIDI → Set up again.
  3. Check the Port in Settings → MIDI is their virtual port (IAC Bus, loopMIDI or Midi Through), not another device.
  4. On the host's screen, a person without a red R on their track can't be started by PodSlate. Their own screen says what to fix.
The recordings don't line up
  1. Everyone turns off count-in and pre-roll (see setup).
  2. Everyone uses the same buffer size (64, or 128 if anyone crackles). A mix put our test recordings about 26 ms apart.
  3. Everyone's project and audio device at 48 kHz. A mismatch on one computer can put its file tens of milliseconds late, and drifting over time.
  4. Nobody has set a manual recording offset or latency adjustment in their DAW. 0 is simplest.
  5. Nobody pressed Record by hand before PodSlate's start.
  6. An Unsteady link (Settings → Connection) means a less precise start: try a wired connection or sitting nearer the router.
Someone lost connection

Their recording carries on in their DAW: the internet isn't needed once it's started. PodSlate reconnects them by itself and, if you stopped meanwhile, stops theirs as soon as they're back. If it doesn't come back within a minute, they can reload the page: they'll rejoin the same session.

How do I check everything lines up?

Do a short test recording with one person on speakers.

I can't hear the countdown beeps
  1. The beeps play through your computer's current output: in your headphones, if you're wearing them.
  2. Check your volume, and that beeps are on (click the time display).
  3. There's deliberately no beep on the start itself.

Sounds

I can't hear the sounds
  1. Click anywhere on the page: browsers keep a tab silent until you do. PodSlate shows Turn sound on when that's the problem.
  2. Check the Vol slider and your computer's output.
  3. Guests hear the host's board: if the host has turned off guests playing sounds, guests still hear them.
Sounds play at the wrong speed

Your computer's sample rate changed after the page opened (plugging in an interface does it). Click Fix sound when PodSlate offers it, or reload.

Putting the sounds in my DAW

See getting the sounds into your DAW. For Pro Tools, use One WAV.

My DAW only records at 44.1 kHz (GarageBand)

That's fine. What matters is that each person's DAW and audio device agree with each other, so their own recording plays at the right speed. Whoever records at 44.1 kHz keeps their file at 44.1 kHz, and everyone else stays on 48 kHz.

When you edit, bring everything into one project and your DAW sorts out the odd one: Logic, Pro Tools, Cubase and GarageBand convert it as it comes in (say yes if asked), and Reaper and Ableton Live play it at the right speed as it is. The length in seconds stays the same, so it still lines up. The sounds from the board work the same way: drop them in and your DAW matches them to the project.

Can I use MP3s (or M4A, FLAC, OGG)?

Yes. Add them like a WAV and PodSlate turns them into a 48 kHz WAV on the spot, in your browser. The pad shows a small MP3 (or M4A…) tag so you know.

  • They still land on time. Every MP3 starts with a short stretch of silence its encoder added (usually around 25 ms). Most MP3s say how much, and PodSlate trims exactly that, so the sound lands where you played it. An MP3 that doesn't say gets the usual amount taken off, which is right for nearly all of them; hover over its tag to see.
  • Quality: the WAV holds exactly what the MP3 had. It can't add back what the MP3 squeezed out, so a WAV from the start is still best for music beds.
  • WAVs are never changed. A WAV you add is exported byte for byte, at whatever rate it is.
Adding sounds from Google Drive doesn't work

Pick the Google account the files are in (Google's window lists your accounts each time, with Use another account), and allow PodSlate to open the files you pick. WAV, MP3, M4A, FLAC and OGG files can be added. If Google shows an error, try again in a minute, or download the files and drop them on the board.

Setup and connecting

The light says the IAC Driver isn't found (Mac)
  1. Audio MIDI Setup → Window → Show MIDI Studio → double-click IAC Driver → tick Device is online, with a bus in the Ports list.
  2. Quit your browser with ⌘Q and reopen it. Browsers often only look for MIDI devices when they start.
  3. If the bus has another name, pick it in Settings → MIDI → Port.
The light says no loopMIDI port is found (Windows)
  1. Make sure loopMIDI is running (by the clock) and has a port in its list. + adds one.
  2. Close every browser window (and exit it by the clock if it's there), then reopen PodSlate.
  3. If the port has another name, pick it in Settings → MIDI → Port.
The light says Midi Through isn't found (Linux)
  1. Run aconnect -l. If Midi Through isn't listed, run sudo modprobe snd-seq-dummy.
  2. Close your browser completely and reopen it.
  3. A Flatpak or Snap browser may not see MIDI: use your distribution's own package.
“Couldn't connect” or stuck on Connecting

PodSlate connects your browsers directly, and some networks block that: work and university wifi, VPNs and some phone hotspots.

  1. Turn off any VPN and try again.
  2. Try a different network for one of you, such as home broadband instead of a hotspot.
  3. Everyone uses Chrome, Edge or Firefox.
A guest is stuck on “Waiting for the host”
  1. Check the four-letter code, or send the invite link again. Easily confused letters like O and I are never used.
  2. The host needs to keep the PodSlate page open. If they left and started again, there's a new code.
It says this browser can't send MIDI

Safari doesn't support Web MIDI yet. Use Chrome, Edge or Firefox. In Firefox, allow the permission prompt; it may ask to add a small site-permission add-on.

Still stuck? Copy the technical log (Settings → About) and contact us.