Guide · Mozonic Studio
Getting started with Mozonic Studio
Written for Mozonic Studio 1.0.4 on macOS.
Install and first launch
Mozonic Studio needs macOS 12 Monterey or later on Apple silicon (M1 or newer). Download it, open the .dmg and drag the app to Applications. It is notarized by Apple, so it opens normally.
On first launch you’ll see the Software Licence Agreement. Choose Accept to continue. Studio then builds a small built-in sample library, Mozonic Core, so the Browser isn’t empty. The AI panel is open on the right by default.
macOS will ask for microphone access the first time you record or dictate. Dictation is transcribed on your Mac and never uploaded.
Set up your audio interface
Click the AUDIO chip in the bottom status bar (or the gear icon → Audio Settings). In the Audio Device panel:
- Pick your Output and Input devices. Input defaults to none, so set it before you record.
- Set Session rate to match the device’s Sample rate, or playback runs at the wrong speed.
- Lower the Buffer size for less latency while recording; raise it if you hear clicks. The panel footer shows xruns (dropouts) and CPU.
- Test tone (440 Hz · −20 dB) confirms sound is reaching your speakers.
Scan your plugins
Studio doesn’t scan plugins automatically. To add yours: open the Mix window (⌘2), click an empty insert slot, then choose Scan for plugins… → Scan all plugins. It looks in the standard macOS plugin folders. VST3 and Audio Unit are supported; VST2 and AAX are not.
The first scan can take several minutes on a large library, and the engine is busy until it finishes. Later scans only check plugins that changed. Full rescan re-checks everything and takes much longer.
Plugins that need iLok, Waves, UAD or Antares licensing can be blocked if their activation prompt went unanswered during the scan. They’re listed under N plugins blocked. Sign in to the licence manager, then retry.
Use the AI assistant
Toggle the panel with ⇧A (or View → Show Agent). Type what you want — compose, mix or master — and press Enter. Type / for saved prompts and skills.
The assistant measures your session on your Mac before it proposes anything. Changes arrive as a card marked Awaiting your approval:
- Preview A/B applies the change, measures before and after (loudness, peak, headroom, width, correlation, clipping), and lets you Keep B or Revert to A.
- Accept (1 undo step) applies it;
⌘Ztakes it back. - Decline discards it.
Auto mode (the Auto chip under the message box) applies every proposal as it arrives and answers consent prompts with yes, including cloud uploads and music generation. It’s off by default. For something in between, ⋯ → Auto-apply settings lets you auto-apply chosen categories only. Destructive changes (removing things, tempo) always ask.
Loudness values in Studio are approximate integrated loudness. Check final masters with a certified EBU R128 meter if you’re delivering to a spec.
Sign in and credits
You don’t need an account for the DAW. Recording, editing, mixing, plugins and export all work signed out, and the AI panel shows Local only. To use the cloud AI, click sign in at the bottom right of the status bar and use Google or your Mozonic email and password. It’s the same account as the web app.
AI features use credits: 1 credit is 1¢ of usage. Your balance is the cr chip at the top of the AI panel. Starter includes 500 a month, Pro 2,000. To buy more, click the chip or ⋯ → Buy credits; checkout opens in a secure Stripe window, and credits appear a few seconds after payment clears.
If you see Out of credits, or “Insufficient credits: this request could cost up to…”, buy a pack or wait for next month’s allowance. “Daily AI spending cap reached” resets the next day.
Export your mix
File → Export Mix… (⇧⌘E) renders the whole session at the session sample rate, with dither. Formats: WAV (24-bit), AIFF (24-bit), or MP3 (320 kbps). Export Stems… writes one 24-bit WAV per track, and Export MIDI… saves MIDI clips.
If the export dialog warns about clipped samples, turn the master down and export again.
MP3 needs the free LAME encoder. If export fails with “MP3 export needs the LAME encoder”, install it with Homebrew: brew install lame. Then export again.
Projects, autosave and crash recovery
Projects are .mozonic files; double-click one in Finder to open it. File → Save as Template… and New from Template… keep a starting point you reuse.
Studio autosaves every 30 seconds. If it didn’t shut down cleanly, the next launch offers Recover or Discard. After recovering, use File → Save As to keep the session under a real name.
Troubleshooting
A plugin shows red and italic, or says “(plugin missing)”. It crashed or failed to load. Plugins run outside the audio engine, grouped by manufacturer, so the rest of your session keeps playing while that vendor’s plugins pass audio through. To bring it back, run a plugin scan again, or remove the plugin and add it back.
No sound. Check the Output device in Audio Settings, press Start audio, and try the test tone. Make sure the Session rate matches the device rate.
“Engine failed — click for details”. Click the chip to open Engine Diagnostics (also under the gear icon) and press Restart engine. The same panel shows the app and engine versions and the location of the log file.
Contacting support. Include the app version and the log file. Engine Diagnostics shows both, including the exact path to desktop.log.
Updates
Studio downloads updates in the background and installs them when you quit; macOS shows “A new update is ready to install” once one has downloaded. If you installed 1.0.0 on launch day, download Studio again once. Automatic updates began with 1.0.1.
Keyboard shortcuts
Spaceplay/stop ·⇧Spacerecord ·Returnback to startLloop ·Kmetronome⌘1/⌘2/⌘3Edit, Mix, ArrangeBBrowser ·⇧AAI panel⌘Tnew audio track ·⇧⌘Tnew MIDI track⌘Zundo ·⇧⌘Zredo ·⌘Ssave ·⇧⌘Eexport mix
Press ? in the app for the full list.
Uninstall
Quit Studio and drag it from Applications to the Trash. Your projects stay wherever you saved them. Settings, autosaves and logs live in Studio’s Application Support folder (Engine Diagnostics shows the path); delete it too for a clean removal.
Something here doesn’t match what you see? Tell support — include your app version and what you were doing.