Troubleshooting

No sound. Check the top of the list: did the audio device change? Zammoth reports device trouble in the status line and, when it matters, as a durable chat note ("⚠ no audio output — pick a device in Preferences (⌘,) ▸ Audio"). Also check the track's ⏻ power (a powered-off track is out of the graph entirely), mute/solo states, and whether the Loop Deck currently owns playback.

A take recorded silent. Zammoth checks finished takes and tells you ("the take on ‹track› is SILENT — check the input + gain", or "…went SILENT before the stop — did the input device disconnect mid-take?"). If the audio device changed mid-take, the recording was necessarily discarded and chat says so; re-record once the device settles.

The CLIP lamp is red / amber. Red = the master actually clipped (true peak over 0 dBTP). Amber = hot: over your deliverable ceiling but not clipping. Click the lamp to acknowledge. The fix is usually the master limiter (or asking the engineer "why is the master clipping?" — it can see exactly which chain stage is responsible via the Δ chips).

A plug-in crashed the app. On the next launch Zammoth checks the crash log; if it names a plug-in that was loaded, that plug-in is quarantined automatically and will not load until you Trust it (its box's right-click, or the scanner table). Quarantine is the protection working, not a fault.

The engineer isn't responding / "could not start the engineer". The agent runs in a helper process; if it can't start, the status line says why (it distinguishes "exited with an error" from "hung during startup"). It reconnects automatically on your next agent action; a wedged run is force-recovered about 45 seconds after you press ■. If the composer won't send at all, read the sentence at the foot of the console: it names what's missing (a key or a sign-in), and clicking it takes you there.

"Your Anthropic API key was rejected" / "out of credit" / "rate limit". These come from your Anthropic account, not your project: replace the key in Preferences ▸ Agent, top it up at console.anthropic.com, or give a new account's low rate limits time — they rise with use. "Anthropic is overloaded" or "had a server error" means nothing is wrong on your side; try again in a minute. "Can't use the model you picked" or "data-retention setting" is about the model: pick another in Preferences ▸ Agent (or the composer's model word) — Opus 5, the default, is the safe choice. The full list is under Account and Updates.

A run made the mix worse. It shouldn't have kept it: runs revert automatically to their best measured pass and say so. If you still don't like the result — undo run or ⌥⌘Z, or hold a/b to compare against the pre-run chains. (⌘Z does not take back a run's mix moves; see Undo and the agent.)

"It looks stuck" during separation / Auto Mix / pitch correction. These are staged background jobs (the ENGINEER cell names the stage: tagging, profiling, building, applying, rendering). Stem separation genuinely takes minutes on first use.

Reverb tail cut at the end of an export. The bounce currently ends at the arrangement's end — leave a little arrangement space after the last clip if the tail matters. (Track freeze keeps tails correctly.)

Reporting a problem. Help ▸ Report a Problem… copies a diagnostics block (version, OS, CPU, audio device, buffer, measured latency — never project content) and can reveal the log folder. Help ▸ Show Logs opens the same folder; the engineer's own log lives there too.