Re: coremidi virtual endpoint problem
Re: coremidi virtual endpoint problem
- Subject: Re: coremidi virtual endpoint problem
- From: James Maxwell <email@hidden>
- Date: Mon, 20 Oct 2008 10:31:06 -0700
hmm... Actually, I'm wondering whether this has something to do with
the fact that virtual outputs, which are represented as sources (not
destinations), need to use MIDIReceived instead of MIDISend? I should
mention that this is for playback from a MusicSequence/MusicPlayer, so
it's MusicPlayerStart that outputs nothing when using my virtual
ports, but works correctly when using the IAC bus.
So is there some special way of dealing with MusicPlayerStart when
using virtual outputs?
I'm using the same call to MusicSequenceSetMIDIEndpoint in both cases.
J.
On 20-Oct-08, at 9:12 AM, James Maxwell wrote:
I'm setting up 4 virtual endpoints for my app - at this point these
are just sources, so they're for output to other apps. I'm using the
PYMIDI framework to simplify things, and they ports appear to
initialize correctly - no errors during init, and the ports are
visible to other apps. However, they won't send any midi data. If I
switch the assignment to the IAC Bus, midi is sent as expected, so
it's something to do with the endpoints I'm creating.
I contacted Pete Yandell (author of PYMIDI) about it, and he
couldn't see any problems in my code. So I'm wondering whether
anyone else has had virtual endpoint problems in 10.5.5, or if
anyone has experienced something like this and found a solution?
Thanks,
J.
_______________________________________________
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
_______________________________________________
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