• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Leak while in Midi thread
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Leak while in Midi thread


  • Subject: Re: Leak while in Midi thread
  • From: Chris Reed <email@hidden>
  • Date: Tue, 21 Jan 2003 15:52:02 -0600

Create a new thread and a CFRunLoop for that thread. Then use CFRunLoopTimers on that run loop. This will have the same effect as using EventLoopTimer, I believe.

(I'm not 100% certain about the names of everything above--I'm used to the Cocoa equivalents.)

Cheers
-chris

On Tuesday, January 21, 2003, at 08:51 PM, Lubor Prikryl wrote:

Hi,
What do you mean to be the best way to get MIDI data from its thread in Carbon? I have double buffered these data and read by a function, called by (not idle, but still low priority) EventLoopTimer. But Carbon I/O thread has sometimes too many things to do to let the timer make its work. Is there a better solution - opening a special new thread? Which API to use in this case? I also tried to send an event (created outside the MIDI thread), but it blocks event queue.

Thanks for a hint

Lubor, DSound, www.dsound1.com
_______________________________________________
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.

References: 
 >Re: Leak while in Midi thread (From: Lubor Prikryl <email@hidden>)

  • Prev by Date: Re: Leak while in Midi thread
  • Next by Date: Unloading a sound driver
  • Previous by thread: Re: Leak while in Midi thread
  • Next by thread: indexed parameter rounding problem
  • Index(es):
    • Date
    • Thread