Re: RemoteIO glitches - cured by propListener audio route change?!
Re: RemoteIO glitches - cured by propListener audio route change?!
- Subject: Re: RemoteIO glitches - cured by propListener audio route change?!
- From: jhno <email@hidden>
- Date: Sun, 2 Jan 2011 19:48:35 -0800
I cured my mysterious audio glitches, by switching the objects used by my RemoteIO perform() callback from Objective C to C++.
I saw a reference to this phenomenon from James McCartney in the archives. Apparently Objective C selectors can invoke housekeeping tasks that can cause unexpected execution time.
In my case, the result was reliable and inexplicable audio glitches.
There was nothing fancy about the Objective C code. So this is something to keep in mind - !
jhno
---
On Dec 15, 2010, at 2:11 PM, jhno wrote:
> Greetings,
>
> I have an iPad app with an audio engine based very closely on the AurioTouch code example.
>
> When I start the app, the synthesized audio is interrupted by glitches - which seem to be comprised of unprocessed signal vectors that contain the microphone input instead of my synthesized output. In other words there are bursts about every second where the perform() callback is not invoked.
>
> The glitches go away completely when I plug headphones into or out of the iPad. My propListener is invoked, it calls SetupRemoteIO, makes a new RemoteIO, and everything is fine - !
>
> However, if I manually try to call my propListener by another mechanism (NSTimer, UIButton), the audio still glitches.
>
> Does anyone have any idea what could be causing this behavior?
>
> I have been looking into this for a long time now and am totally flummoxed.
>
> thanks,
> jhno
>
>
_______________________________________________
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