Reference
Save, reopen & export
Keep editable projects and deliver audio for listening.
In this guide
Project versus audio file
A project keeps the editable arrangement, notes, routing and settings. A mixdown is an audio file for playback. Exporting a mixdown does not replace saving your project, and saving a project does not create a finished listening file.
Save and make versions
Use Command+S or File → Save. Save As makes a separate project copy with a new name and normally continues in that copy. File → Save Copy… saves another copy while leaving the current project open. Its later edits and unsaved state stay with the current project. Canceling the save dialog leaves it unchanged.
Recent Projects and Open return to saved work. Previous Versions and autosave recovery can help recover earlier states, but keep independent Project Bundle exports as well. If you edit while a save is finishing, those later edits still need saving; an older completed save does not remove their newer recovery copy.
Revert or close a project
File → Revert to Last Save… returns to the last explicit save. Save a new project before using it. With unsaved changes, choose Don't Save to discard those changes and load that saved version. Cancel keeps the current work. Save keeps your changes by saving them instead of reverting. A failed read leaves the current project open.
File → Close Project returns to the project chooser. With unsaved changes, Save must finish successfully before closing; Don't Save discards them; Cancel keeps the project open. Stop recording before reverting or closing. Export a Project Bundle first if you need an independent copy of the current work.
Export a project copy
Choose File → Export → Project Bundle. Keep it somewhere separate from the application's local storage. Reopen a copy to confirm that the expected tracks and media are present. Do not clear application storage as a troubleshooting step without a verified backup.
Bounce audio
Choose File → Export → Bounce… for the combined output, or Stems… for separate rendered parts where supported. The Bounce dialog groups its controls into File, Range, Quality, Level and Tail. File chooses the format. Quality contains sample rate, bit depth or encoding quality, and compatible dither options. Level contains normalization and its peak or loudness settings. Available formats depend on the build's encoders.
Choose the Bounce range
- Whole project runs from the project start through the current End marker.
- All content (longest track) runs from the project start through the latest region end across all tracks. An earlier overlapping region can set this end even when a later region finishes sooner.
- Loop area uses valid timeline loop bounds, including when loop playback is off.
- Selected regions runs from the earliest selected start through the latest selected end.
The range summary shows its start, end and duration. Unavailable choices have an explanation. An invalid range is refused instead of silently replaced with another one.
Keep the sound tail
Tail → Sound tail adds time after the chosen range for note releases, reverb and delay. Choose None, a fixed duration or Until silent. New musical events stop at the selected source boundary while existing releases and effects can continue through the tail. A fixed tail preserves the requested output length.
Until silent has a 30-second cap. If audio is still detected at the cap, export asks for a longer fixed tail instead of accepting that audible edge. A quiet interval cannot prove that no sparse echo is scheduled later, so choose a sufficiently long fixed tail for long delays. Check routing and the selected range, choose Bounce, then reopen and listen to the resulting file.
Cancel closes the options dialog without starting a render. Export preparation also supports cancellation while rendering or encoding. One large render still needs full audio buffers, and oversized archives are refused rather than allowed to grow without a bound.
Stems use a stable project snapshot and a common output window. They render one at a time and keep their levels; they do not offer individual normalization. Independently processing stems through nonlinear master effects does not guarantee that their sum matches the full mix. Keep the editable project and compare the results before delivery.
Transfer between DAWs
Use DAWproject to import or export a project. Interchange may not reproduce every plug-in, automation detail or proprietary feature. Keep the source project and compare the transferred result rather than replacing your original immediately.
A save problem
If storage, a sample or a plug-in fails, preserve the open project and follow the message. Record the exact error and build, then contact support. Do not repeatedly discard changes or remove missing-device placeholders just to clear a prompt.
Export from the intended playback state
Stop recording before export and review the active range and scene performance tempo/meter. A performance override can affect the export even after playback stops. Inspect the Bounce or Stems dialog's actual options, then reopen the resulting audio. Keep the editable project and its original media independently of a stem or mixdown file.
Mastering tools
The existing Maximizer, stock effects, analysis/reference tools, loudness normalization, sample-rate and bit-depth choices, and dithering support a manual mastering process. Version 2.1 does not add an integrated mastering workspace or assistant. Compare at a matched listening level and check the actual encoded file before delivery.
Dawnamite user guide for macOS. For changes between versions, see update history.