Audio Trigger BETA

Start Windows Automation When a Sound Plays

Teach Auto Clicker a short reference sound and run a supervised action when the sound matches.

By Osenpa Published Reviewed

Short answer

Audio Trigger compares a short reference sound with sound currently arriving from computer audio or a microphone. Use a clean, distinctive reference, choose the correct listening device and test silence, similar sounds and the expected sound before connecting any important action.

Audio Trigger is labeled BETA

The feature is implemented, but microphones, sound drivers, volume, compression and background noise can change the match. It recognizes similarity to a reference sample, not the real-world meaning of an alarm, spoken phrase or system event. Keep important work supervised.

Build a sound-triggered workflow

1. Decide which sound is the signal

Choose a short sound with a clear beginning and end. Avoid music, long speech, changing background noise or a tone that occurs often for unrelated reasons.

2. Create the reference

Record the sound inside the app or load a WAV, MP3, M4A or FLAC file. The useful reference length is 0.25 to 8 seconds, and a reference file can be up to 32 MiB. Trim silence and unrelated audio from both ends.

3. Choose where to listen

Computer sound uses Windows loopback to hear what the PC is playing. Microphone listens to the selected input device and can also hear the room. The reference source and listening device are separate choices.

4. Decide how device changes should behave

System default follows the current Windows default device. A fixed device remains tied to that device. If a fixed device disappears, the trigger fails safely instead of silently switching to another microphone or speaker.

5. Test the live score and input level

Play the expected sound several times at realistic volume. Then test silence and similar sounds that should not match. A visible input level confirms that audio is arriving; the match score shows how closely it resembles the reference.

6. Tune one setting at a time

Sensitivity controls the match required to trigger. Release threshold helps the trigger reset after a sound. Noise gate ignores input below a chosen level. Stability can require a match to remain consistent. Cooldown prevents one sound from firing repeatedly. Change one control, then repeat the positive and negative tests.

7. Choose wait behavior and actions

Single scan checks once. Timeout can use ELSE if no sound matches before time ends. Until triggered keeps listening and has no finite no-match result for ELSE. Start with a harmless THEN action and keep F12 ready as the permanent Emergency Stop.

Checkpoint: prove the trigger is selective

Pause before attaching an input action. Play the reference several times, then test silence and a similar sound. Continue only if the expected sound matches and the negative samples do not.

Local audio behaviorWhat is heard, stored and sent.
  • Reference processing and live matching run locally.
  • The audio trigger does not need to upload the reference or live audio for matching.
  • A microphone can capture voices and room sounds. Use a synthetic chime or harmless test recording. Do not use private audio.
  • Fixed-device failure is reported instead of silently listening through a different device.
  • Input Variation does not change audio scores, sensitivity, stability or cooldown. It only makes small timing or click-position changes within the limits you set and is not an anti-detection guarantee.

Beginner example: react to a short chime

Create a one-second synthetic chime and load it as the reference. Listen through computer sound. Make THEN wait for one second without clicking, use a short timeout and make ELSE stop. Test silence, a different tone and the exact chime. Only after those paths behave correctly should you replace the harmless delay with the intended supervised action.

Watch for

Common false-match causes

  • A reference with long silence or background speech
  • A microphone hearing notifications or voices in the room
  • Volume or device changes after tuning
  • High sensitivity without a negative test set
Verify the result

Audio Trigger checks

  • The expected sound matches several times.
  • Silence and similar sounds do not match.
  • Removing a fixed device fails safely.
  • Cooldown prevents one sound from firing repeatedly.
  • F12 stops a harmless test immediately.
Audio Trigger settings in Osenpa Auto Clicker
Audio Trigger BETA

Osenpa Auto Clicker

Compare a short sound locally and connect a tested match to an editable supervised workflow.