I guess the old python control stuff I did is by far outdated and not working ;-). I'm planning to move up to new MusE sometime, if it isn't fixed then, I'll probably do something about it. However, I used it to be able to control MusE from my Line 6 floorboard. I was able to control locators and did some experimentation with stepping back and forth while playing. It would make it possible to play to backgrounds live but not have a fixed scheme (e.g. play the chorus one more time).

/Mathias

2012/10/2 Martin Drautzburg <Martin.Drautzburg@web.de>
On Tuesday, 2. October 2012 10:27:41 Robert Jonsson wrote:
> Hi Martin,
>
> Old mails, good times :)

Yeah. It took some time to swap those ideas back in. Especially the 2nd
(unfinished) possibility. But the more I think of it, the better I like it.
IIRC it allows writing any sort of frontend to muse.

This seems to be much closer to the natural production process of music, where
you start with vague ideas, draw some sketches, write some phrases and then
"render" it all into sheet music. Finally the sheet music is performed by
musicians. Only the this last step (performing) is supported by muse. All the
early steps are entirely unsupported by software.

Even if you write such SW yourself, you could not hook it up with muse other
than writing midi-files and importing them (I did that a couple of times with
MMA). But it is tedious, especially when not all parts of the song are
controlled by this frontend and you want to do several iterations.

I encountered a similar issue when processing vocal tracks with melodyne. Here
I had to import wave tracks.

> There are two scripting possibilities in MusE.
> 1. simple but quite powerful. In the pianoroll you have a Plugin dropdown.
> The plugins listed there are scripts operated through a pipe,

Alright! Yes that works and the pluging sources are quite legible. Initially I
didn't understand that you have to mark the events you want processed. I am
not sure what to think of that. When you mark some non-adjacent events and
process them with double-speed you get "interesting" results. However, for
other plugins this makes quite some sense. It is a bit tedious to open the
pianoroll editor for each part when you e.g. want to process an entire track,
but given the fact that I don't have any scripts it is certainly good enough
for now.

I suppose those scripts can be any executable which can read and write files,
or does it have to be python?


> 2. Which is what is described below I think, this is unfinished work and as
> far as I know this does not compile. WillyFoobar on the devel list has
> expressed wishes to fix this, atleast the compilation problems.

That would be way cool.

------------------------------------------------------------------------------
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
_______________________________________________
Lmuse-user mailing list
Lmuse-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lmuse-user