Submit your Fractal unit ID

// How it works

On Windows: install the Fractal USB driver first — get it from fractalaudio.com/support, which has a driver page for each USB unit (Axe-Fx III, FM9, AM4, VP4, the II family). Without it, Windows shows no MIDI ports at all. Close any other MIDI software — Windows gives the MIDI port to one program at a time, so an open editor leaves this page hearing nothing.

Works with the Axe-Fx III, FM9, FM3, AM4, VP4, the Axe-Fx II family, and the original Axe-Fx Standard and Ultra. Connect it over USB (or 5-pin MIDI for the FM3, Standard and Ultra), open this page in Chrome or Edge, press START LISTENING, then IDENTIFY MY UNIT — Fractal units only speak when spoken to, and the reply is what identifies yours. (Opening your Fractal editor for a few seconds works too.)

Once your unit is identified, press CAPTURE MY UNIT. One button runs the whole thing: it reads your current preset plus a sample of others, the routing grid, blocks, and parameters, then maps which commands your firmware supports — all read-only, the same questions your unit's own editor already asks it. Nothing is written and nothing is saved, so your presets are exactly as you left them.

One thing to do first:load the preset you want captured and don't touch a knob before you start. Reading a block asks the unit what kind of block it is, and on FM9 and FM3 that makes the unit reload it — which throws away any edit you haven't saved. Your saved presets are never at risk; only unsaved tweaks sitting in the edit buffer are. Start from a freshly loaded preset and there is nothing to lose.

During a guided bench pass, keep Fractal's official editor open and connected if you need action-marker evidence: a marker only records the action you reported, never wire traffic by itself. To capture actual editor→unit Save activity, use the local Editor Capture Proxy described in the Prober guide.

The last step — mapping supported commands — keeps running for a while after the capture itself finishes; SUBMIT only appears once that's done, so don't close the tab if it looks idle for a bit. Add your email so we can follow up and credit you, then press SUBMIT. That one capture is what turns "should work" into confirmed support for your unit — your rig is a bench we don't have.

// Unit not answering? Work down this list

Permission granted, page listening, IDENTIFY pressed — and silence. The tool names the most likely cause itself once a sweep finds nothing; this is the same list in full, in order of how often we see it:

1. Chrome 152+ on a Mac is deaf to your unit. This one is not your gear. We reproduced it on the bench: the unit answered on the wire — an independent listener saw the reply, and a tempo tick every half-second — while Chrome handed the page zero SysEx frames, with permission granted three different ways. Fractal units speak only SysEx, so on that Chrome every unit looks silent. Quit Chrome completely and reopen it — that alone clears most stuck connections. If it is still silent, update Chrome: this was a Chrome bug and the current version has the fix, which we confirmed on our own Axe-Fx III. Windows Chrome was never affected. Stuck on an old version you can't update? Quit Chrome, then relaunch it from Terminal with open -na "Google Chrome" --args --disable-features=MidiMacUmp and come back to this page.
2. Another app is holding the unit. Fully quit Axe-Edit, Fractal-Bot, AxeBlock EDIT, and any DAW — on the Mac too, not just Windows. Fractal units answer one editor at a time, and an open editor eats the identify reply before this page ever sees it.
3. Check the port list on this page. The listening panel counts ports — but count isn't enough if they're all virtual ports from other gear. Your unit's own name (AXE-FX II, Axe-Fx III, FM9…) has to be among them. Not there? The computer isn't seeing the unit at all: try another USB cable and port, then confirm the unit shows in Audio MIDI Setup → Window → Show MIDI Studio (Mac) or Device Manager (Windows).
4. Power-cycle the unit with USB attached, then press IDENTIFY MY UNIT again once it fully boots. The II family especially brings USB MIDI up in a state some hosts miss until a reconnect.
5. Check the unit's own MIDI settings — I/O → MIDI: SysEx over USB must not be disabled.
6. Still nothing? Reload the page (listening restarts clean) and try once more. If it stays silent, use the support chat and tell us the unit, the OS, and whether its port name appeared in the list — that one detail tells us which half of the path is broken.

// Connecting through 5-pin MIDI (FM3, Axe-Fx Standard, Ultra)

The FM3's USB carries no MIDI, so it connects through its 5-pin jacks — and either path works: a wired USB MIDI interface like the Roland UM-ONE mk2 (Mac or Windows), or a CME WIDI Master over Bluetooth (Mac only — Windows Chrome can't see Bluetooth MIDI, and no iPad browser supports Web MIDI at all). We also recognize the Yamaha MD-BT01 as a Bluetooth option on Mac, though we haven't tested a capture through one — if you have one, we'd like to hear how it goes. The plug rule is the same for all, and it's the step people miss:

1. Cross the plugs over: the interface's OUT plug into the FM3's MIDI IN, its IN plug into MIDI OUT (on a WIDI Master: main plug → MIDI OUT, tail plug → MIDI IN). Both matter — the probe asks questions through the FM3's IN side; with only one plugged in your unit either never hears us or we never hear it.
2. Wired (UM-ONE mk2): plug its USB into the computer — done, skip to step 4. Bluetooth (WIDI Master): first disconnect your phone (or anything else) from the WIDI — it holds one connection at a time.
3. Bluetooth only: on the Mac, open Audio MIDI Setup (Applications → Utilities), then Window → Show MIDI Studio, click the Bluetooth button in the toolbar, and press Connect next to the WIDI Master.
4. Come back to this page in Chrome or Edge, press START LISTENING, then IDENTIFY MY UNIT. The port is picked up automatically — even if you connected it after the page was already listening.
5. Press CAPTURE MY UNIT. Bluetooth MIDI moves at 5-pin speed, so this takes a minute or more — the frame counter ticking up means it's working. Don't close the tab; SUBMIT appears when it finishes.

Own an original Axe-Fx Standard or Ultra? They have no USB at all — 5-pin MIDI only, and you only need one cable: the interface's IN plug into the unit's MIDI OUT. That is the direction your own manual gives for a dump, and this page never sends your unit anything, so the other direction does nothing for us. We recommend the same Roland UM-ONE mk2. Don't use a CME WIDI Master here — it powers itself from the unit's MIDI OUT port, and phantom power on a first-generation jack is unverified on our bench.

The capture is listen-only: your generation predates the read commands newer units answer, so the page transmits nothing at all and simply records what your unit says while you drive it. When the capture starts, recall the preset you want on the front panel, then select UTILITIES → PRESET → Preset Dump and press ENTER— that dump provides the data we need. Tap the matching button on screen as you go, and if time allows, turn one knob, switch a preset, and power-cycle the unit.

If you have a Windows PC, that is the capture we want most.Fractal's original Axe-Edit still runs there, and it is 32-bit so it no longer runs on any current Mac — which is exactly why these units have no modern editor. Open it alongside this page and use it normally for a minute: we then see the real back-and-forth between editor and unit, which is the one thing a listen-only capture cannot show us and the last piece we need to switch Standard and Ultra support on.

// Your gear is safe

The page listens by default and transmits only when you ask it to — and everything it sends is a read-only request: the firmware-version query on IDENTIFY, plus, on units we haven't confirmed ourselves, the deep probe's requests for presets (read from flash without switching), the grid, blocks, and model lists — asked in your unit's own dialect. All of them are questions your unit's own editor asks. It never changes a parameter, switches presets, or writes anything to your unit. Nothing leaves this page unless you press submit.

// Why we built this

We make AxeBlock EDIT, an iPhone and iPad editor for Fractal hardware. Supporting a new unit starts with one byte — the model ID in that header — and we confirm every unit on real hardware before we claim it. Submitting your capture is how the FM3, FM9, and AM4 get confirmed on hardware.

Bloody Finger Software is an independent software studio, not affiliated with or endorsed by Fractal Audio Systems.