Reference

Shortcuts, glossary, troubleshooting, FAQ.

Quick-reference appendix. Bookmark this page — it's where the things you'll forget live: every shortcut, every term, every "why isn't this working" fix.

Keyboard shortcuts

Transport

`Space`	Play / stop
`R`	Record-arm selected track
`M`	Toggle metronome
`L`	Toggle loop
`Home`	Jump to start
`End`	Jump to last clip

Editing

`⌘ / Ctrl`+`Z`	Undo
`⌘ / Ctrl`+`⇧`+`Z`	Redo (also Ctrl+Y)
`⌘ / Ctrl`+`S`	Save
`⌘ / Ctrl`+`C`	Copy clip or sequencer selection
`⌘ / Ctrl`+`V`	Paste
`⌘ / Ctrl`+`D`	Duplicate selected clip
`⌘ / Ctrl`+`A`	Select all (sequencer)
`S`	Solo selected track
`Delete`	Delete selection

Navigation & help

`1`–`4`	Switch view: Arrangement / Session / Mixer / Modular
`?`	Open the shortcuts dialog
`A`–`;`	Play white keys on the on-screen keyboard
`W`–`P`	Play black keys on the on-screen keyboard

Remix Lab

`R`	Open Stem Editor for the focused stem
`Space`	Preview the focused slice (Stem Editor)
`S`	Save the focused slice to your Sample library
`Delete`	Remove the focused slice or warp marker
`Shift`+`Click`	Add a warp marker at click position

Editable focus

Shortcuts without a modifier are suppressed while typing in an input or text area. The Cmd/Ctrl combos still fire — except undo/redo, which yield to the browser's native text-editing history.

Glossary

Arrangement: Linear timeline view — tracks stacked vertically, time running left-to-right.
Session: Clip-launcher grid view. Rows are tracks, columns are scenes; clips fire non-linearly.
Scene: A column of clips in the session view that play together when triggered.
Bus: A summing destination — route multiple tracks into one bus for group processing.
CV: Control voltage. Modulation signal in the modular rack — used to drive parameters, not heard directly.
Gate: A CV signal that triggers envelopes and notes when it crosses a threshold.
V/oct: 1 volt per octave — the standard pitch-CV scaling.
Macro: An assignable knob that drives many parameters at once, with per-target depth.
Freeze: Render a rack or track to a sample in place to save CPU.
Stems: Per-track WAV exports of a finished mix. Pro & Studio tiers.
Warp: Time-stretch audio to fit the project tempo without changing pitch.
Choke group: A group of pads where triggering one cuts off the others — natural for hi-hats.
Mod matrix: A grid of source → destination → amount slots for routing modulation inside a device.

Troubleshooting

Audio context won't start

Modern browsers require a user gesture before audio plays. If the transport seems to play but you hear nothing, click anywhere in the studio once — that unlocks the audio context. On iOS Safari, you must also have your ringer switch on.

MIDI device not detected

Web MIDI works in Chromium browsers; Safari uses our polyfill — accept the permission prompt.
USB-connect the device before opening the studio tab. If you plug it in later, reload.
Class-compliant devices work automatically. Manufacturer drivers (Native Instruments, Ableton Push) may need their host software running.

Export is silent or clipping

Check the master meter — if it reads <-60 dBFS the project itself is silent (likely a muted master or unrouted output).
If the exported file clips but playback didn't, you have an unfrozen modular rack that resampled differently offline. Freeze the rack and re-export.
MP3 export requires Pro+ — Free accounts only get WAV.

Slow CPU / audio glitches

Open the CPU meter (top-right of transport). If it sits above 80%, look for offenders.
Freeze idle modular racks — they're the #1 cost.
Reduce unison voices on Forge Steel instruments. 7 is usually enough; 16 is rarely worth it.
Increase audio buffer size (Settings → Audio). 256 → 512 samples adds 6 ms of latency but halves the per-block overhead.

Browser support

Chrome / Edge / Arc / Brave — full support.
Firefox — works, with reduced MIDI throughput on Linux.
Safari 17+ — works; MIDI uses our polyfill.
Mobile — use the Forge Pocket app, not desktop Forge in mobile Safari/Chrome.

Reporting bugs

Hit the bug-report button (bottom-right of any studio view) to file a report with a one-click screen capture, session log, and CPU trace attached. The same flow runs from /qa/walkthrough with a guided checklist — great for reproducing tricky bugs step by step.

Sensitive data (sample names, project names, MIDI mappings) is included in the report. Strip it on the confirmation screen before sending if you're concerned.

FAQ

Does Forge work offline?: Yes — once a project loads, you can keep editing without a connection. Saves queue and sync when you're back online. Library downloads and collaboration require network.
Who owns the tracks I make?: You do. We never claim a share of your music or its rights. Anything you publish to the community Showcase keeps your ownership — you choose the license per publish.
Can I cancel any time?: Yes. Downgrades take effect at the end of your billing period. Your projects stay accessible on Free; only the gated features (Pro packs, stems export, big storage) lock back down.
Is there a mobile-only workflow?: Forge Pocket can capture and edit standalone, but a full mix and export currently needs the desktop studio. Pocket-only export is on the roadmap.
How are remixes counted toward my plan?: Each remix in Remix Lab counts as one project. Free plan = 3 total (projects + remixes combined). Pro and Studio are unlimited. Warp markers, full note transcription, and live collaborative remix sessions are Pro/Studio only.
What audio file formats are supported?: Import: WAV, AIFF, FLAC, MP3, OGG, M4A. Export: WAV (all tiers), MP3 / FLAC / stems (Pro+).