Troubleshooting

Common issues with Grainsmith Field on iPhone and iPad, each as symptom, cause, and fix.

I can't find Field in my host's instrument list

Symptom. You added a plug-in in AUM, Logic, or another AUv3 host, opened the instrument list, and Grainsmith isn't there.

Cause. Field is an audio-effect plug-in, not an instrument. Its audio component registers as type aumf (Audio Unit music effect). Hosts list it under audio effects, not instruments.

Fix. Open your host's list of audio effects (sometimes labelled FX or "Audio Unit Effects") and load Field there, in an FX slot. See Install for the full component identity.

Live mode or recording is greyed out or silent

Symptom. The record button is dimmed, or tapping it shows "Recording unavailable on Bluetooth audio," or Live mode produces no sound.

Cause — no input. Field's Live and record features capture an audio input. In an AUv3 host, Field is an audio effect: if nothing is routed into the FX slot that holds it, there's no input to capture. In the standalone app, recording uses the microphone or line input, so it needs microphone permission.

Cause — Bluetooth output. When the output route is Bluetooth (AirPods or any A2DP device), the standalone app switches to playback-only on purpose. Recording over Bluetooth would force iOS into its hands-free profile, which collapses the sample rate and breaks the engine. So while a Bluetooth output is connected, the mic is turned off, the record button dims, and Field stops any recording already in progress.

Fix. In a host, route an audio source into Field's FX slot. In standalone, grant microphone access under Settings → Grainsmith → Microphone. To record, switch output off Bluetooth — use the built-in speaker or wired output. Playback keeps working over Bluetooth at full quality; only recording is held back. Disconnect the Bluetooth device and the mic and record button come back automatically.

No sound at all

Symptom. Field is loaded but you hear nothing.

Cause. Usually one of: the transport is stopped, the level ribbon is down, or no sample is loaded.

Fix. Check three things.

1. Transport. Make sure playback is running from the transport control in the top bar.
2. Level. The level ribbon sets output volume; unity (full) is the top. If it's pulled down, raise it.
3. Sample. Field granulates a loaded buffer. If no sample is loaded, load one from Files or record into the buffer, then start the transport.

In an AUv3 host, also confirm the host track carrying Field isn't muted and its output reaches the master.

AUv3 shows default settings after I reopen it

Symptom. You close and reopen Field's plug-in window in a host and it looks like your tweaks are gone.

Cause. AUv3 hosts destroy and recreate the plug-in UI every time you reopen the window, while the engine keeps running underneath with your recorded audio and parameter values intact. On reopen, Field reads the live engine state back into the UI. If that read is bypassed, the UI can briefly show its compiled-in defaults even though the engine still holds your sound.

Fix. The engine keeps playing your settings regardless of what the reopened window shows first; the UI pulls the current engine values on reopen so it catches up. If the display still looks stale, nudge any control to force a refresh. Your audio and parameters were never lost — only the freshly recreated view had to re-read them.