Re: More: Time Stamps across different busses/through AUConverters

Bill

On 22/11/2006, at 9:42 AM, Evan Olcott wrote:

Further investigation finds the following:

As soon as a sample rate is changed on one of the AUConverters, the timeStamp throughput value is changed. In fact, it seems as though the timeStamp numbers themselves reset within the converter, and there exists a sort of offset after they've been changed. Even if the values are the same as they were previously, simply the call to:

AudioUnitSetProperty(audioUnit, kAudioUnitProperty_StreamFormat, kAudioUnitScope_Input, 0, &streamFormat, streamFormatSize);

(audioUnit is the AUConverter) - will somehow "reset" the timeStamp throughput and make an offset of sorts. The timeStamp inside the mixer, after that point, is not the same one showing up at the render callback.

Is this expected behavior?

What can I do to sync up these various busses into the mixer? Where can I find, at the very least, a common start point where each buss can at least then fly off on their own?

-ev
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/coreaudio-api/email@hidden

This email sent to email@hidden

mailto:email@hidden

tel: +1 408 974 4056

__________________________________________________________________________

"Much human ingenuity has gone into finding the ultimate Before.

The current state of knowledge can be summarized thus:

In the beginning, there was nothing, which exploded" - Terry Pratchett

__________________________________________________________________________

References:
	>More: Time Stamps across different busses/through AUConverters (From: Evan Olcott <email@hidden>)