It would be nice if Bitwig would support existing plug-ins formats like AU.
DAWproject: Open exchange format for DAWs
11–20 of 93 posts
Re: DAWproject: Open exchange format for DAWs
#12Nice idea, but not useful unless each DAW manufacturer supports the format. And there are a lot of DAWs.
Well, you have to start somewhere.
Re: DAWproject: Open exchange format for DAWs
#13XML, why? And... 99% of the issues will be around plug-in management.
What would you propose? Json?
Re: DAWproject: Open exchange format for DAWs
#14Nice idea, but not useful unless each DAW manufacturer supports the format. And there are a lot of DAWs.
MIDI was enthusiastically supported by Yamaha and Roland, two of the biggest synth players of that era.
So I imagine, for it to become widely successful, that this new standard would need the wholehearted support of at least 2 of Steinberg, Apple, Ableton, and Avid.
Re: DAWproject: Open exchange format for DAWs
#15Bitwig is quickly becoming my favorite DAW. Big fan of how they develop software.
Bitwig knocked it out of the park coming out the gate with Linux support. Can't say I'm surprised though, it's made by the original team that made Ableton Live.
Re: DAWproject: Open exchange format for DAWs
#16One thing I'd like to see is native support for some notion of pitch other than 12-tone equal temperament.
Looking at their example, I see this:
...which looks like it's basically just a representation of the underlying midi.
One way they could represent other pitches is for "key" to allow a floating point value rather than an integer. So, for instance, 65.5 would be a quarter-tone (50 cents) above note 65.
According to their reference document, "key" is currently required to be an integer:
https://htmlpreview.github.io/?https://github.com/bitwig/daw...
There's other ways to support microtuning. They could apply a tuning table to the midi notes, for instance. (Ideally they should support more than the 128 notes that midi supports, because 128 isn't enough for some use cases.) They might also allow you to apply pitch bend to individual notes (which isn't allowed in midi 1.0 but was added to 2.0).
Re: DAWproject: Open exchange format for DAWs
#17One thing I'd like to see is native support for some notion of pitch other than 12-tone equal temperament. Looking at their example, I see this: ...which looks like it's basically just a representation of the underlying midi. One way they could represent other pitches is for "key" to allow a floating point value rather than an integer. So, for instance, 65.5 would be a quarter-tone (50 cents) above note 65. According…
At this layer of note information, fact is the data will be either sent to a MIDI device or a plugin as a MIDI event, so you might as well keep it in the native format and not convert to a frequency.
Re: DAWproject: Open exchange format for DAWs
#18It would be nice if Bitwig would support existing plug-ins formats like AU.
Do you encounter many AU-only plugins? From what I can tell, the limitations of VST/AU/AAX are more pressing and Bitwig are working to address that with CLAP: https://u-he.com/community/clap.
Re: DAWproject: Open exchange format for DAWs
#19If the goal is widespread industry adoption, I'd recommend the approach of extending a professional, standards-based interchange format already supported by major DAWs: AAF.
https://en.wikipedia.org/wiki/Advanced_Authoring_Format
https://www.loc.gov/preservation/digital/formats/fdd/fdd0000...
Re: DAWproject: Open exchange format for DAWs
#20If the goal is widespread industry adoption, I'd recommend the approach of extending a professional, standards-based interchange format already supported by major DAWs: AAF. https://en.wikipedia.org/wiki/Advanced_Authoring_Format https://www.loc.gov/preservation/digital/formats/fdd/fdd0000...
The README extensively references AAF.