Check Gesture Synth Browser Compatibility

Chrome, Edge, Safari and Mobile Support

Use a current desktop Chrome or Edge release for the most predictable combination of camera permission, WebAssembly hand tracking and Web Audio. Chrome on Android supports the same core instrument with a smaller landscape layout and may need Low-performance mode on slower hardware.

Safari on macOS, iPhone and iPad may support the core camera and audio path, but version-specific restrictions can affect background audio, camera recovery or offline WAV rendering. Firefox and other standards-based browsers may expose the required APIs, yet they are not the primary tested path for this release.

• Chrome desktop: primary tested camera, tracking, audio and export path.
• Edge desktop: primary tested Chromium path.
• Chrome Android: supported with landscape and performance guidance.
• Safari and iOS: capability-dependent; use the visible error and fallback messages.

Verify Camera, WebAssembly and Web Audio Separately

A visible camera preview does not prove that the hand model loaded, and a moving chord label does not prove that the audio output is active. Press Start in a secure top-level tab, then check the camera status, Left and Right indicators, chord or pitch display and audible output in that order.

The browser must allow a video-only camera stream and load the local hand model files. It must also create or resume an AudioContext after your Start click. The instrument never needs microphone access, so enabling a microphone is not a compatibility fix.

Use a compact compatibility record when a device fails. Note the exact browser and operating-system versions, whether the direct HTTPS page showed a camera prompt, whether video appeared, whether both hand indicators reacted, whether the chord label changed and whether sound reached the chosen output. Test a one-bar export only after live sound works, and record whether WAV, WebM or an error was produced. These checkpoints correspond to separate browser capabilities, so the record shows whether failure occurred at permission, camera capture, WebAssembly inference, Web Audio or offline rendering. It also makes a second-browser comparison meaningful without sharing camera footage or personal account information.

Restore camera access → · Restore browser audio →

Open a Secure Top-Level Tab, Not an Embedded Preview

Camera access requires the production HTTPS page. Open gesturesynth.me directly instead of using an embedded social, email or search-app preview. Embedded frames can hide site controls, block permission prompts or pause the page when their parent application changes state.

Close duplicate GestureSynth tabs and other camera applications before testing. If one recent browser succeeds and another fails on the same device, reset only the failed browser's site permission and retest before changing operating-system privacy settings.

Understand WAV and WebM Export Compatibility

The loop sequencer first tries OfflineAudioContext to render a stereo 44.1 kHz, 16-bit PCM WAV file locally. When offline WAV rendering is unavailable, the app tries MediaRecorder and a supported WebM audio type. If neither API exists, the interface reports that export failed in this browser.

Export support is independent from camera recognition. You can play successfully even when a browser lacks the preferred offline export path, and a WAV problem does not mean camera frames were uploaded or microphone audio was recorded.

Follow the complete WAV export guide → · Set up Gesture Synth on mobile →