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
Microphones, sound drivers, volume, compression and background noise can change a match. The tool recognizes similarity to a sample, not the meaning of an alarm, phrase or event. Keep important work supervised.
Build your first sound trigger
1. Prepare a simple chime
Choose a short, harmless test chime, such as a plain one-second beep. It should have a clear start and end and contain no speech, music or private audio.
2. Add the reference
Open Audio Trigger. Load the chime as the reference. You should see its duration, audio format and a shortened SHA-256 value.
3. Listen to computer sound
Choose Computer sound and System default. Play the chime once. You should see the input level move.
4. Add safe actions
Choose a short Timeout. Put a one-second Delay in THEN and Stop in ELSE. These actions let you test without clicking anything.
5. Test the expected chime
Start the test and play the exact chime. You should see the live match score rise and the THEN delay run.
6. Test silence and a different tone
Run the test in silence. Then play a clearly different tone. Both tests should end in ELSE. Keep F12 ready as the permanent Emergency Stop.
Advanced reference and matching controlsFormats, devices, tuning and wait behavior.
You can record a reference inside the app or load WAV, MP3, M4A or FLAC. References can be 0.25 to 8 seconds and up to 32 MiB. Trim silence and unrelated audio from both ends.
Computer sound hears what the PC is playing. Microphone hears the selected input device and can also capture the room. System default follows the current Windows device. A fixed device fails safely if it disappears instead of silently switching devices.
Sensitivity controls the required match. Release threshold helps reset after a sound, Noise gate ignores quiet input, Stability can require a consistent match, and Cooldown prevents repeated firing. Change one setting at a time and test both the reference and a similar sound. Single scan checks once. Timeout has a finite ELSE result; Until triggered does not.
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 reference triggers and the other tests do not.
Local audio behaviorWhat is heard, stored and sent.
- Reference processing and live matching run locally.
- The audio trigger does not upload the reference or live audio for matching.
- A microphone can capture voices and room sounds. Use a plain test chime or another harmless 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.
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 testing similar sounds that should not trigger
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.
Osenpa Auto Clicker
Compare a short sound locally and connect a tested match to an editable supervised workflow.