Hi Isidro,

Thank you for the info. Reading the library you had mentioned, I got the impression that it currently does not support MIDI functions for Windows.

Similar to some of my posts from a while back, I am trying to learn what it takes to get Sysex working, this time under Windows.

Homebrew I/O devices are cool indeed. Meanwhile, there are a great variety of MIDI devices available in shops which require Sysex messages to fully utilize them. I find it a bit sad that I cannot easily prepare abstractions to work these devices.

For Linux, Sysex ([midiout]) seemed to be simply "fixed" in recent versions of Pd.

What more does it take to work it under Windows?

So far what I've learned from observation is that a C function, "midiOutLongMsg" must be utilized to send Sysex messages. In the current code I am reading (0.41-4) there are only midiOutShortMsg. Haven't looked in to receiving yet.

I will have to proceed with reading the internals a bit more before I can write anything myself.

-- David Shimamoto

If you don´t want to use the DirectX API, you could use sndlib by Bill Schoesttadt. Sndlib can be obtained at CCRMA of Stanford and allows Audio and Midi I/O. The MIDI functions are sparse but may match what you are looking for your purposes. This is the CCRMA WEB: http://ccrma.stanford.edu Best Isi

--- PSPunch shima@pspunch.com wrote:

...

Hi,

I understand that MIDI objects under Windows is said to be less stable than Linux, due to the MIDI functions under Windows API that Pd relies on.

If I were to write my own MIDI I/O external for Windows, are there such things as alternative MIDI libraries or APIs available, or does Windows not allow you to access MIDI devices it recognizes without running data through its interface?

Like some posts I made about a month back, my initial goal is to get raw MIDI in&out working, this time on Windows.

Any hints appreciated. Thanks.

-- David Shimamoto

---

Pd-dev mailing list Pd-dev@iem.at http://lists.puredata.info/listinfo/pd-dev