• 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: RemoteIO glitches - cured by propListener audio route change?!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: RemoteIO glitches - cured by propListener audio route change?!


  • Subject: Re: RemoteIO glitches - cured by propListener audio route change?!
  • From: Morgan Packard <email@hidden>
  • Date: Sat, 8 Jan 2011 18:27:28 +0000

I'm brand-new to C++ but am finding I like the feel and syntax more than Objective C, so I may be happier all around just switching to C++ for audio. 
thanks!
-Morgan

On Sat, Jan 8, 2011 at 6:17 PM, Kyle Sluder <email@hidden> wrote:
On Fri, Jan 7, 2011 at 6:41 PM, Morgan Packard <email@hidden> wrote:
> Your post has scared me a bit, since I've been using Objective-C
> extensively. I've been getting some conflicting bits of advice regarding
> whether it's appropriate to call objective-c code from the RemoteIO
> callback. Do you have more specific ideas about what was causing your
> glitches? Was it the non-cached selector calls described
> here http://lists.apple.com/archives/cocoa-dev/2006/feb/msg01735.html, or
> perhaps something else involving locks?

The advice is quite clear: do not call objc_msgSend from your render
callback or anything that gets called by it. This means no calling
Objective-C methods using [foo bar] syntax.

Calling cached IMPs is fine, but only if those IMPs don't themselves
call objc_msgSend.

Under the current runtime, there's a very small chance that calling
objc_msgSend will cause glitches. But since the number of things you
need to do in a render callback is so small and well-defined, there's
very little reason to be using Objective-C anyway.

Render callbacks are very much a "get in, get it done, get out"
situation. If your current architecture will not function without the
dynamic features of Objective-C, that's a good indication that it's
too complicated to fit into a render callback in the first place.

--Kyle Sluder
 _______________________________________________
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



--
================================
Web:
http://www.morganpackard.com

Mobile Phone:
(646) 206-8337

Music/Art:
Album Moment Again Elsewhere available Oct 11.
iOS app Thicket available on iTunes store.
================================

 _______________________________________________
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

References: 
 >Re: RemoteIO glitches - cured by propListener audio route change?! (From: jhno <email@hidden>)
 >Re: RemoteIO glitches - cured by propListener audio route change?! (From: Morgan Packard <email@hidden>)
 >Re: RemoteIO glitches - cured by propListener audio route change?! (From: Kyle Sluder <email@hidden>)

  • Prev by Date: Re: RemoteIO glitches - cured by propListener audio route change?!
  • Next by Date: Re: Send midi to host application
  • Previous by thread: Re: RemoteIO glitches - cured by propListener audio route change?!
  • Next by thread: Ambient/mixable sessions: adjust volume of ambient source?
  • Index(es):
    • Date
    • Thread