OpenStudio Loading your studio
Skip to content
Docs · Reference

Troubleshooting

Indexed by symptom: no audio, latency, crackle, plugins, media, rendering.

Last updated 08 Oct 2026Development build referenceSource on GitHub
Development checkout: Native window behavior

Unreleased September 29 working-tree changes after app commit 52cbd7c use OS title bars for the main app and the implemented mixer, MIDI and built-in plugin editor windows. Startup refreshes no longer change outer window bounds; saved detached bounds stay on the relevant monitor when available. The graphical pitch editor also has a native detached window: Detach, Focus and Dock keep the existing clip session and committed history. Closing and reopening the same clip retains committed edits. WebView2 applies to Windows; macOS uses WKWebView and Linux uses WebKitGTK. Windows Debug geometry/lifecycle checks do not establish packaged Release or cross-platform results. First-launch readiness, physical drag/snap, DPI transitions and close/reopen still need qualification on each target platform.

Find the symptom, work through the list in order. Shortcuts are the OpenStudio default keyboard profile (Ctrl is Cmd on macOS). Background for each group is in Audio setup, Plugins & scanning, and Keyboard shortcuts. If nothing fits, search the issue tracker before opening a new one.

Install and first launch

Development checkout: startup recovery

Unshipped working-tree changes reviewed on top of app commit 52cbd7c improve packaged AppImage asset lookup and require the Linux release check to launch the finished AppImage. On Windows, an unusable inherited WEBVIEW2_BROWSER_EXECUTABLE_FOLDER override can be ignored when the installed Evergreen runtime works. Startup diagnostics now record WebView2 loader and environment results; Repair Dependencies waits for the bundled installers, checks their exit codes, and checks browser availability again. These paths still need validation on the affected Linux and Windows 10 machines.

The OS warns or blocks first launch

Signing and notarization depend on the build. Check the release notes; a signature does not guarantee that SmartScreen or Gatekeeper will accept a download without a warning.

  1. Windows: when SmartScreen appears, choose More info → Run anyway.
  2. macOS: right-click the app, choose Open, then allow it under System Settings → Privacy & Security if asked.
  3. Ubuntu or Ubuntu-based Linux Mint: open the .deb with Ubuntu App Center or Software, or Linux Mint’s package installer, install it, then launch OpenStudio from the application menu.
  4. Optional AppImage: run chmod +x OpenStudio-*.AppImage before launching. It requires compatible host GTK/WebKit and FFmpeg libraries.
  5. For the optional AppImage, launch the AppImage itself, rather than an extracted usr/bin/OpenStudio binary, so its bundled assets and startup environment are available.
  6. Verify the SHA-256 on the download page to check file integrity.

The DEB opens Archive Manager or does not install

These native Linux installation instructions refer to published v0.1.05, app commit 649012c, built for x86-64 Ubuntu 22.04+ (including 24.04) and Ubuntu-based Mint. Automated qualification installed the DEB through the package manager on Ubuntu 22.04; it does not establish every graphical installer or clean desktop environment.

  1. Use Open With and select Ubuntu App Center or Software, or Linux Mint’s package installer. Archive Manager extracts files; it does not install the package.
  2. If the graphical installer cannot upgrade the package, close OpenStudio and install the downloaded .deb with the distribution’s package manager.
  3. Read any dependency error before retrying. The package is for x86-64; it is not an ARM installer. Do not run OpenStudio as root.

AI Tools are missing, or a generation dialog says the runtime is absent

AI Tools are optional runtimes installed separately so the base download stays small. Only stem separation and generation need them.

  1. Click the AI Tools button beside the Settings button, or Install AI Tools inside the Stem Separation dialog.
  2. Let the setup modal finish; it can be cancelled, reset, or retried from there.
  3. See AI Tools setup for what is installed and how to keep it offline.

No sound, latency, crackle, high CPU

Transport says Playing but there is no sound

  1. Open View → Audio Settings… and confirm the output device.
  2. Check the interface is powered on and connected.
  3. Check no track is muted and the master fader is up.
  4. Check for a stray solo; solo mutes every other track.
  5. On ASIO, make sure no other application holds the driver exclusively.

Noticeable delay between playing and hearing it

  1. On Windows, switch to ASIO.
  2. Lower the Buffer Size to 128 or 256.
  3. Close other audio applications competing for the device.
  4. If the smaller buffer crackles, raise it one step until stable.

