The Problem If you are shouting “Clip That!” but the AI isn’t capturing the moment, the issue is usually related to browser permissions or audio input settings. Eklipse needs clear access to your microphone to detect the trigger words.
The Solution: Check These 3 Settings
1. Allow Microphone Access in Browser Your browser (Chrome/Edge) often blocks microphone access by default.
- Click the Lock Icon 🔒 in the URL bar (top left).
- Find Microphone and toggle it to “Allow” or turn the switch On.
- Refresh the page for changes to take effect.
2. Prevent “Sleeping Tabs” If you stream with Eklipse open in a background tab, your browser might put it to “sleep” to save RAM, cutting off the audio listener.
- Chrome: Go to Settings > Performance > Memory Saver. Add
app.eklipse.ggto the “Always keep these sites active” list. - Edge: Go to Settings > System and Performance > Never put these sites to sleep > Add
app.eklipse.gg.
3. Check Default Input Device Ensure Eklipse is listening to the correct microphone (especially if you have a headset + standalone mic).
- Go to your PC Sound Settings > Input.
- Ensure your main streaming microphone is set as the Default Device. Eklipse automatically uses the system default.
⚠️ Specific Error Messages #
Still stuck after checking settings? Check these specific scenarios:
“Microphone Not Detected”
Unplug and replug your microphone USB/Jack. Then, refresh the Eklipse page. Ensure no other app (like Discord) has “Exclusive Mode” enabled for your mic.
I said “Clip That” but nothing happened
Speak clearly and wait for the “Listening…” indicator to pulse. Background music or loud game audio might mask your voice command.
System Checked? #
Your mic is ready. Try saying “Clip That” on your next stream!
Test Voice Command Now →*Works on Chrome, Edge, and Brave
