FAQ

Short answers to the questions that come up before and just after installing, each with a link to the page that has the detail.

Is OpenStudio really free, and what does AGPLv3 mean for me?

Yes. No paid tier, no trial, no license key, no account. The NAM Rack and every built-in effect ship in the base app with nothing to unlock. The source is published under the GNU Affero General Public License v3; the NAM core it uses is MIT-licensed.

The app’s license does not by itself put your recordings under AGPLv3; third-party content and models have their own terms. Distributing a modified app, or letting others use it over a network, carries corresponding-source obligations under AGPLv3. Full text: the LICENSE file; plain summary: the terms page.

Which platforms does it run on?

• Windows 10 or later, 64-bit, as an installer that also handles WebView2 and the VC++ redistributable.
• macOS 12 Monterey or later, as a DMG.
• x86-64 Linux as an AppImage; the release pipeline builds on Ubuntu 24.04.

Drivers: ASIO, WASAPI, or DirectSound on Windows; CoreAudio on macOS; ALSA or JACK on Linux. Plan on 8 GB of RAM. The download page has the current builds and requirements table.

Why does the installer warn me?

Signing and notarization depend on the build. SmartScreen on Windows or Gatekeeper on macOS may warn or block first launch. On Windows choose More info → Run anyway; on macOS right-click the app, choose Open, and allow it under System Settings → Privacy & Security if asked. Most Linux distributions run the AppImage without extra steps.

That path is documented, not warning-free. Download only from openstudio.org.in or the official GitHub releases, and compare the SHA-256 on the download page to check file integrity.

Which plugin formats work, and how well?

VST3 is the stable, primary path for effects and instruments. CLAP and LV2 code paths are present where the format is available, but compatibility varies more by plugin; bringing CLAP instrument and event handling up to the VST3 standard is on the roadmap.

Does it bundle amp captures or cabinet IRs?

No. The NAM Rack engine is in the base app, but third-party captures and impulse responses keep their creators' licenses and are distributed separately. Load your own .nam files and IRs, or connect the optional TONE3000 catalog. A roadmap guardrail rules out bundling third-party captures or IRs without clear redistribution permission.

Do I need an account?

Core recording and editing need no account. Gated Stable Audio downloads require Hugging Face access and licence approval. TONE3000 is another optional service: its connected catalog uses a TONE3000 account through a browser-based OAuth sign-in, with tokens kept in the OS credential store. Local capture loading never depends on it, and the app stays usable when the service is unavailable.

Is AI required, and does it run locally?

AI is optional and never blocks startup. Stem separation, text-to-music, and text-to-audio install on demand through AI Tools Setup, which prepares a managed local Python runtime and model assets. Once the files are validated, processing runs on your machine and works offline.

The bundled Basic Pitch model for audio-to-MIDI needs ONNX Runtime, provisioned on Windows and Linux only. Generation results depend on your hardware, RAM, and VRAM; upstream gives no fixed minimum. Guided setup downloads Stable Audio 3 Medium after Hugging Face licence approval, and MiniMax Music 3 after licence acceptance. Local snapshot import remains optional. See AI Tools setup.

What is the project file format?

Projects save as .osproj; retired project formats require conversion and cannot be opened by renaming the file. Back up projects and keep the older app for unconverted sessions. The file holds tracks, clip references, MIDI data, automation, markers, the tempo map, mixer and plugin state, and settings. Audio stays outside the project and is referenced by path. To move a session, copy its project and media files, including any NAM captures and IRs. File → Archive Session… has portability limits; see Rendering & export.

Can I import REAPER or Ableton projects?

Not currently. REAPER .rpp, Ableton Live .als, and AAF import are not available as supported project workflows. RPP and EDL export are not available from the app either. Export stems from the other DAW and import the audio.

What can I export?

WAV, AIFF, and FLAC with selectable bit depth; MP3 and OGG Vorbis through FFmpeg; MIDI; and DDP. Master, per-track stems, region ranges, and a render queue are available. FFmpeg is bundled on Windows; on macOS and Linux, MP3 and OGG export need a system ffmpeg on your PATH.

Does it phone home?

The app requests release metadata from openstudio.org.in to find newer builds; Help → Check for Updates… triggers the same check. Those requests fetch version and download information and are not intended to send personal identity information. Projects, audio, presets, and exports stay on your device, and the optional AI tools process audio locally.

Optional connected features contact TONE3000 for its catalogue and downloads, GitHub for releases and runtime assets, and model hosts such as Hugging Face during AI setup. Gated models may need a provider account and access approval. The desktop app has no advertising or marketing vendors. The privacy page is the full statement.

Where do I report bugs or contribute?

Open an issue on GitHub with your OS, OpenStudio version, and steps to reproduce. Code and documentation changes go through pull requests on the repository; the community page lists good first issues. Security problems go by email, not a public issue; see the security page.

Where is the roadmap?

On the roadmap page, mirrored from roadmap.md upstream. It describes direction, not dates: release quality now, DAW foundations next (MIDI workflows, CLAP parity, render options), and a local DAW assistant among the items under exploration.

What is not planned?

The roadmap's product guardrails rule out:

• Bundling third-party NAM captures or cabinet IRs without clear redistribution permission.
• Presenting automated measurements as proof of subjective tone, naturalness, or commercial-product parity.
• Exposing experimental controls as working features before their full signal path, persistence, and tests exist.
• Bringing back retired NAM Rack controls or decorative routing without a new product decision and full QA.

A native extension SDK is only under exploration, conditional on demand for a stable ABI; Lua and JSFX remain the supported extension paths. See Lua scripting.