bach: automated composer’s helper


Authors: Daniele Ghisi and Andrea Agostini

bach: automated composer’s helper is a cross-platform set of patches and externals for Max, aimed to bring the richness of computer-aided composition into the real-time world.

bach provides you with two new data types: rational numbers and lllls (an acronym for Lisp-like linked lists), the latter being a list capable to contain other lllls in itself, a bit like a Lisp list. In addition to that, it includes a large collection of tools for operating upon these new types and a number of advanced facilities and graphical interfaces for musical notation, with support for microtonal accidentals of arbitrary resolution, measured and non-measured notation, polymetric notation, support for MusicXML files and much more.

bach is a completely independent project by composers Andrea Agostini and Daniele Ghisi. For this reason its main focus is on musical representation, analysis and composition. Nonetheless, the data types it provides, along with their related tools, may have a much broader area of application.

bach is distributed as freeware and is still in the alpha phase. To obtain the latest version of this software, please refer to the official website www.bachproject.net.



Tatiana Catanzaro
September 7, 2012 | 5:33 am

Hi!
I’m having a problem trying to export a poly (OM) to finale. Neither the ETF nor the XML keeps the velocity information on the file. When I open it in Finale, the dynamics are all the same (velocity=64) for all the notes! So, I wonder if I can do that through Bach in order to export it correctly with all the velocity information to finale.
Thank you in advance!


February 16, 2013 | 12:49 pm

Hi Tatiana,
sorry for the late answer… did you already contact Andrea privately?
Please refer to the bach official forum (forum.bachproject.net) to post any question or bug report!

Thanks,
Daniele



jbm
August 24, 2013 | 1:41 pm

First of all, brilliant work!
Just wondering, though, whether there’s a 64-bit version in the near future?


Viewing 3 posts - 1 through 3 (of 3 total)