Latency and AUTimePitch
Latency and AUTimePitch
- Subject: Latency and AUTimePitch
- From: Ashley Allen <email@hidden>
- Date: Thu, 12 Jun 2008 16:48:14 -0700
Hi,
Just a few minutes ago I submitted an email regarding latency and AUTimePitch. In that email I described a simple AUGraph with two subgraphs (tracks) that have AUFilePlayer units at the end. Track 0 has an AUTimePitch unit that is programmed to beat match with Track 1. The latency introduced by the TimePitch unit is printed out below.
Track 0 Latency := 0.075904
Track 1 Latency := 0.000000
I assume I set the start time of the AUFilePlayers as shown below.
Track 0 startTime is being set to := 0.000000
Track 1 startTime is being set to := 0.075904
In the above scenario the tracks are not in sync.
In another test I added TimePitch units to both tracks. The TimePitch unit on Track 1 has a rate set to 1.0 which does nothing. The latency for each track is as follows:
Track 0 Latency := 0.075904
Track 1 Latency := 0.067460
I compute the starttime for each AUFilePlayer on each track by first determining which track has the greatest latency. In this case it's Track 0. I then set the start time of each track to the difference between the greatest latency and the track latency which gives me the following start times.
Track 0 startTime is being set to := 0.000000
Track 1 startTime is being set to := 0.008444
In this scenario the beats are in sync when played back. I realize I should not have to put TimePitch units on all tracks to get the timing of the tracks to synchronize if only one track needs to be time pitched. I must be missing another latency component. All help is greatly appreciated. Thanks again. Sorry for the flurry of questions.
Ashley
_______________________________________________
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