interapplication midi communication, cfmessageports, ques
interapplication midi communication, cfmessageports, ques
- Subject: interapplication midi communication, cfmessageports, ques
- From: "Alex Sheh" <email@hidden>
- Date: Thu, 23 Feb 2006 18:26:53 -0800
- Thread-topic: interapplication midi communication, cfmessageports, ques
Hi All,
In my MIDI driver, there is a
CFMessagePort’s run loop source added to the current run loop. This MIDI
driver is used to pass MIDI data between 2 applications on a system, however
lately I have been seeing some issues that may be related to latency on this
communication channel – it also involves large amounts of MIDI data are passed
through over a long period of time.
Does it make sense to instead add my MIDI driver’s
run loop source to the realtime IO run loop? Although when I call
MIDIGetDriverIORunLoop( ) it returns NULL, is this normal? Do
CFMessagePorts seem reasonable for what I am doing (interapplication, low
latency)? Also, I’m not really clear as to how CFMessagePorts handle flow
control, in cases where there is a lot of MIDI data sent across does this data
start “piling up”? What about compared to MIDIPortRefs?
Thank you for
your help.
- Alex
_______________________________________________
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