Pops, clicks, or crackle during playback or recording

  1. Raise the Buffer Size to 512 or 1024.
  2. Freeze CPU-heavy tracks: right-click the track → Freeze Track.
  3. Reduce the number of active plugins.
  4. Close unnecessary background applications.
  5. Update your audio interface driver.

CPU usage stays high

  1. Freeze tracks with heavy plugins.
  2. Increase the buffer size.
  3. Remove or bypass plugins you are not using.
  4. Reduce the number of simultaneous tracks.
  5. Close the Mixer and unused plugin editors to reduce display work.

Plugins

An installed plugin does not appear in the list

  1. Check it is installed in a standard VST3 directory.
  2. Open the FX Chain panel and click Scan to rescan.
  3. Confirm it is a 64-bit plugin. VST3 is the most mature path; CLAP and LV2 compatibility varies by plugin and build.
  4. Check the plugin file is not corrupted; reinstall it if in doubt.

A plugin crashes, hangs, or makes noise

  1. Open a copy in Safe Mode with Ctrl+Shift+O; saved instruments and FX are not loaded. Avoid overwriting the original from this mode.
  2. Add plugins one at a time in the copy to find the culprit.
  3. Check the plugin's documentation for channel configuration requirements.
  4. Update the plugin to its latest version.
  5. Remove and re-add the plugin to reset its state.

Recording and MIDI

Record is greyed out, or the recorded clip is empty

  1. Arm at least one track; the transport Record button is disabled otherwise.
  2. Confirm the Input Device in Audio Settings.
  3. Check the input channel chosen on the armed track's header.
  4. Watch the track header's activity meter to confirm signal is arriving.
  5. Make sure Record Safe is off on the track.

macOS: the input shows in Audio Settings but records silence

macOS gates every audio input, interfaces included, behind the Microphone permission.

  1. Quit OpenStudio.
  2. Enable OpenStudio under System Settings → Privacy & Security → Microphone.
  3. Relaunch, reselect the input, arm a track, and check the meter.
  4. If OpenStudio is not in the list, reset the permission for the app bundle only; the command is in Audio setup.

A MIDI controller is not in the input selector

  1. Connect and power the controller before launching OpenStudio.
  2. Install the device's driver if it needs one.
  3. Restart OpenStudio after connecting.
  4. On Windows, confirm the device shows in Device Manager under Sound, video, and game controllers.

Projects and media

Clips are empty or show a missing file warning

Audio is referenced by path, not embedded, so moving or deleting source files breaks the link. The Missing Media dialog is the recovery path; the full Media Pool panel is not mounted in the current build.

  1. When prompted on load, browse to the moved files in the Missing Media dialog.
  2. Resolve each referenced path; resolved paths are saved with the project.
  3. If the originals are gone, re-record or re-import.

The project will not save

  1. Check the target directory is writable.
  2. Try Save As (Ctrl+Shift+S) to a different location.
  3. Check free disk space.
  4. Check antivirus software is not blocking writes.

Audio clips have no waveform

  1. Wait a moment on first load; the peak cache is being built.
  2. Waveforms come from .ospeaks sidecar files, which the app regenerates when needed. Deleting a peak-cache sidecar does not delete the source audio.
  3. Check the referenced audio file exists and is readable.
  4. Zoom in or out to force a refresh.

Rendering

The rendered file is silent

  1. Check the Start and End times cover where the clips are.
  2. Check Source: Master mix for the whole song, specific tracks for stems.
  3. Check no track or clip is muted.
  4. Confirm the project plays back audibly before rendering.
  5. Render once with Entire project bounds to rule out a bounds problem.
MP3, OGG, and placeholders

MP3 and OGG need FFmpeg, bundled on Windows only; on macOS and Linux put a system ffmpeg on your PATH. Resample Quality remains disabled. Selected-item sources require selected audio clips; the current dialog does not offer Metadata entry or Online render.

Keyboard shortcuts

A shortcut does nothing

  1. Click the timeline or a panel so the main window has focus.
  2. Ordinary typing, native text-editing keys and input-method composition belong to text fields. Global modifier shortcuts can still work there. Native plug-in editors may consume their own keys; return focus to the main window to use host shortcuts.
  3. Open Help → Keyboard, Mouse & Trackpad for the effective map. F1 opens the Help Reference, not the key map.
  4. Check the selected profile, any platform override, and whether the action is intentionally unassigned.
  5. Check the action's scope. Timeline, Piano Roll, Pitch Editor, Mixer, automation, browser, plug-in, track-control, and modal bindings only fire in their own context.
  6. With a custom profile active, choose Inherit for the binding or reset the profile to compare against its base map.