> CSound is still too cryptic / weird for the non-nerd.. tracking is less robotic..
>having
> real equipment is best
I dont know if I am a nerd. Rubo (of midi2cs fame) was very helpfull. I
have two batchfiles, one is realy important, that calls csound. All I have
to do is, after editing midi2cs's "midi2cs.pro" file (which is sotosay the
Gui of midi2cs) (1) to produce a midifile, lets say bla.mid, (2) to type
"midi2cs bla" and (3), this is the important batchfile, "cs bla".
No, I dont think I am a nerd, I just dont have problems with command line
interfaces. And I dont have the money for a real sampler. Btw, all
samplers have latencies, csound not. Not so important for this kind of
"music", I think, but who knows.
The most important thing to know is that samples must be "aif" (I think
they must be 16 bit too, but they are 16 bit anyway, and that they must
have names like "blablaf4.aif", with the note value at the end. You dont
need to know much more about the many dirs for samples etc, all files,
*.mid, *.aif, the midi2cs.pro file, the resulting *.sco and *.orc (for
csound, produces by midi2cs, thanks !) are in the same directory.
Anyway, it costs nothing, some thoughs, it has limits (you must use
drumloops like other samples, less interactiv than a real sampler), but
for me it was worth the try. There is a "makemusicfast.zip" containing
midi2cs, csound, loop.exe (which makes aif samples loop, if you havent got
Soundforge) and a Readme file, that is on the Leonardo Music Journal CD
and, well Owen has more important things to do, I could look for it and
put it into www.uni-bonn.de/~uzs106/, but you can get midi2cs and csound
also from Robos site, ask altavista for "midi2cs".
Heiko
