alga: Algorithmic automation for various DAWs
How to algorithmically control every aspect of music using familiar, robust tools: plugins, DAWs, etc. that have not been built with this in mind? I've partially solved the problem in MIDA — program that generates MIDI files using very simple and symmetric language. However, even though MIDA is a fine tool to create scores, it's not sufficient if you want to control everything. Initially I thought I could find some plugins that can algorithmically control other plugins, but there are no decent tools of this sort. How automation is handled in a traditional DAW? Well, you draw it in a separate track. Wouldn't it be a good idea to algorithmically perform exactly that: drawing of the automation track. This is simpler than it may seem: many DAWs allow to export tracks in XML format, and this is all we need to start our hacking.
[Skip to Readme]
|Versions [faq]||0.1.0, 0.2.0, 0.2.1, 0.2.2|
|Dependencies||aeson (>=0.7), alga (>=0.2.1), base (>=4.8 && <5), containers (>=0.5.5.1), data-default (>=0.5.3), exceptions (>=0.8), filepath (>=184.108.40.206), formatting (>=6.2), haskeline (>=0.7.1.3), hxt (>=220.127.116.11), megaparsec (>=4.2 && <5.4), mtl (>=18.104.22.168), optparse-applicative (>=0.11.0.2 && <0.13), path (>=0.5.3), path-io (>=0.3.1), random, text (>=22.214.171.124), tf-random (>=0.5), transformers (>=0.2.0.0), yaml (>=0.8.15.1) [details]|
|Copyright||Copyright © 2015–2016 Mark Karpov|
|Revised||Revision 1 made by HerbertValerioRiedel at 2019-05-20T21:13:59Z|
|Source repo||head: git clone git://github.com/mrkkrp/alga.git|
|Uploaded||by mrkkrp at 2016-02-24T14:15:14Z|
|Downloads||2741 total (10 in the last 30 days)|
|Rating||(no votes yet) [estimated by Bayesian average]|
Docs available [build log]
Last success reported on 2016-02-24 [all 1 reports]
Turn on development settings.
Use -f <flag> to enable a flag, or -f -<flag> to disable that flag. More info
Note: This package has metadata revisions in the cabal description newer than included in the tarball. To unpack the package including the revisions, use 'cabal get'.
For package maintainers and hackage trustees