Re: MIDIPacketList behaviour problem
Re: MIDIPacketList behaviour problem
- Subject: Re: MIDIPacketList behaviour problem
- From: Doug Wyatt <email@hidden>
- Date: Fri, 23 Jan 2004 16:56:01 -0800
On Jan 22, 2004, at 15:44, Michael Harbour wrote:
I originally used .newMIDIPacketData(256) because 256 was one of the
few numbers i could get to make a Packet without throwing a
CAMemoryObjectException
I'm still not clear about the difference between newMIDIPacketData and
neRawData calls - do you get pre-built MIDI bytes inserted for you
into a MIDIPacket? I need to know what the key MIDIpacket abstraction
is and its relation to an n-byte MIDI protocol event.
The documentation in both Java and C APIs is _woefully_ thin (or
non-existent in the JavaDoc case) on building up packets from scratch
and sending them out.
All the nice architecture and layers and models aside, I would have
thought that MIDIPacket building was the absolute focus of this API
and yet I cant seem to find this emphasised anywhere - do these Packet
building docs exist anywhere on the Developers Tools CD and I havent
found them yet? I'll eat my hat and apologise if they are :)
Sorry, I have no experience or knowledge of the Java wrappers for our
API's.
As for using the C interface -- there is a presumption that you know
the MIDI spec. People who know the spec don't seem to have a hard time
understanding the comments in the C header -- that CoreMIDI deals with
MIDI-standard messages, with just a few restrictions on how they are
placed into MIDIPackets and MIDIPacketLists.
Doug
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.