dawproject
daw
| dawproject | daw | |
|---|---|---|
| 6 | 1 | |
| 723 | - | |
| 1.5% | - | |
| 7.4 | - | |
| 8 months ago | - | |
| HTML | ||
| MIT License | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
dawproject
- DAWproject: Open exchange format for DAWs
-
Bitwig and Presonus launch open DAWproject format
One 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).
-
DAW which saves projects to JSON / serializes to text? Version control?
Bitwig can export/import their DAW interchange format: https://github.com/bitwig/dawproject
- File format .dawproject !
- .dawproject - transfer projects between DAWs
daw
-
Bitwig and Presonus launch open DAWproject format
One 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).
What are some alternatives?
Launchpad95 - Improved Novation Launchpad scripts for Ableton Live