MIDI driver monitoring -- bad destination?
MIDI driver monitoring -- bad destination?
- Subject: MIDI driver monitoring -- bad destination?
- From: Kurt Revis <email@hidden>
- Date: Thu, 7 Mar 2002 23:22:56 -0800
Has anyone tried using the monitoring function in a CoreMIDI driver
(that is, implemented a Monitor() function on their driver)?
I am finding that the MIDIEndpointRef passed in as a destination is not
a real MIDIEndpointRef that I can use in other CoreMIDI calls. I'm
wondering if I'm doing something wrong, or if there is something else I
need to do to get a real MIDIEndpointRef.
Here's the details: In my Monitor() function I get a destination like
0x67580. This function is running in a CoreMIDI work thread, so I can't
do much of anything with the destination right there; most CoreMIDI
calls return kMIDIWrongThread. But, if I pass that MIDIEndpointRef back
to a function running in the main thread, trying to use it gives me a
-50 error (paramErr). (For instance, if I call
MIDIObjectGetIntegerProperty().)
Also, the destination given does not correspond to any of the
MIDIEndpointRefs which are returned by MIDIGetDestination(). Those are
all in a much different range of values, like 0x981000d.
Anyone have any ideas?
--
Kurt Revis
email@hidden
_______________________________________________
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.