> Using git itself is a little problematic because it is very line-oriented and most project file formats for DAWs are not.Īrdour and Reaper use plaintext project formats that work well with Git, at least for basic versioning. It sounds to me as if you've worked with a relatively small number of DAWs on only Windows and macOS and are not really aware of the breadth or depth of the "field". You can use oscsend(1) to control plugins inside several different plugin hosts.
You can also run plugins from the command line by using standalone plugin hosts. There are things close to DAW functionality that have a CLI (such as ecasound). The problem is that most users want more functionality than a DAW itself could feasibly provide (they also sometimes like to use the same functionality (plugin) in different DAWs or different workflows). Regarding plugins, I know that I'm not the only lead developer of a DAW who, if they possibly could, would refuse to support plugins entirely. Using git itself is a little problematic because it is very line-oriented and most project file formats for DAWs are not. > Imagine if they applied something similar to a git versioning system to music projects. Also consider that there are no good audio drivers for Linux (like Asio for example) so you're almost forced to stay in windows or Mac.
0 kommentar(er)
