Hi All, OK I've debugged the sysex.exe app by sending a few bytes of SYSEX msg from a file to my device. (P.S. would be nice to add a msg to the program explaining what the supported text file format is).
Seems that PortMidi is OK with respect to Sysex .. the mistake was mine. What happens is, a bunch of data gets sent upon opening the MIDI port .. in my case, my USB IN Endpoint buffer size is 64, and I'm seeing about 16 writes to this buffer. So it's a kind of initialization thing, that is probably managed by Windows' USB Audio device class driver. (p.s. anybody knows what 0BBF40000000000030303030303030303030303030303030000000000000000000000000000 means? The 17th write however is exactly the data I am expecting and decodes perfectly according to the USB-MIDI spec. Anyway thanks again for all the help! Gal. _______________________________________________ media_api mailing list [email protected] http://lists.create.ucsb.edu/mailman/listinfo/media_api
