Reference
Troubleshooting
Trace a problem from the source to the output.
In this guide
No sound
Check the output device and physical headphone/speaker connection. Check Master and track levels, mute, solo and routing. For MIDI, check the selected instrument, controller input and monitoring. For audio input, check microphone permission, Capture Audio channels, hardware gain and I monitoring. Use meters to find the point where activity stops.
Sound but no recorded region
Check record arm on the intended track and whether Record actually started. Review Punch boundaries and count-in. Selecting or monitoring a track does not necessarily arm it. After stopping, wait for the take to finish saving and read any error message.
Double sound or delay
You may be hearing both hardware direct monitoring and software monitoring. Choose one path. Use wired monitoring for a timing check. Reduce the buffer only when the computer can sustain it; reported latency does not include every part of a physical listening path.
Clicks, dropouts or high load
Stop, increase the buffer and test again. Bypass demanding processing one device at a time. Check sample rate and the audio device's own control application. If using an installed plug-in, test a saved copy with that plug-in bypassed and preserve its state.
For the different treatment of MIDI-only and audio takes during sustained playback dropouts, read Playback dropouts during a MIDI take. Continuing a MIDI take preserves the recording workflow; it does not make interrupted monitoring reliable.
A shortcut does something unexpected
Click the intended editor and check Settings → Shortcuts. Text fields, dialogs and MIDI Keyboard have their own key contexts. Numbers select arrangement tools. In the arrangement, 0 mutes the selected track. In Clip → Notes, 0 mutes selected notes; in Steps it mutes the selected pitch row. Click the intended editor before using the key. The legacy Shift-number workspace shortcuts are removed.
I can only see a few note pitches
Turn Fold off to see unused pitches. Scale limits the view to scale pitches and any existing out-of-scale notes; turn it off for all 128 MIDI pitches. Scroll vertically through the keyboard or Steps rows. Notes and Steps share these filters.
Notes or automation look unchanged
Open the correct Clip and check the active tool. A scale setting is a reference and does not automatically rewrite every existing note. For automation curves, create two points at different values first. Check for a manual automation override if playback does not follow a lane.
Ask for help
Email apps@iacompa.com with the build, macOS version, device/plug-in names, exact steps and the observed result. A small screenshot or minimal example is more useful than an entire private recording. Remove personal information and share only material you have permission to send.
Keyboard is too large or notes keep sounding
Use the keyboard percentage button to reset to 100%, or focus its corner grip and press Home. A small window can reduce the displayed size; below the readable minimum, scroll inside the keyboard to reach controls. Escape releases held software notes. Closing the keyboard or losing app focus also releases them. Check the destination track before playing again.
Audio waveform is still loading
A loading or error message is different from an empty audio recording. Wait for loading to finish, read the error if it fails, and preserve the project and original file. Use Fit audio to bring the current occurrence into view. Check Warp / Pitch and waveform offset before changing the source timing.
Audio-engine error
If Audio-Engine Error offers Restart Engine, check the output connection and selected audio device, then choose Restart Engine once. This restarts audio; it does not undo your project edits. Wait for the result before trying playback again.
In version 1.3.0, edits after an audio output fails to reopen no longer keep the studio trapped in a retry loop. A successful Restart Engine clears the earlier project-change error. If the restart fails or a new error occurs, that failure remains visible. This recovery does not remove the underlying device or plug-in problem.
If another error appears, read that error and preserve the project. Do not delete a plug-in or its saved state just to dismiss the message. Once the studio is available, save your work or a separate copy. If restarting still fails, report the build, selected device and exact error using Ask for help above. A restarted engine is not proof that every connected device or plug-in is working correctly.
Dawnamite user guide for macOS. For changes between versions, see update history.