gesture synth no sound
Restore Sound Without Sharing Camera or Audio
Most silent sessions come from a muted tab, a suspended browser AudioContext, very low right-hand volume or a camera pose that has not produced a valid chord. The checklist below separates audio-output problems from hand-tracking problems.
Protect your hearing while testing. Keep system volume moderate, use the instrument mute control between attempts and never raise the output to maximum before a valid gesture is recognized.
Play the instrument ↑- Microphone
- Not required
- First check
- Tab and instrument mute
- Audio start
- Requires a user click
- Fast reset
- Stop, then Start again
Quick No-Sound Checklist
Press Start again so the browser can resume audio after a user gesture. Confirm the browser tab is not muted, the in-app mute button is off and the master volume in Settings is above zero. Then hold a valid left-hand degree while raising the right hand to an audible position.
Check the left and right detection indicators. A running camera preview alone does not guarantee that both hands are recognized or that the current pose maps to a chord.
Run one minimal signal-path test before changing several settings. Disconnect Bluetooth temporarily, choose the device speaker or wired headphones, set system output to a moderate level and confirm another ordinary browser sound is audible. Return to Gesture Synth, press Start, unmute the instrument and hold degree I with the basic right-hand triad around mid-frame height. Read the evidence from left to right: active hand indicators prove tracking input, a changing chord label proves gesture mapping, and an audible chord proves Web Audio reached the selected output. If the first two succeed but the third fails, moving the camera or granting microphone access cannot help; continue with tab, browser and output-device checks. After direct output works, reconnect one wireless or virtual device at a time and repeat the identical chord. The first change that makes the test silent again or adds a long delay identifies the routing layer to correct.
- Unmute the browser tab and GestureSynth master mute.
- Set system output to the intended speakers or headphones.
- Press Start after reload; browsers block automatic audio before interaction.
- Show both hands and hold a clear finger count for a moment.
- Stop the session and start again if audio was suspended in the background.
Tell a Tracking Problem from an Audio Problem
If hand indicators remain inactive, improve lighting, move both wrists into frame and close other applications using the camera. This is a tracking problem even if the preview video is visible.
If both hands are detected and the chord or pitch display changes but nothing is audible, focus on tab mute, selected output device, browser audio permissions and system volume. The site does not need a microphone and enabling one will not restore synthesized sound.
Browser and Device Recovery Steps
Recent Chrome and Edge on desktop provide the primary experience. Reload the page in a normal secure tab, close duplicate GestureSynth tabs and check that another app is not holding the camera. On mobile, rotate to landscape and disable battery-saving restrictions that pause background audio.
If the model fails to load, verify that the connection can download the local hand-tracking assets. A corporate firewall, privacy extension or blocked WebAssembly can prevent the instrument from becoming ready even when the HTML page opens.
If the Synth Is Still Silent
Test another recent browser with the same output device. If one browser works, reset camera and sound permissions for gesturesynth.me in the affected browser and reload. If neither works, test a normal system audio source before changing more site settings.
When reporting a reproducible problem, include the browser name and version, operating system, whether both hands were detected and the exact status message. Do not send camera recordings, passwords or verification codes.
Answers before you play
Gesture Synth Sound Troubleshooting FAQ
Does GestureSynth need microphone permission for sound?
No. It generates audio with Web Audio and never records microphone input. Camera permission is used only for hand tracking.
Why is the camera working but the synth silent?
The tab may be muted, audio may still be suspended, the right hand may be at a zero-volume position or the current hand shape may not map to a valid chord.
Why did sound stop after switching tabs?
Browsers and mobile operating systems can suspend audio or camera work in background tabs. Return to the page and use Stop, then Start again.
Should I turn system volume all the way up?
No. Keep a moderate level while testing. Confirm mute, AudioContext and hand detection before increasing output to protect your hearing.