B.Beat & the agent

Everything between your cloud library and the hardware runs through the setshed agent — a small tray app on the computer that shares a network with your B.Beat.

Send to B.Beat

🔌 B.Beat → ⤴ Send to B.Beat pushes the band's library to the device over your network. Safety rails, in order:

  • Firmware check — a library authored on newer firmware than the device runs pauses for your confirmation.
  • Destructive-restore guard — if the library you're sending is missing songs the device has, setshed names them and makes Cancel the big button. A full restore replaces the whole device library; it will never quietly delete songs.
  • Single songs can be synced live — right-click a song → Sync to B.Beat — updated in place with no reboot, or added if it isn't there.

Check & save B.Beat to cloud

⤵ Check & save B.Beat to cloud is how edits made on the device get home. It starts with a two-second check that reads no audio and tells you exactly what changed:

  • New songs — imported whole.
  • Changed audio — only the stems that actually changed are transferred, byte-exact.
  • Changed without touching the audio — a fader, a rename, a folder, lyrics, chords, markers: applied with zero download.
  • Setlists built on the device come across too.
  • Removed songs are only listed. Saving never deletes anything from the cloud.

Save everything is always one click away — use it the first time on a new computer, or whenever the check looks wrong.

The check: new songs, songs whose audio changed, songs changed without touching the audio, and how much it would download instead of the whole library
The check: new songs, songs whose audio changed, songs changed without touching the audio, and how much it would download instead of the whole library

When the B.Beat won't show up

  • Same network — the B.Beat and the agent computer must share a Wi-Fi/LAN.
  • The browser permission (Chrome/Edge): 🔌 menu → 🔓 Let setshed reach this computer → Allow. This looks exactly like "the agent isn't running" — and it isn't; it's the browser.
  • Discovery blocked? Some routers don't forward mDNS. Use ⌨ Enter the B.Beat address manually — the IP is on the device's own network screen.
  • The diagnostic page — 🔌 menu → Why can't setshed see my agent? opens a plain-text report of what your network is actually doing. Paste it into Discord and we can usually tell you the fix in one message.
  • B.Beat Manager open? The device allows one controller at a time. setshed will say so rather than stealing the session — close Manager and retry.

USB export

⇉ Export to USB writes the library in the format the B.Beat's official update path expects — the belt-and-suspenders route when you'd rather not push over the network.