A browser session works best with a narrow goal
Making music online can mean many things: arranging a song, building a drum pattern, playing an instrument, or recording a short visual performance. Trying to do all of them in one first session creates friction. Pick a narrow goal such as making a 20-second chord performance with a clear beginning and ending.
Gesture Synth is useful for that kind of goal because the selected style provides a coherent harmonic space. You decide when to change chords and when to raise or lower intensity. The browser is the performance surface; it is not presented as a replacement for a full production workstation.
Choose the right online music workflow →Start in keyboard mode →Explore the browser instrument →
Make one sound before you make a pattern
Before planning chords, verify that your browser can play audio through the output you expect. Check system volume, browser-tab muting, Bluetooth routing, and headphones. Most browsers require a user gesture before beginning audio, so interact with the player rather than waiting for sound to start by itself.
If a single chord plays, your next task is musical rather than technical. If it does not, avoid changing five settings at once. First test another safe audio page or local media file, then return to the player. This separates a device-level output issue from a control issue inside the page.
Use a three-part structure for a first performance
A short performance becomes easier to remember when it has three parts. Start quietly with one chord state. Repeat or contrast it once in the middle. Then make one final change and allow a beat of space at the end. The structure is simple enough to practice without notation but gives your take a recognizable shape.
In Gesture Synth, do not rush through every available chord. Two or three reliable changes usually communicate more than a dense sequence. In keyboard mode, repeat the same action on a count. In hand mode, hold a gesture long enough for tracking to settle before moving to the next state.
- Choose one style and begin with a single chord state.
- Repeat it or switch to one contrast chord after a steady count.
- Create one energy change rather than constant motion.
- Return to a stable ending and listen for a clear stop.
Use the right input for your setting
Keyboard mode is the practical starting point when you are at a desk, using a shared device, or do not want to grant camera permission. It also helps isolate audio problems: if keyboard mode works but hand input does not, focus on the camera path rather than the sound engine.
Hand tracking is an optional performance input. It works best with even front lighting, a visible palm and fingertips, and no other application claiming the webcam. Camera access is controlled by your browser and can be changed later from site settings. There is no need to enable it just to make a first musical idea.
Use a computer keyboard as an instrument →Prepare a webcam for hand tracking →Learn how browser permissions work →
Treat recording as a compatibility check, not a promise
If you want to keep a performance, make a short test before you build a longer one. Check that the controls react consistently and that the resulting download plays on the device you intend to use. Recording and file handling vary across browsers, operating systems, and available storage, so an actual check is the honest way to plan.
Keep the first attempt small. A repeatable 20-second performance tells you more about timing and export behavior than a complicated five-minute session. Once the workflow is stable, you can add variation without losing the ability to identify what changed.
Record a short browser music performance →Read about responsive music visuals →Open Gesture Synth →
