I am very interested in this - can you post details of HUBIE?
As I understand it, the real requirement is for a proper multi-process
device driver for MIDI (which many are not) - ie one app writes MIDI
messages, and another reads them. I have heard of commercial
applications which do this sucessfully, eg the output of a  pitch/MIDI
converter program being read directly by Logic Audio, etc. So I have yet
to be convinced this is really a failing of Win95. It IS multi-tasking,
but the 'standard' Windows MMedia spec for MIDI does not appear to
provide for internal pipes between MIDI OUT and IN.

On the other hand, if I have got this completely WRONG, I would love to
hear how it can be done!

Richard Dobson




Lonce LaMar Wyse wrote:
> 
> I have used the HUBIE MIDI loopback utility to run one application
> generating MIDI msgs, and directed them to a simultaneously running
> CSound process. I did this under Win95 and proved (yet again) what a
> sorry OS it is. It "worked", but the sound was breaking up horribly
> and no tweaking of buffer sizes was going to fix the fundamental
> scheduling problem.
> 
> Of course, the ADI extended csound runs great driven by a MIDI
> generaating application. The other alternative to compensate for the
> lack of Win95 support for real multiple processes...
[snip] 
> Lonce Wyse