Lists

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

The legacy of kAudioUnitRenderAction_OutputIsSilence

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

The legacy of kAudioUnitRenderAction_OutputIsSilence

Subject: The legacy of kAudioUnitRenderAction_OutputIsSilence
From: Evan Olcott <email@hidden>
Date: Thu, 23 Feb 2006 09:03:43 -0600

Hey everyone.

I found an interesting situation with the kAudioUnitRenderAction_OutputIsSilence flag that I'm not sure I understand.

I've got a graph setup where I'm using a (slightly customized) AUStereoMixer with many input busses. I also schedule automation for AUs in the graph (previous to the mixer) in my preRender call.

If one of the render calls connected to one of the busses returns kAudioUnitRenderAction_OutputIsSilence, any buss after that buss will have it's scheduled automation "de-scheduled". Not just it's own buss (I can't prove that - no audio to prove it against), but all the busses after it are affected.

I can whittle it down to simply using or not using the "kAudioUnitRenderAction_OutputIsSilence" flag - what is it doing in terms of scheduling automation as opposed to processing buffers?

BTW - my modified AUStereoMixer doesn't do anything special with the kAudioUnitRenderAction_OutputIsSilence flag at all - I'm using the base classes for creating the custom AU.

Anyone have any ideas? I'd love to use this flag to get as much optimization as possible, but I also need the automation...

-ev

_______________________________________________
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



Prev by Date:
AudioConverter buffer size questions

Next by Date:
Re: Hardware Plugins

Previous by thread:
AudioConverter buffer size questions

Next by thread:
Recognizing iSight as audio input device?

Index(es):

Date
Thread