From: Ian Gardner <ilgardner@ya...> - 2010-09-18 22:23:38
----- Original Message ----
> From: Ian Gardner <ilgardner@...>
> To: Chris Cannam <cannam@...>
> Cc: D. Michael McIntyre <michael.mcintyre@...>;
> If I'm feeling brave/foolish/drunk enough over the coming days/weeks I might
> have a look at how you "do midi" on windows. Maybe Jack2 can help out with
> Dunno yet. I don't think ALSA can run under cygwin, I'd be mildly astonished
> it did but I could be wrong.
Has anyone ever had a play with the midi examples in the jack source code? Two
of them might be of interest:
midiseq.c is a little app which generates a loop of midi on/offs and writes them
to a jack midi buffer. When you run it you see it as a midi output port in
qjackctl. I've run it and connected it to qsynth which receives the midi ok.
midisine.c is an app which responds to midi on/offs read from a jack input
buffer by writing sine wave data to a jack output buffer. I've tried it by
connecting up vkeybd to it again via qjackctl, and it worked.
So given these mechanisms for writing to and reading from jack midi ports, is it
in principle possible to write something like "JackMidiDriver" as a subclass of
SoundDriver to do the midi magic with jack api as an alternative to AlsaDriver
on windows? I'm making massive assumptions about being able to use the jack api
to query all the hard and soft midi devices on the system, and all the other
stuff which goes on in the 5000+ lines of AlsaDriver.
'scuse the ongoing ramblings about this - I keep trying to forget about it and
do other things but I find my mind being drawn back to it...