Leaving Glob

You’re opening another site. Its content and privacy practices are outside Glob’s control.

Skip to main content
Sign inSign up
Skip to the guide

Reference and help

Studio troubleshooting

Resolve silent playback, missing MIDI input, failed local saves, listener-audio problems and export errors.

Start with the status area in the bottom dock and any message in the panel you are using. Save the work that is still available before reloading or switching browsers.

No sound

Tap play to enable sound means the browser has not started its audio context. Press Play directly in Studio. If that does not help, check the browser's site sound setting, tab mute and your operating system's output volume and device.

Studio has no output-device selector. If you changed headphones, speakers or an audio interface, choose the intended output in the operating system or browser. Stop and restart playback after changing it. Keep the project saved before reloading the page.

If the browser is allowed to make sound:

  1. Check Listening level in the mixer.
  2. Check the track's M and S controls. Another soloed track can exclude the one you want.
  3. Check that an instrument remains on the track. No instrument: add a device to hear this track explains an empty instrument slot.
  4. Check that the phrase has notes and that its arrangement placements cover the position you are playing.
  5. If you launched clips earlier, check launcher control. Switching to Arrange does not reset those tracks.
  6. For a custom patch, check that its source reaches an output and that any required sample source is assigned.

If one sound stops after adding a module, reopen its Grid and inspect the compile or preparation message. An unsupported or over-budget patch can leave a previous playable version active, or leave an affected track silent. Remove the last addition or simplify the graph, then retry. Performance covers freezing and device load.

The browser cannot prepare audio

AudioWorklet is unavailable in this audio context means the browser cannot provide the audio-processing facility Studio needs. Save the project to Glob from a working session if possible, and open it in a browser that supports the required audio features. A different browser does not have access to this browser's local drafts automatically.

If you see Glob Studio was updated. Reload the page to keep playing., use its Reload button after checking your save status. The page and its audio runtime need to match. Repeatedly pressing Play does not resolve that mismatch.

Audio exports also need offline audio rendering. MIDI, audio rendering and ordinary audio-file playback are separate browser capabilities; success in one does not establish that the others are available.

MIDI does not appear

Make a pointer press or play a recognised note key in Studio to start the MIDI permission request. Allow MIDI access if the browser asks. Connected inputs are attached automatically and the status reports MIDI: … connected.

If no input appears, check that the keyboard is connected, that the operating system recognises it, and that the browser supports Web MIDI and has permission. Computer keys and the on-screen piano remain available when MIDI is refused or absent.

In a custom device's preview tools, Web MIDI is unavailable in this browser. Use the on-screen keyboard or QWERTY keys. provides the same fallback. See the device designer for that preview's separate Connect Web MIDI control.

Playing works but notes do not record

Record notes requires both the transport playing and Record notes enabled. It writes to the selected track, regardless of the header's arm indication. Text fields take typing keys, so click out of Project name or search first.

Pointer auditions on piano keys and drum pads are for listening; use computer or MIDI input for this recorder. This clip could not record another note means the edit could not fit or validate. Remove unneeded notes or use a shorter phrase. Recording explains phrase wrapping and held-note limits.

A control changes but the sound does not

Some visible settings have limited current sound behaviour. Pitched factory waveform choices, LP/BP/HP and Key trk are retained without being applied to the current factory graph. Drum per-pad Pan and Choke are disabled. Track Envelope modulation is not triggered from notes. The instrument, drum, effect and modulation references identify these cases.

After loading a generated sound or kit from Samples, explicitly choose Drum Rack in the instrument selector if a different instrument was there before. The Samples action changes rhythm and type but does not replace the existing graph.

Also check whether you are in Edit modulation amounts mode: cyan values change route amounts rather than a knob's base setting. A hidden automation lane can still override the base during playback. See modulation and automation.

Local saving fails

Message What to do
Browser storage is full. Your latest edits have not been saved locally. Keep this window open and free browser storage, then retry. Keep Studio open. Free browser storage without clearing the work you need, then use Retry local save. Save to Glob if available.
Local storage is unavailable. Your latest edits have not been saved in this browser. Check browser storage permissions or restrictions. Keep the window open and save to Glob if possible.
Local save failed. Keep this window open and retry to save your latest edits. Retry from Projects in this browser and check the resulting status.
Could not open this local project. Refresh the local library and try another saved project. Do not clear storage as a first step.

Show deleted projects → Restore can recover a project deleted through the local library. It cannot recover browser data that has been cleared or removed. See projects.

This v1 project uses the retired audio engine. Open a new Grid project; the original has been kept unchanged. means the old project cannot execute in the current engine. It has not been silently converted. Start a new project.

Saving to Glob or listener preparation fails

Sign in to save to Glob requires a signed-in music session. Could not save means the server save did not complete; retain the browser copy while resolving it. A saved track's version may have changed in another tab. Check the shared-edit message before retrying.

The shared project changed. Choose which edits to keep. offers Keep my edits and Use shared edits. Choose based on which work you intend to preserve. Live edits are offline. Your draft is kept on this device. means the live editing connection is unavailable; it is not confirmation of a new saved Glob version.

Your project is saved, but listener audio is not ready. Try preparing it again. distinguishes an audio-preparation failure from losing the saved project. Use Prepare listener audio again and leave the browser open through rendering and uploading. A listener can otherwise see Audio is not available yet. The creator needs to finish publishing it.

Export fails

Save the project successfully first, then retry the intended export action. The saved project changed before export. Try exporting again. asks for a fresh render from the current saved version. Set a loop region with an end after its start. requires valid loop boundaries.

These export options need a Grid project with a Grid instrument on every track. can follow deletion of a track's instrument. Add a source to that track. Signing is unavailable. Please try again later. is a temporary signing failure; keep your saved project and retry later.

The configurable Export WAV and separate Export signed WAV buttons use different export settings. Read exporting audio before comparing their results.

If the problem persists, contact [email protected] with the exact message, browser, device and steps that caused it. Keep private project material out of a public report.