Frequently asked questions

The community firmware is where active development happens: it adds features (extra mod destinations, FM, quality-of-life) and fixes ahead of official builds, and is widely considered stable. Official firmware is more conservative. Most engaged users run community firmware; just read the release notes and back up your SD card before flashing.

Feature availability and even where things live can shift between firmware versions (official vs community, and across community releases). If a mode "vanished," you likely changed firmware lines or the combo moved — check the release notes for your exact version and the Shortcut Finder. Reflash a known-good version if needed.

Set the input source to the built-in mic, arm an audio/sample track to record, set monitoring/threshold, and hit record. The usual snag is leaving the input set to line/USB or not arming an audio track — the mic won't capture into a synth track, only an audio/sample track.

Song mode is the live, loopable clip-launch view; the Arranger lets you lay clips out on a timeline for a fixed arrangement. You build/perform in Song mode and commit a structured arrangement in the Arranger. Many "how do I make a full track" questions are really "switch to the Arranger."

Map the controller to the Deluge and use note input into the sequencer; for true step entry, use the Deluge's grid for steps and the controller for pitch. Exact step-mode behavior depends on firmware — community firmware has improved external MIDI note/step handling, so check your version.

Load samples across the pads/keyboard with zones (root notes + ranges) for a multisample, or assign one sample per row for a kit. The web Kit/Preset Builder lays this out for you and writes the files to the right SD layout, which avoids a lot of manual XML/folder fiddling.

Keep SAMPLES, SYNTHS, KITS and SONGS in their standard folders and avoid renaming files a song references (it'll break the link). Back the card up before firmware flashes. A tidy, consistently-named sample library on the card prevents most "missing sample" and load issues.

Functionally the same instrument; the OLED is much easier to read menus/values on, the 7‑segment relies more on memorized shortcuts. Newer units are OLED. If buying used, the 7‑seg is fine if you'll learn the combos, but most people prefer OLED for menu-heavy work.

Yes — the Deluge sends/receives MIDI and you can learn CCs to parameters; pitch handling (including master/transpose) is configurable. Specifics improved in community firmware, so if a CC mapping or pitch feature isn't there, check whether you're on a firmware version that added it.

Use a kit/synth with two sample sources and modulate their levels in opposite directions (e.g. an LFO or the mod matrix), or use the granular/looping options for smoother blends. There's no single "crossfade knob" — it's built from the mod matrix, which is why it's a common how-do-I question.

Edits are per-instance — changing one kit row's synth or one clip's sound doesn't propagate to others. To reuse a tweaked sound, save it as a preset (save the synth/sound) and load that preset into the other clips/rows, or copy the sound. There's no global "apply everywhere"; presets are the propagation mechanism on the Deluge.

Song view holds your clips (rows of instruments, columns of sections); the Deluge community firmware also added a grid launch mode for triggering clips Ableton-style. Because the grid is a community-firmware feature, the best written reference is the community firmware docs (delugecommunity.com) for your exact version, not older manuals. If "grid" looks different from a tutorial, you're likely on a different firmware line.

Generally yes — the Deluge is open-hardware and fairly serviceable, and Synthstrom has historically offered repair/refresh support (confirm current availability before counting on it). On a used unit, test every pad/button and encoder, the screen, the SD slot (a flaky slot is the most common issue), and that it boots and updates firmware. Open hardware + an active community means parts/fixes are documented.

First check the physical lock switch on the side of the SD card (slide it toward the contacts to unlock). If it's already unlocked, the card likely needs reformatting as FAT32 (not exFAT/NTFS) — back up its contents and reformat. If it keeps happening, the card is probably failing; swap to a known-good FAT32 card. A genuinely write-protected card will also stop the Deluge saving songs.

The Deluge is synth-engine first — it ships with factory synth/kit presets but not a large built-in sample library, so most owners load their own samples and community kit packs onto the SD card. Start from the factory presets and the community firmware's content, then build your sample folders on the card (see the kit/preset builder tools in the list).

For a MIDI synth, run the Deluge's MIDI OUT (DIN or USB) to the synth's MIDI IN, set a Deluge track to MIDI mode on the matching channel, and play/sequence it. For an analog module, use the Deluge's CV/Gate outputs (assign a CV track, set V/oct and gate). If nothing sounds: confirm the channel/port, that the track is MIDI (not synth), and that the module is set to receive on that channel.

No — swing/groove isn't an LFO destination. Swing is a timing/quantize setting you dial in per clip (the groove/swing amount), so set it there rather than trying to modulate it. For evolving feel, automate other parameters with the LFO/mod matrix and adjust swing manually, or vary it between sections.

Synthstrom open-sourced the Deluge firmware, and the community firmware builds on it well ahead of (and beyond) the official releases — DX7-style FM synthesis, extra mod/automation options, UI and workflow improvements, and bug fixes — while staying compatible with your existing songs. Stock firmware is what ships from Synthstrom; most of the active scene runs the community build. You can flash back and forth, so it's low-risk to try — just back up your SD card first.