Availability
DAWproject is available as of today with Bitwig Studio 5.0.9 and PreSonus Studio One 6.5.Introducing DAW Project
A new file format standard to exchange data between DAWs
Studio One 6.5 introduces a new open exchange format designed to let users share sessions across multiple DAWs. Today the only way to share projects between DAWs is to use OMF or AAF, or to manually export MIDI and audio data to then import it in a different software. This workflow is tedious and prone to errors or lost information.
This all changes with DAWproject. For the first time, users of DAWs from different manufacturers can exchange sessions in a format that includes all critical data. Starting with PreSonus and Bitwig, DAWproject (.dawproject) will be provided as a standard import/export format.
The DAWproject file format includes all time-related information, all track/channel information, audio/note/automation data and the states of the plug-ins used. In that, the format is far superior to other exchange formats such as OMF, AAF or Standard MIDI File.
The following types of data are currently supported in a .dawproject file*:
- Audio Tracks
- Instrument Tracks
- Folders
- Automation
- Mixer Channels
- Channel Insert and Send Effects
- VST2 and VST3 plug-in settings (AU coming soon)
- Markers
* Exchange limited to content that is supported by both Studio One and Bitwig Studio! Additional data such as lyrics, chords or video will be added in the future.
Here’s the complete list of features. For reference we’ve included a comparison with MIDI and AAF. The latter formats have different functions and intentions. The table is meant as a help to understand where DAWproject fits in. It covers a wider range of data relevant to DAWs and DAW-like applications.
| DAWproject | Standard MIDI Files | AAF | |
| Intended Use | Music Production | MIDI Sequencing | Video post-production |
| Time Format (seconds/beats) | Beats and seconds can be combined | Beats | Seconds |
| Audio |
Audio Events/Clips Fades Crossfades Amplitude Pan Time Warping Transpose |
Not Supported |
Audio Events/Clips Fades Crossfades Amplitude Pan |
| Notes |
Notes Note Expressions |
Notes | Not Supported |
| Automation |
Tempo Time Signature MIDI Messages Volume Pan Mute Sends Plug-in Parameters Built-in Device Parameters |
Tempo Time Signature MIDI Messages SySex Messages |
Volume Pan Video Related Parameters |
| Plug-ins | Stores full plug-in state and automation of parameters (VST2, VST3, AU, CLAP) | Not Supported | Not Supported |
| Built-in Devices |
Generic EQ Generic Compressor Generic Gate Generic Limiter |
Not Supported | Not Supported |
| Clip Launcher |
Clips Scenes |
Not Supported | Not Supported |
v1, Sep 26, 2023
What is it technically?
The format is a container which includes audio, notes and plug-in data along with the project and metadata structure represented as XML data. It is designed to be extensible and remains compatible even if certain data cannot be used due to differences in feature-sets.
How does it work?
Export:
Studio One: Go to the menu File / Convert To / DAWproject File…
Bitwig Studio: Go to the menu File / Export DAWproject…
Import:
Go to menu File / Open, or just drag and drop a DAWproject file onto your DAW window.
Read more about how Bitwig Studio 5.0.9 and Presonus Studio One 6.5 currently work with DAWproject. (LINK to Bitwig KB (and Studio One KB))
(Specifics to Bitwig Studio 5.0.9 and Studio One 6.5:
- Bitwig Studio imports Studio One Alias Clips as Clips
- Studio One doesn’t read Bitwig Studio Clip Launcher data (Clips and Scenes)
- Studio One AU plug-in data isn’t read by Bitwig Studio
- Bitwig Studio CLAP plug-in data isn’t read by Studio One
- Built-in generic devices: supported in Bitwig Studio 5.0.9. Coming soon in Studio One 6.5
- Studio One Video track currently isn’t supported in Bitwig Studio
Resources
The specification is available on Github (LINK).
Visit the Bitwig Press Area for images, logo and additional press material found in our digital press kit. (LINK)