A granular instrument should explain what moves, why it repeats, and where your audio stays.
That is intentional. A fresh install loads the bundled 120 BPM Demo Loop so the Terrain is ready, but Ohms Terrain never auto-plays. Drag a cloud halo, tap empty terrain to create a cloud, tap the sample Play control, or tap Run when you are ready to hear sound.
The small fixed numbered orbs are the actual sample slices used as Markov nodes, and the weighted arcs connect those exact orbs. The larger translucent halos are independent grain clouds. You can create, drag, pinch, throw, lock, or delete up to eight clouds in the standalone app.
By design. Transport starts from the fixed OHMSLOOM seed, so the same state produces the same decisions. Reweave randomizes the transition map without changing that seed. Snapshots, sessions, and takes let you return to a variation you want to keep.
Yes. Session schema 3 stores the quantized motion events, loop duration, quantization, cloud positions, and lock state. The temporary REC and PLAY latches restore off, so opening a session never starts recording or playback by itself.
Drone Horizon allows 4×–32× stretch but caps output at 180 seconds. The source-duration limit therefore depends on the chosen ratio. The app explains the valid duration before rendering, and the offline render remains cancellable.
Only for optional recording and sound-on-sound overdub in the standalone app. Capture starts after your action, stays visibly active, and remains local. Denying permission leaves file import, Terrain performance, sequencing, MIDI, stretch, sessions, and AUv3 use available.
No. Ohms Terrain AUv3 is an output-only aumu instrument. It generates audio in compatible iPad hosts, supports up to four clouds, and has no host-input bus or microphone path. Insert it as an instrument, not an effect.
The planned price is a one-time $29.99 purchase. There is no subscription and no in-app purchase. The product remains marked Coming soon until its App Store listing is approved.
Please do not attach private samples or recordings. Include your iPad model, iPadOS version, host name/version if applicable, audio interface, buffer size, and the exact control sequence that failed.