Re: Who is calling my MIDIReadProc?
Re: Who is calling my MIDIReadProc?
- Subject: Re: Who is calling my MIDIReadProc?
- From: Doug Wyatt <email@hidden>
- Date: Mon, 11 Oct 2004 10:24:45 -0700
On Oct 6, 2004, at 18:34, Alex Rosenberg wrote:
When I play an SMF from another app (like Rondo or Sweet) my
MIDIReadProc is called with a srcConnRefCon of NULL.
I neither see a source when I scan at launch, nor is my notifyProc
called to inform me of the source.
Can I be assured that srcConnRefCon will be NULL if I didn't connect
to that source?
Note that I see a source appear and give it a refCon for apps like VMK.
Not always seeing a source properly is going to make it hard to
support virtual control surfaces since they can't be identified.
So if you set a breakpoint at MIDIPortConnectSource(), your app never
calls it and yet you begin receiving MIDI?
Does your app create any virtual destinations with
MIDIDestinationCreate()?
I can't think of a way that your app would start receiving input from a
source you didn't connect to, unless you have created a virtual
destination. If you have a virtual destination, then anyone can send to
you at any time and the srcConnRefCon in the readProc will be the
refCon you passed to MIDIDestinationCreate().
Otherwise, it's a bug -- please file one.
Thanks,
Doug
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden