Firmware and backups
What a firmware update on the FM3 actually changes, what it leaves alone, and the backup that means none of it can cost you anything.
It does not erase your presets
Customised presets survive a firmware update. That is the easy half of the answer.
It can change how they sound
Updates revise amp models. A preset is a list of settings, so a preset built on a model that changed will sound like the new model afterwards. This is what the release notes are for, and why they are worth reading before rather than after.
Saving after an update can lock a preset to that version
The one that costs people something. Once you re-save a preset on new firmware, it may no longer load on the old firmware. A backup taken before the update is the only route back, which is why the backup and the update are one procedure rather than two.
It does not update the factory presets
New factory presets show up sometimes, but as a separate download you install yourself — through Fractal-Bot, the same way as firmware. A firmware update on its own leaves them where they were.
The part that makes everything else safe
Fractal-Bot's RECEIVE tab automates this. As on the rest of the line, presets are stored in banks — so "back up my presets" means backing up all of the banks, not the one you happen to be looking at. Fractal-Bot also offers a single-preset backup when that is all you want.
- 1
Back up all the preset banks
Not just the one you are working in. There is also an option to back up an individual preset, which is the right tool when you are about to experiment on one sound rather than update the unit.
- 2
Back up the SYSTEM
One file holding every custom setting in the SETUP menu. Without it a restore returns your sounds with none of your rig's configuration.
- 3
Name the folder by date
Fractal-Bot asks where to put the files, so decide in advance. The convention Fractal recommend, and that touring techs use, is yymmdd — 260829, then the unit's name. Sorting by name then sorts by date.
- 4
Write down the firmware version
Keep a text file next to the backup saying which firmware was installed when it was made. This sounds fussy until the day you need to know whether a backup will load — and since presets saved on newer firmware may not open on older, that day comes.
Doing the update
Fractal-Bot again, and a backup before any major update.
- 1
Quit everything else first
Close the editor, any DAW, and anything else touching audio or MIDI. They will fight Fractal-Bot for the connection.
- 2
Download and unzip, but do not double-click the firmware
The archive holds documents as well as the firmware itself, which is a SysEx (.syx) file. Extract it somewhere you can find again and leave it alone — double-clicking a .syx hands it to whatever else on your machine claims that extension. Fractal-Bot will ask you where it is.
- 3
Read the release notes
They say what changed and warn you about anything you need to know first. If you are skipping several versions at once — which is allowed, any version to any version — read the notes for the versions in between too. They ship with every release.
- 4
Then run Fractal-Bot
Three steps, self-explanatory, with the instructions built into the app. Windows needs a driver first, from the downloads page for your unit; macOS does not.
Restoring is not the same shape as backing up
Backing up is automated. Restoring is not — you send each file from the backup set over individually, waiting for one to finish before starting the next. If a System file is one of them, reboot the unit immediately afterwards. Fractal-Bot will remind you, but people miss it.
Do not do this over 5-pin MIDI
Backing up and dumping are not supported over MIDI at all. You can send files to the unit that way, but the transfer rate makes it a genuinely bad idea. Use USB.
If an update fails, try again before you panic
If the unit still boots, simply repeat the update. If it keeps failing, delete the download and fetch it again — a truncated file looks exactly like a broken unit. A different USB port or cable is the next thing to try.