A focused playback checklist

No sound? Fix a silent Play Music Theory loop

A silent canvas is usually easy to explain: there may be nothing to play, the browser may be waiting for a tap, or the sound may be muted or routed elsewhere. Start with the quickest checks and stop as soon as the loop returns.

Updated September 27, 2026 · 1,125 words · 6 min read

First prove that the canvas contains playable marks

A blank canvas is silent by design. Begin troubleshooting with one obvious mark in the middle of the page so the test does not depend on a complex imported or partially erased drawing.

Try it once: Draw a thick green line across the middle-left of the canvas and confirm that it remains visible. Add a second mark at a different height so there are two unmistakable events.

A visible test source separates playback problems from an empty or off-screen composition. Ask yourself: Does either mark sound when the playhead reaches it?

The easy mistake is debugging headphones, browser settings, and exports before checking whether there is anything to play. If that happens, clear the page, redraw the two test marks, and keep every optional beat or program off.

If that works, take it one step further: Use Shuffle to compare a generated composition with your manual test marks. If both remain silent, continue to audio activation and output checks; if Shuffle works, inspect the original drawing. Stop there for a moment. The small version is easier to hear than a crowded canvas.

  • Start: Draw a thick green line across the middle-left of the canvas and confirm that it remains visible.
  • Change: Add a second mark at a different height so there are two unmistakable events.
  • Listen: Does either mark sound when the playhead reaches it?
The live Play Music Theory editor playing a rising green line
The live Play Music Theory editor playing a rising green line

Use a direct tap to activate browser audio

Modern browsers commonly wait for a user gesture before starting Web Audio. A page can be fully loaded and still require a direct Play tap before sound is allowed.

For the next pass: Tap or click Play inside the page rather than relying on automatic playback after navigation. Pause, tap another editor control, and start again from the beginning.

The gesture gives the page permission to resume its audio context under browser autoplay rules. Ask yourself: Does sound begin only after the direct interaction?

This gets muddy when you start refreshing repeatedly while expecting the browser to autoplay without interaction. If that happens, wait for the editor to finish loading, tap Play once, and keep the tab in the foreground.

A good second take is simple: Open a fresh tab and confirm that the first-tap behavior is reproducible. A successful activation should make later play and pause actions respond normally during the session. If the second take surprises you, keep it. A useful test can become a song idea.

A finished drawing beside the live WAV and MIDI export controls
A finished drawing beside the live WAV and MIDI export controls

Check volume, mute state, and the actual output device

Sound can be generated correctly and still be inaudible because system volume is low, the browser tab is muted, or audio is routed to headphones, Bluetooth, a monitor, or another device.

Start small: Raise system media volume to a safe audible level and inspect the browser tab for a mute indicator. Disconnect unexpected Bluetooth or external outputs and select the intended speaker.

Output routing occurs beyond the editor, so an active playhead does not prove the intended speaker is receiving sound. Ask yourself: Does audio return when the route changes even though the canvas remains untouched?

Watch out for raising every volume control to maximum without first identifying the selected output. If that happens, pause playback, select the correct device, set moderate volume, and resume with the two-mark test.

If you are curious, try this: Compare built-in speakers and wired or Bluetooth headphones one at a time. The same test loop should follow the selected route without requiring a different drawing. You may prefer the imperfect version. That is a choice, not a failed experiment.

The live editor with beat and click controls enabled
The live editor with beat and click controls enabled

Inspect the instrument switch, program, tempo, and play state

The editor includes controls that can change what is heard or how quickly it passes. A silent-looking failure may instead be an off instrument, an unexpected program, or a playhead that has not reached the marks yet.

Here is the useful comparison: Confirm the instrument switch is on, select Program 1, and place a mark near the left edge. Return tempo to a moderate setting and turn optional beat buttons off.

A known editor state removes timing and program ambiguity from the audio check. Ask yourself: Does the left-edge test sound quickly after Play is pressed?

If the result is hard to read, you may be waiting only a moment for marks located near the far right of a slow canvas. If that happens, move the test mark left, restore common settings, and watch the playhead cross it.

There is one more version worth hearing: After sound returns, restore one previous control at a time to identify the trigger. The failure should be connected to one reproducible setting rather than described as random. The point is not to win the comparison; it is to notice what changed.

The live editor showing scale, range, timing, and export controls
The live editor showing scale, range, timing, and export controls

Isolate browser extensions, stale state, and unsupported conditions

If the simple test remains silent, isolate the browser environment. A private window, a current alternate browser, or cleared site data can reveal interference without changing the music drawing itself.

Before adding anything else: Copy the share link, open it in a private window, and perform the direct Play tap again. If needed, test the same link in another current browser on the same device.

A successful clean-session test points toward cached state, extension interference, or a profile-specific permission. Ask yourself: Does playback work in one clean environment but fail in the original profile?

The comparison stops being useful when you start clearing all browser data before preserving the editable link or noting the failing state. If that happens, save the link and screenshots first, then clear only relevant site data or disable extensions selectively.

You can turn the test into a sketch: Compare normal and private sessions with the same output device and system volume. You should know whether the problem follows the piece, the browser profile, or the whole device. Save the odd result if it makes you want to listen again.

The live Play Music Theory sharing workflow
The live Play Music Theory sharing workflow

Collect useful evidence when the loop is still silent

A useful problem report describes the smallest failing case and the exact environment. “No sound” becomes actionable when it includes the test marks, browser, device, output route, and steps already tried.

For the last pass: Preserve a share link to the two-mark test and capture the visible editor state. Write numbered reproduction steps beginning with a fresh page load and direct Play tap.

Reproducible evidence distinguishes product defects from local routing or permission problems. Ask yourself: Can another person follow the steps and encounter the same silent moment?

The last thing to avoid is sending only a screenshot with no link, browser version, device, or indication of where the playhead was. If that happens, add the missing environment details and state whether other websites produce sound through the same output.

Then stop reading and try one final variation: Record a short screen capture showing the tap, moving playhead, and missing audio response if practical. The report should let support or development test the same state without guessing your setup. You have enough information now. Close the guide and make the next choice by ear.

The live editor playing a multicolor drawing in a phone viewport
The live editor playing a multicolor drawing in a phone viewport

Wiggly Music app

Keep making music on Android.

Take the idea with you in Wiggly Music.