-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
.dawclip format #53
Comments
This is a good idea, and reminds me of when Renoise switched to xml documents for a lot if its data - this idea that subdocuments of a whole project can be useful on their own is incredibly powerful. Another innovation they had (have?) is that the clipboard formats were also xml, we did a lot of generative composition by writing software that put interesting data on the clipboard which could be pasted directly into the running application. It felt very 21st century, and I'd love to see this project evolve in that direction. |
Sounds like midi files. |
basically an an additional, stripped-down version of dawproject. It would contain only the part of dawproject elements/attributes relevant for storing/loading a single clip or scene of clips. So it is basically equivalent to .bwclip/.bwscene files which, besides clip data (audio events, note events, automation, stretch markers, ...) contain additional information (such as metadata, devices, track properties, routing,...)
In Bitwig but also other daws a .dawclip file could then be dropped into a free clip launcher slot or into the arrangement.
As .dawclip could be a subset of .dawproject, it could use the same source files.
The text was updated successfully, but these errors were encountered: