From: martin <martin.drautzburg@we...> - 2013-10-07 19:35:38
been away for a while and just compiled 2.1.2. Great stuff.
What is the status of the pyro support? The README does not "recommend"
to compile it in. And when I tried, the build failed with undefinded
refererences to "PyInt_AsLong" and two others. Is this someting which
just doesn't work, or should I hunt problems in my system (I do have
tons of libpython* in my /usr/lib)
Why this is important to me:
There are a number of SW packages out there, which support algorithmic
composition and which allow creating abstractions (most notably
"hascore"). But I could not find any such package which supports the
tail end of the process, i.e. putting it all together and produce an
Most sequencers ONLY support the tail end, but provide nothing for the
front end, i.e. the composition process. You are left with very simple
editors and the option to practice and play your composition with a
keyboard. It is already refreshing, that muse allows for expressing
"repetition" via linked parts. But it is still a long way from there to
"creating arbitrary abstractions". And IMO it is nothing which should be
built into muse. Leave that to languages, which are good at that.
If we want to combine these two worlds, a remote controllable sequencer
would solve most issues. I could generate parts whith my algortithmic
composer and import it into muse. Now I can do this already today, but
imagine, I have to go through hundreds of edit-compile-run-import
cycles. I clearly do not want the mouse much to do this. I want to
generate something and attach the information, where it should go within
muse right away. Then a simple "doit" should take care of pasting it
BTW, I love the scripting support.