Beta testers' guide
Thanks for testing Outrigger. Most testers need the first three parts; the rest are for when something goes wrong.
- What Outrigger is, and what you need
- Install and first setup
- The test plan
- Switching FM-1 firmware: what can go wrong
- Adding a firmware
- Your backups
- If your FM-1 won't boot
- Known issues
What Outrigger is, and what you need
Outrigger is a small touchscreen board that sits on a USB hub next to your FM-1. It lets a MIDI controller with a USB connection play the FM-1 with no computer, and it switches the FM-1's firmware for you, backing it up first.
The homepage has the full shopping list, with links: outrigger.music. In short:
- An ESP32-S3 board with a screen. Tested: Waveshare ESP32-S3-Touch-LCD-1.69 and 3.5. Other ESP32-S3 boards with native USB need a board profile: tell us the board, or send Report this board from the installer.
- A powered USB-C hub that can charge a laptop through it. Outrigger plugs into its host cable, where the laptop would; the FM-1 and controller go in its USB-C data ports.
- Your FM-1.
- A MIDI controller with a USB connection. Tested: Novation Launchkey Mini MK4 37.
- To install: Chrome or Edge on a Mac, Windows or Linux computer, and a USB-C data cable.
The fine print
Outrigger is an unofficial, independent project. It isn't made or supported by M-VAVE or Waveshare. It's a beta: use it at your own risk, and read If your FM-1 won't boot before your first firmware switch.
Install and first setup
Installing is on the homepage: outrigger.music, under "Set up once". Plug your ESP32 into the computer, click Check my board and pick the port Chrome offers. It reads the board and tells you what installing would change, without changing anything. Then click Install. It never erases: your settings and FM-1 backups stay. On a new ESP32 it also sets up firmware switching, starting with M-VAVE stock V15. Add Felucca, Skiff and others afterwards (see Adding a firmware). Your browser downloads stock V15 from the Firmware Hub, and one small file from GitHub, and checks each. If a download fails, it writes nothing and asks you to try again.
If it says your ESP32 has storage we can't read, nothing was installed. That can happen on an ESP32 that ran an earlier beta. Email [email protected] before going further: your backups may be in there.
Then put it on the hub:
- Power first: the charger goes into the hub's charging port. The hub needs its own power: Outrigger runs on it.
- Outrigger goes on the hub's upstream (host) cable or port, the one a laptop would plug into.
- The FM-1 and your MIDI controller go into the hub's USB-C data ports. On the hub we tested, its USB-A ports didn't work (see Known issues).
The homepage's What you need has a picture of the wiring.
Outrigger's Play screen shows a line each for the hub, your controller, the router and the FM-1. All green means notes are getting through.
Wi-Fi: off until you turn on Setup > Remote diagnostics, and then only for a read-only page with Outrigger's status, log and any crash: see Known issues. Updates and downloads over Wi-Fi are coming; see "What's coming" on the homepage.
Updating
When a new build is out:
- On Outrigger, open Settings, then Computer mode, and hold the button. Outrigger restarts with MIDI off, so your computer can reach its USB port.
- Plug it into your computer, open outrigger.music, click Check my board, then Install.
- When it's done, Outrigger restarts by itself and goes back to MIDI. Your settings and backups stay.
Settings shows which build you're running, for example ccbc36d hub+L.
Going back to an earlier build
Not from the website yet: it only offers the latest build. If a new build gives you trouble, email [email protected] with the build shown in Settings, and we'll get you the previous one.
The test plan
Thanks for testing. Please work through these checks once, in order, then use Outrigger normally for a week. Each check says what should happen. Anything else is worth an email, even if it fixed itself.
The checks
- Install. Follow "Set up once" on outrigger.music: Check my board, then Install. Expected: Check my board says what's on your ESP32 and changes nothing. Install takes a couple of minutes, sets up firmware switching, and says it's done. Outrigger restarts by itself.
- First start on the hub. Wire it up as in Install and first setup. Expected: within a few seconds the Play screen shows the hub, your controller and the FM-1 (with its firmware's name), all green.
- Play for 10 minutes. Play the way you normally would: notes, knobs, pads. Expected: every note sounds, with no stuck or dropped notes, and the Router line's count keeps climbing.
- Unplug and replug each device. One at a time: the controller, then the FM-1. Wait for each to come back. Expected: its line turns orange (the FM-1's says "not found"), then green again within a few seconds of plugging back in, and playing works again.
- Restart Outrigger. Unplug the hub's charger, wait 5 seconds, plug it back in. Expected: everything comes back on its own, as in check 2.
- Change a setting. In Settings, change the text size, then restart Outrigger as in check 5. Expected: the setting is still there after the restart.
- Back up your FM-1. On the FM-1 screen, open Backups and hold the button. Expected: it reads the FM-1 twice, writes nothing to it, and says the backup is saved.
- Switch firmware once (a new ESP32 comes with stock V15; add Felucca or Skiff first). Read Switching FM-1 firmware and the switching part of Known issues first. Start with Felucca ↔ Skiff, the tested pair, on the FM-1 screen. Ask us before switching Skiff to stock. Expected: in about a minute the FM-1 restarts in the new firmware. Switch back, and your songs are where you left them.
Then, a week of normal use
Use Outrigger the way you'd use your FM-1 anyway. We're looking for anything that happens only over time: a dropped connection, a freeze, a setting that didn't stick.
How to report
Email [email protected] with:
- the build from Outrigger's Settings screen (for example
ccbc36d hub+L); - your MIDI controller and hub (make and model);
- your FM-1 firmware and its version;
- what happened, and which check it was, if any;
- a photo of Outrigger's screen, if it shows something unexpected.
Good news is useful too: "all eight passed" tells us that setup works.
Switching FM-1 firmware: what can go wrong
Outrigger can put a different firmware on your FM-1: Felucca, Skiff, SLOOP, M-VAVE's own, and most of the Firmware Hub catalog. Two aren't supported yet: Melodee and Tessera (below). This page explains what happens during a switch, what can go wrong, and how to make it unlikely. Read it before your first switch.
What happens when you switch
You pick a firmware on the board's FM-1 page. Its plan page lists, in plain words, everything the switch will do. Nothing happens until you hold the yellow button for two seconds. Then, in about a minute:
- The board restarts and sends your FM-1 into its built-in install mode. The FM-1's screen goes dark. That's normal.
- It checks the FM-1 against its latest backup. If anything changed since (a new song, say), it backs the FM-1 up first. Your very first backup comes from the board's Backups screen, before your first switch.
- It saves the current firmware's songs and settings on the board.
- It writes the new firmware, and reads back every piece it writes to check it.
- It sorts out your songs (next section), then restarts the FM-1 into the new firmware.
MIDI stops while this runs, and comes back when the FM-1 does.
What happens to your songs and settings
- Another version of the same firmware (Felucca 1.6.1 to 1.7.0, say): your songs and settings stay. One exception so far: Skiff 1.x and Skiff 2.x. Skiff 2.0 can convert 1.x songs, but we haven't tested that, so the board starts 2.x fresh and keeps your 1.x songs on their shelf for when you go back.
- A different firmware (Felucca to SLOOP, say): the old firmware's songs go on their own shelf on the board. Then the board clears the old firmware's data off the FM-1, so the new one can't trip over it. The new firmware gets back whatever it had the last time you used it, or starts fresh if this is its first time. Switch back later, and your old songs come back with it. The plan page says "Clears old data" when it does this, and asks for your OK first.
- Tested pairs skip the clearing and work as they always have. So far that's Felucca 1.6.1 and Skiff 1.4. Felucca 1.8.0, Skiff 2.1.1 and stock are being tested now.
- M-VAVE's stock firmware: nobody has mapped how it stores its settings yet, so the board can't keep a shelf for it. Switching to stock clears the old firmware's data (we're still testing how stock takes that); switching away from stock doesn't save stock's settings (the board's full backup still holds them). If presets look scrambled after switching to stock, use System > Reset Patches on the FM-1.
- Skiff 2.x, then stock: Skiff 2.x stores patterns in the area where stock keeps some of its factory resources, and the board can't put those back. Until we've tested what stock does without them, the plan page warns: "Returning to stock may lose stock resources."
Firmwares that aren't supported yet
Melodee and Tessera can write the part of the FM-1 the board uses to tell one FM-1 from another. After that, the board would see a stranger, and your backups would no longer match it. The board won't install them until it can recognise an FM-1 another way. If your FM-1 runs one of them now, switching away still works.
What the board never touches
The board refuses, every time, to write:
- the FM-1's boot area, the small part that lets it always get back into install mode;
- its Bluetooth pairing data, which is also how the board tells two FM-1s apart;
- its factory voices and stock's resources;
- stock's factory data.
What can go wrong
- The connection drops mid-write. A cable gets knocked, the hub loses power, the board loses power. The FM-1 is left with half a firmware, and won't start normally. This is recoverable: see If your FM-1 won't boot. The key is leaving it switched on.
- The FM-1's battery runs out mid-write. Same as above, except you'll need to charge it before retrying.
- Leftovers from another firmware. Some firmwares crash when they find another firmware's saved data. The one proven case is Felucca 0.9 data under Felucca 1.0.1 and 1.0.2, fixed in Felucca 1.0.3.1; erasing the data areas cured it. The board's clearing step erases those areas and more on every untested switch. It can't clear the protected areas above, so a firmware that keeps data there could still trip over leftovers. If a newly installed firmware crashes at start, switch back to the previous one and tell us which pair it was.
Before you switch
- Charge the FM-1 fully.
- Use short, good USB-C data cables, pushed all the way in. Plug the FM-1 into one of the hub's USB-C ports.
- Keep the hub on its power brick.
- Back up first from the Backups screen, if you haven't yet.
- Don't touch anything until the board shows its result. The board's screen says "Don't unplug or switch off the FM-1" while it writes.
Adding a firmware
Outrigger comes with M-VAVE stock V15. Add Felucca, Skiff or any other firmware from the community catalog at mutant.cloud, up to ten in all, from the Firmware library. No Mac tools, and nothing on Outrigger is erased.
How
- On Outrigger, open Settings (the gear), then Computer mode, and hold the button. Outrigger restarts with MIDI off.
- Plug it into your computer with a data cable, and open the Firmware library in Chrome or Edge.
- If you haven't updated Outrigger since this feature came out, click Check my board, then Install, first. Outrigger restarts into MIDI after an install, so go back to Computer mode (step 1) before going on.
- Click Connect, then Choose my Outrigger, and pick the port Chrome offers. On your board shows what Outrigger has, with an Update where the list has a newer version; Available lists mutant.cloud's FM-1 firmwares. If mutant.cloud doesn't answer within a few seconds, the page uses the Firmware Hub's list instead and says so.
- Click Add next to one or more, then Apply under Your changes. Your browser downloads each from the same site as the list and checks it against the list's SHA-256. Then it sends it to Outrigger, which checks it again before storing it. Outrigger's screen shows how far it's got. About a minute.
- Add more if you like. When you're done, tap Back to MIDI on Outrigger, then plug it back into the hub. The new firmware is on the FM-1 page.
What it changes
Only Outrigger's store, and only by adding: your backups, your saved songs and the firmwares already there stay as they are. If the cable comes out partway, nothing is added; try again.
Outrigger refuses an add, and says why, when:
- it already has ten firmwares (its FM-1 page shows ten);
- the add would leave less room than one full backup of your FM-1, which every switch takes first;
- the file doesn't arrive intact, or isn't an FM-1 firmware it can use.
What isn't on the list yet
The library lists these under Riskier, with the reason:
- Melodee, Tessera and the firmwares built on Melodee. They write the part of the FM-1's memory Outrigger uses to tell FM-1s apart.
- SLOOP and most firmwares built on it or on Felucca 0.9 (Clipper and others). SLOOP's fourth sample slot overwrites the same part of the FM-1's memory as Melodee. DX SLOOP, Salt, Hortator, MNM-1, Nauclerus and Hawk-Chua are on the list: by a reading of their source (not yet run on an FM-1), they keep everything where Outrigger clears it on a switch.
- Firmwares without a license, and one whose file doesn't pass Outrigger's checks.
- Files of your own (an author's test build, V16, a firmware the Hub doesn't list). Only the Hub's list for now; your own files come later, behind a setting.
Switching to an added firmware
The same as switching to the three it came with: see Switching FM-1 firmware. Most switches to an added firmware haven't been tested on a real FM-1, so Outrigger clears the old firmware's data first and keeps a copy on its shelf. Switch back and it comes back.
To remove one, use Remove on the library's On your board tab and Apply. It needs an Outrigger build from after 2026-11-05: if there's no Remove, update Outrigger from the home page, and if there's still none, that build isn't out yet. Its saved songs stay on Outrigger. Stock V15 and the firmware your FM-1 runs can't be removed.
Your backups
Where they live
On the board itself, in its own storage, about 12 MB. Not on the FM-1, and not online. The board tells FM-1s apart, so if you use more than one, each gets its own backups.
What it keeps
- Full backups: a copy of all 1 MB of the FM-1, read twice and compared. It keeps your FM-1's first backup ever for good, plus the latest one. A new backup replaces the previous latest one. One exception: a backup that holds the only copy of a firmware isn't replaced. That's a firmware installed some other way, that the board couldn't download again.
- Your songs, one shelf per firmware: every switch saves the current firmware's songs and settings on its shelf. Switch back to that firmware, and they come back by themselves. You don't have to do anything.
- Firmware files: the firmwares you've installed, so switching back doesn't need a download.
There's room for roughly a dozen firmwares plus their songs. Songs are small.
Making a backup
FM-1 page, then Backups at the bottom, then hold the yellow button for two seconds. It reads the FM-1 twice and writes nothing to it. Back up after you change songs or settings, and before trying something risky. (A switch also backs up by itself first whenever the FM-1 changed since its last backup.)
Reinstalling the board keeps them
Installing or updating the board from the Outrigger page never erases your backups or song shelves. The page has no erase option. Only a developer command run from a computer, make flash-store, wipes them, and nothing can bring them back after that.
Coming later
Two things aren't here yet:
- copying a backup to your computer;
- restoring a backup you choose on the board.
For now, your songs come back through each firmware's shelf, and your backups live only on the board. Saving a copy to your computer, including before you reinstall the board, comes later, together with export.
If your FM-1 won't boot
An FM-1 that won't start after a firmware switch can almost always be brought back. The order matters, so go step by step.
1. If the board says the install stopped: don't switch the FM-1 off
If the board's screen says Switch stopped or Install unfinished, with "Don't unplug the FM-1 or switch it off":
- Leave the FM-1 switched on, and leave every cable where it is. Its screen is dark because it's still in install mode. That's what lets the board finish the job.
- If something came unplugged, plug it back in.
- On the board, hold the red Hold: retry … button for two seconds. It carries on where it stopped.
- If Retry fails twice, go to step 3 below. Still don't switch the FM-1 off.
Switching the FM-1 off at this point makes things harder: with half a firmware, it can't go back into install mode by itself, and you'd need the recovery kit below.
2. If the FM-1 is dark but the board says the switch finished
- Switch the FM-1 off and on again.
- If it starts but crashes, or its presets look scrambled, switch back to the firmware you had before, on the board's FM-1 page. Your songs for that firmware come back with it. After a switch to M-VAVE's stock firmware, System > Reset Patches on the FM-1 often fixes scrambled presets.
- If it still shows nothing at all, go to step 3.
3. Tell us, before trying anything else
Email [email protected] right away with:
- a photo of the board's screen;
- the build number (the board's Setup screen);
- which firmware you were switching from and to.
Please don't try other tools or web updaters first. Some of them talk to the FM-1's normal firmware over MIDI. On a half-written FM-1 they fail at best, and at worst leave it harder to recover.
4. The recovery kit: when nothing else works
When an FM-1 shows nothing at all, a small kit can force it into install mode at power-on, whatever state its firmware is in. Then a recovery tool writes M-VAVE's stock firmware back. It brought a fully dark FM-1 back on 2026-10-25.
The parts, about $15, no soldering:
- Seeed XIAO RP2040 with pre-soldered headers. It must be the RP2040, not the RP2350.
- A USB-C to 4-pin header cable. A "USB-C to 4 pin header motherboard adapter cable" with separate 2.54 mm sockets works.
- A USB-C data cable from the XIAO to your computer.
What the recovery looks like:
- Three wires go from the XIAO to the FM-1's USB-C port: data+, data− and ground. The fourth wire, power, is taped off. The FM-1 is switched off while you wire it.
- The recovery tool reads the FM-1 twice to make a backup, checks the two reads match, then writes only the firmware area and reads it back.
- Unwire it, switch the FM-1 on, and it starts on M-VAVE's stock firmware. Then switch to your firmware again from the board.
We'll walk you through it step by step. We'd rather you had this kit before you start testing firmware switches. If you don't have one, tell us before your first switch.
The tools behind it, for the curious: FM-1 Transporter (the XIAO side) and MvaveFM1Unbricker (the recovery tool).
Known issues
A living list. If you hit something that isn't here, email [email protected].
What it has, and doesn't
- Stock V15 comes with it. A new ESP32 gets M-VAVE stock V15 at install. Add Felucca, Skiff and others from the list on the homepage, which comes from mutant.cloud (or the Firmware Hub when mutant.cloud is down).
- SLOOP, and most firmwares built on it or on Felucca 0.9, are left out on purpose. SLOOP's fourth sample slot overwrites the part of the FM-1's memory Outrigger uses to tell FM-1s apart (and the FM-1's Bluetooth address), the same problem as Melodee. It waits for the same fix. Six of the family (DX SLOOP, Salt, Hortator, MNM-1, Nauclerus, Hawk-Chua) keep their data where Outrigger clears it, by a reading of their source (2026-11-04, not yet run on an FM-1), and can be added.
- Add firmwares from the Firmware Hub's list on the homepage, up to ten in all: see Adding a firmware. Files of your own (not on the Hub's list) can't be added yet, and there's no way to remove a firmware yet.
- Melodee, Tessera and the firmwares built on Melodee can't be added yet. They write the part of the FM-1's memory Outrigger uses to tell FM-1s apart.
- Wi-Fi is for remote diagnostics only, and it's off until you turn it on. In Setup, open Remote diagnostics and tap Turn on (restarts). Outrigger opens a hotspot,
fm1hub-setup: join it from your phone and pick your Wi-Fi. Then openhttp://fm1hub.localon the same Wi-Fi for a read-only page with its status, log and any crash. Updates and firmware downloads over Wi-Fi are coming.
Firmware switching
Switching is tested on stock and the Felucca family. Every switch between two different firmwares starts on a clean slate: it clears the old firmware's data from the FM-1 first. A community firmware's songs and settings wait on its shelf in Outrigger and come back when you switch back to it. Stock's settings aren't brought back: they're only in the full backup Outrigger takes before every switch.
- Skiff → stock: ask us first. Skiff saves its patterns into part of the FM-1's memory where stock keeps its factory resources. After many Skiff pattern saves, those resources may be gone, and the board can't put them back. Nobody has tested what stock does without them. Email us before switching from Skiff to stock.
- During a firmware switch the board restarts 2–3 times, and the FM-1 goes dark for about a minute. That's normal. A crash looks different: a safe-mode screen that says where it stopped and "RST to try again". If you see that, email us.
- After a firmware switch, your MIDI controller may stop sending. Unplug it and plug it back in.
- What can go wrong during a switch, and what to do, is on Switching FM-1 firmware.
Setup
- If an install stops partway (the cable came out), install again: it picks up where it stopped.
- An ESP32 that ran an earlier beta may stop at "storage we can't read". Nothing was installed. Email us before going further: your backups may be in there.
- Adding a firmware needs Outrigger in Computer mode, on a build from this page. After an install it restarts into MIDI: go back to Computer mode before adding.
- An FM-1 running M-VAVE's October "Open" firmware plays, but can't be backed up or switched yet. Outrigger recognises it (USB ID 3654:7756, "FM1 Community") and your keys play it. A switch stops before anything is written, and says so. To switch firmware, first put stock V15 back with M-VAVE's FM1 Workbench or the Transporter.
- Installing needs Chrome or Edge on a computer. Phones, Safari and Firefox can't talk to the board's USB port.
- There's no way back to an earlier build from the website. See Install and first setup.
The hub
- One MIDI controller at a time. The ESP32-S3 has room for eight USB connections, and the hub, the FM-1 and one controller use all eight. A second controller shows its name but doesn't play.
- On some hubs, some ports never work. Hubs with more than four data ports usually hide a second hub chip inside, and Outrigger can't reach the ports behind it. On the hub we tested, those were its USB-A ports. Use a hub with four data ports or fewer.
- Unplugging the hub's charger restarts everything. Outrigger runs on the hub's power. Don't unplug it during a firmware switch.
On the board
- The largest text size pushes some lines off the screen. Use small or medium for now.
- Your backups can't be copied to a computer yet. They live on Outrigger only. See Your backups.
Getting help
- Email [email protected] with the build from Settings, what happened, and a photo of the screen. The test plan lists what helps.
- A dark FM-1 can be brought back. If a switch stops, keep the FM-1 switched on and see If your FM-1 won't boot. When nothing else works, the Transporter recovery kit (about $15, no soldering) writes stock firmware back. We'd rather you had one before your first switch.