The port your recording software listens to for its Record command.
Your browser will ask for permission. PodSlate only sends Record and Stop to the port you pick.
Your DAW's Record and Stop (sent as MMC) start and stop everyone, after a 2 s countdown. Send them to a second IAC bus (Bus 2) and pick it here. Logic: Project Settings → Synchronization → MIDI → Transmit MMC. Pro Tools: Setup → Peripherals → Machine Control → MIDI Machine Control (Master). Cubase: Transport → Project Synchronization Setup → MIDI Machine Control Output.
No MIDI ports found. Follow the setup below to add one, then reload this page.
Your DAW will respond to the trigger from any MIDI device, including a keyboard you play on. PodSlate sends the very lowest note (note 0) on channel 16. Keyboards send on channel 1 and drum pads on channel 10 by default, so this is very unlikely to start a recording by accident. If you change the note or channel above, map Record again using Test Record.
For recordings that line up, everyone should use the same buffer size. We suggest 64: low enough that hearing yourself through your DAW doesn't sound phasey, and steady on most computers. If anyone gets crackles or dropouts, everyone moves to 128 together: matching matters more than going small, and a mix of sizes put our test recordings about 26 ms apart. Avoid 32 unless everyone's setup handles it; it can crackle or crash on older interfaces and mics.
If your audio interface has direct monitoring (hearing yourself through the interface rather than the DAW), use it: there's no delay in your ears whatever the buffer size.
Use 48 kHz where you can, and make sure your microphone or audio interface
is at the same rate as your project: a mic left at 44.1 kHz in a 48 kHz project records slightly fast and drifts out of sync.
On a Mac, open Audio MIDI Setup, select your mic, and set Format to 48,000 Hz.
On Windows, open Sound settings → More sound settings → Recording, choose your mic,
then Properties → Advanced and pick a 48000 Hz format.
On Linux, the rate comes from PipeWire or JACK: check it's 48000 there (for PipeWire,
pw-metadata -n settings shows clock.rate), or let your DAW set it.
It delays the moment recording actually starts, usually by a bar or two. If one of you has it on and the other doesn't, your files start that far apart.
None is best, but it still works as long as everyone's delay is the same length at the same tempo. One bar at 120 bpm is 2 seconds, but at 90 bpm it's 2.7 seconds. Everyone in the session sets this up once, on their own computer, and you can each use a different DAW.
One person hosts and sends everyone else a link to join. It works best when you're already on a call together.
You've been invited to session .
Start a room and send everyone the link.
Join with the four-letter code from your host.
Sounds you play while recording are logged to the millisecond, then exported to drop straight into your DAW in the right places. In a session, everyone hears them and anyone can play them. Wear headphones so your mics don't pick them up.
Not connected to the host, so the sounds can't play. PodSlate is reconnecting…
Three sounds are already playing. Stop one, or wait for one to finish.
Drop sound files here (WAV, MP3, M4A…), or click + Sound. They're kept in this browser for next time (and saved to your account, if you own PodSlate, so they're on any computer you sign in on), and played and exported exactly as they are. Got a board file from another computer? .
Keys 1–0 play the first ten pads.
The soundboard sounds from each recording, ready to drop into your DAW in the right places.
aconnect -l. If there's no Midi Through in the list, run
sudo modprobe snd-seq-dummy.PodSlate connects your browsers directly, and some networks block that. Work and university wifi, VPNs and some mobile hotspots are the usual causes.
Safari doesn't support Web MIDI yet. Use Chrome, Edge or Firefox. In Firefox, allow the permission prompt when you click Allow MIDI. It may ask you to add a small site-permission add-on.
Join the list for an occasional email when there's something new: an app, or a big update.
The host has turned off playing sounds for guests. You'll still hear them.
Your free trial has everything in it. Here's what you get:
When you stop it
What was played
Sounds you stopped early
For Pro Tools, One WAV is better. Pro Tools can only place these files one at a time, by hand. One WAV goes in with one drag, everything already in place.
(the recording in your DAW isn't affected)
Guests see it when they join, and your recordings are listed under it.
Saves this computer's setup, so another browser on it won't need setting up.
Recording starting and stopping, and people dropping out, as notifications on this computer while PodSlate's in the background (silent, so the mics don't hear them).
For testing only: your mics will hear it.
Just after it stops, so it isn't recorded. Only on this computer.
Only the host can change this.
When they're stopped. Each sound can have its own: click ⋯ on its pad.
Only the host can change this.
The next time you add from Drive, Google asks which account to use.
No edits: the whole file, so it plays in full in your DAW.
Leave it at the default unless you've moved your project's start time. Used by “a file per sound”.
sudo modprobe snd-seq-dummy.Nothing matches. Try other words, or contact us.