Tobiah wrote:
> 
> jpff@maths.bath.ac.uk wrote:
> >
> > Depending on how complex the MIDI file, I use Rosegarden for this.
> > ==John
> 
> The important thing is that the program be usable from
> within a Makefile.  I used to use a wrapper to midi2cs
> for this.  I would record a track on my midi keyboard,
> and then type 'make', which would build and audition
> a sound which relied on that midi file.  If I didn't like
> it, I would just re-record the keyboard part, and go 'make'
> again.
> 
> The greatest thing about command-line apps, is that command-line
> apps can run them.

How timely. I, too, am discovering the joys of using Make for music
composition. In my case, instead of using a MIDI sequencer, I'm using
csound to record MIDI in real time; the instrument both plays the the
sound and uses foutir to generate the csound score, which can be used in
a subsequent csound run. Since I have a slow machine, but still find it
best to play in real-time for creative purposes, I'm trying to set up
something like this, diagramatically speaking:


# Record a MIDI performance using a fast, but real-time instrument. 
# Use foutir opcode to generate a score so that this performance
# can be reproduced.
#
target1:
  ->   -> DAC
                                                   -> 1.sco

# In non-real-time, use the generated score to drive a fancier
# but slower, high-quality version of the first instrument. Save
# to a wave file for future overdubs.  
#
target1w:
  1.sco ->  -> 1.wav

# Now, in real-time, play along and add a second instrument!
#
target2:   
   ->      -- >|
    1.wav   ->  -- >|
                                                \
                                                  -> DAC
                                                  -> 2.sco


Well, this is as far as I've gotten in my little experiment,
but so far it seems to be working.

Larry Troxler