| Well, there was the free CMU toolkit for Macintosh and unix. I think
people still use it but I dont know the version or whatever. It is
completely open ended and you could code until you cant code anymore all
of your home grown midi processes. On the PC the only thing that I know
of are small algo type programs in shareware form. I would think that
you would do better to code your own midi app instead of dealing with
csound and real-time midi control. I dont know.... maybe take the midi
sources from csound and roll your own app from them.... not my idea of
fun but..... Common music has all of this already and runs on many
platforms....
Michael
On Sat, 5 Apr 1997, Gabriel Maldonado wrote:
> Dear Jean,
> you wrote:
>
> > Gabriel,
> >
> > Compared to a myriad of other midi score processors/generators, Csound
> > is an extremely poor choice. Use Max, or better still, Common Music. You
> > already have real-time control input to Csound via console-driven events
> > (-L). Use it. THere are dozens of different ways to do granular
> > synthesis in Csound as it is. As a control language, Csound is very
> > terse and weak compared to just about anything else. You'd be better off
> > writing something new in another language (tcl, perl, C, lisp, anything)
> > to replicate the (simple) table referencing capabilities of csound and
> > moving on from there to more interesting things...
>
> Are Max and Common Music avalaible for win'95? Are these programs free?
> Do these programs manage midi in-out events and audio processing in
> realtime?
> Csound is a low level language. So its flow control is very terse. But I
> think it is not weak. I like low and high level scrambling and for me
> Csound, although far from being perfect, is a good tool. Maybe it is a
> personal point of view, but I think high level and graphical tools may
> influence compositive thought of a person (such as MIDI keyboards that
> conditionate musical taste of their owners) with the programmer's
> thought.
> Writing a complete new program that can manage dimamic event allocation,
> score and realtime IN and OUT is more time consuming than adding some
> UGs to Csound for me.
> I don't want influence anybody with my version of Csound; if someone
> like it, he can use it, else simply can ignore my new MIDI UGs.
>
> P.S.
> it is not my intention to spark off a flame about MIDI and control
> capabilities of Csound. I only asked some tecnical opinion about
> including these UGs in the standard version or making a new version. Now
> I think I will make a unique version with audio OUT which can be
> optionally disabled, if required.
>
> P.S. #2
> Can you help me to use the realtime console-driven events (-L flag)? I
> attempted to use it but I can't hear any sound. What is the syntax of
> console line events? I used the standard Csound .sco syntax, but with no
> results.
>
> Best regards
> --
> Gabriel Maldonado
>
> mailto:g.maldonado@agora.stm.it
> http://www.agora.stm.it/G.Maldonado/home2.htm
>
|