Re: Scheduling Midi data using 'MidiReceived'
Re: Scheduling Midi data using 'MidiReceived'
- Subject: Re: Scheduling Midi data using 'MidiReceived'
- From: philippe wicker <email@hidden>
- Date: Fri, 10 Mar 2006 12:00:34 +0100
On Mar 10, 2006, at 4:17 AM, Chris Cianflone wrote: Hi all,
Anyone know if this has been addressed yet? I am pretty sure it wasn't addressed in Panther but I haven't checked Tiger yet.
Also, if we have to do our own scheduling, what is the best way to do it? It seems that the Time Manager (from the old classic Mac OS days) is not giving us very accurate timing anymore under OS X. Is this related to the following from Technote 2028: ▪ Carbon "interrupt" routines are simulated using preemptive threads
I have been doing a lot of research in this area and it looks like CAPThread (using the THREAD_TIME_CONSTRAINT_POLICY parts) might be useful here. Just looking for some direction. Unfortunately, I am pretty new to pthreads, etc.
The Mac OSX implementation of the POSIX API pthread_cond_timedwait gives quite accurate results. All needed POSIX calls are encapsulated within CoreAudio SDK's CAPThread and CAGuard files. I have wrote a small "demo" program, TimerThread, which uses these utility classes and that you can download as a zip file from:
in the download page.
Feel free to contact me if you have any question.
Thanks, Chris
Chris Cianflone MakeMusic, Inc. www.makemusic.com
|
_______________________________________________
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