I agree it would be best to do this in csound 5. I wrote the existing MIDI
API, but I only actually used it for VST MIDI, not for general MIDI. I did
try to make it generic.

Original Message:
-----------------
From:  gml@xs4all.nl
Date: Tue, 30 Dec 2003 15:27:04 +0100 (CET)
To: csound-dev@eartha.mills.edu
Subject: [CSOUND-DEV:3853] midi in csound5


I looked at the csound5 sources and I am unsure of what the right thing to
do is.

This is partly because I don't understand the relationship between the api
functions and the rest of csound.

F.i. the api has a openMidiDevice function, but even if set to external
the openMIDIDevice function in mididevice.c is called anyway. And then
there is the openMIDIout function called from argdecode.c if the Q flag is
used, but only under Linux. With the added oddity that on linux the
argument is a number and on BEOS it should be a name.

So, besides switching to portmidi, the whole structure should be cleaned
up as well I think. One midiopen function (or two:one for reading one, for
writing) that can be changed with the api. Same goes for reading and
writing.

Anyway, it seems this touches on a lot of stuff that is discussed here and
that I don't understand (yet), so I will finish my jack-csound version
with midi-in only first and look into to this later. (and I am not even a
big midi user....)


Gerard


--------------------------------------------------------------------
mail2web - Check your email from the web at
http://mail2web.com/ .