Help

Quick start

  1. Find a sound

    Use Sounds to search the available models and built-in presets.

  2. Start deliberately

    Choose Play or a named sound action. Nemisindo never autoplays audio.

  3. Shape the result

    Adjust the labelled controls, load a Built-in preset, or choose Randomize controls to make another valid starting state.

  4. Capture locally

    For continuous sound, start playback and choose Record. For a triggered model, choose Record first when you need the opening transient, then play the events you want. Capture begins immediately, so a brief pause before the first event will be part of the recording. Choose the red recording control again to stop, then choose Download WAV.

Model controls

Continuous

Sound that keeps playing

Choose Play once, adjust controls while listening, then choose Pause. Try Static for a continuous texture or Beep for a repeating tone.

Triggered

Sound that plays as an event

Choose Play or one of the model's named actions each time you want an event. Use Pause to stop active or pending events. Try Impact Lite or the multi-action Switches model.

Presets and randomization

A built-in preset is a named set of control values for one model. Select one from Built-in preset, or open it directly from the Sounds catalogue. Preset links include a query such as ?preset=Bad%20Radio, so they can open the matching model with that starting state ready.

Randomize controls chooses a valid value inside each control's supported range. Moving or randomizing a control changes the selection to Custom and removes an old preset query from the address, because the named preset is no longer the active state. Double-click a slider to restore that control to the value from the last selected built-in preset.

Loading a preset or randomizing controls does not start audio. Sound remains under your control until you use a sound action.

Record and download

  1. Choose when to record.Leave a continuous sound playing, or choose Record before a triggered action to capture it from the beginning. Capture starts immediately; trigger the sound when you are ready.
  2. Capture the sound.The timer and recording control's Stop state confirm capture. Sound controls can stop or cancel playback without discarding the recording.
  3. Choose the recording control again.Capture also stops at the time limit reported by the interface.
  4. Wait for local encoding.Choose Download WAV when the file is ready.

Troubleshooting

Continuous playback is reflected by the Play/Pause control. On triggered models, Play stays ready for another event. Recording is reflected by the enabled Record/Stop toggle, elapsed timer, and Download WAV control.

Sound does not start

Sound must begin from Play or a named action; moving a control alone will not start it. Check that the tab and device output are not muted and keep the device volume comfortable. If the audio session closes, reload the page and use a sound control again.

Sound paused after switching tabs or apps

Browsers and operating systems can interrupt Web Audio. Return to the model and use Play or a named action again. Pending triggered events are cancelled rather than queued for later playback.

If recording was active, the interrupted recording is cancelled. Start the sound again, then begin a new recording.

The Record button is unavailable

Start a continuous sound before recording it. Triggered models can start recording before their first event. Recording also needs browser support for AudioWorklet, Web Workers, and downloadable object URLs. When a required capability is missing, the explanation appears below the recording control even if sound playback still works.

A preset link was not found

The model reports the missing preset and leaves its default state ready. Visit Sounds to find the built-in presets currently available for that model and open a fresh link.

The browser reports an unsupported feature

Use a current version of Chrome, Firefox, or Safari. Reload after a browser update, then retry from a deliberate sound action. Recording support is detected separately, so the model may still play when WAV capture is unavailable.

Further help

If a problem remains, note the model, browser, and action that produced it.