On 03.08.2012, at 14:14, Julia Truchsess <[email protected]> wrote:
> If I could rely on each PortMidiEventMBS actually carrying 4 bytes then it > would be very easy to pad the hex strings appropriately, but PortMidiMBS does > not seem to implement a constant 4-byte pmEvent structure and I don't see how > I can accurately reconstruct the sysex data without knowing how many bytes > each PortMidiEventMBS carries." > > IIRC, Christian did not seem too interested in fixing MBS, I was working > under an urgent deadline, and Mel Patrick (Hi Mel!) came to my rescue, > sending me some sample code that got me started with WindowsMidi and Mac OSX > midi classes. PortMidiEventMBS includes the full PmEvent. The RawMessage message property gives you the whole 4 byte message. Or you use RawData0 to 3 properties which give you individual bytes. Or you use normal Status/Data1/Data2 properties for normal midi messages. All those properties are settable in case you need. And also I have Set and SetRaw methods to set all properties together. Is there anything wrong? > I would certainly be interested in an MBS-Midi sub-mailing list. I have > learned a few things about Windows Midi that might be useful to others, > especially if trying to do automatic device recognition, as my app does. As > Mel says, under Mac OSX everything pretty much Just Works. You can just use this list and maybe include midi in the subject, so people not interested in midi can filter it. Greetings Christian -- Check out the Omega Bundle: http://www.omegabundle.com/ _______________________________________________ Mbsplugins_monkeybreadsoftware.info mailing list [email protected] https://ml01.ispgateway.de/mailman/listinfo/mbsplugins_monkeybreadsoftware.info
