Re: AUTimePitch -- edge artifacts
Re: AUTimePitch -- edge artifacts
- Subject: Re: AUTimePitch -- edge artifacts
- From: Brian Whitman <email@hidden>
- Date: Tue, 29 Nov 2005 10:56:09 -0500
Before I go insane listening to clicks all day, I put my code (based
on the Sinewave sample) up on my site for anyone who'd like to try it
out and tell me my problem.
http://variogr.am/Sinewave_AUTimePitch.zip
The sound that loops is in the bundle there. At a rate of 1.0 (no
stretch) the clicks are every 8192 samples, which is my buffer length
(where the Render call starts every time.) If someone could exorcise
those or educate me a bit more on how offline AUs are supposed to be
called I'd appreciate it. When it's fixed I'll post the final result
again for others' sake.
Thanks
Brian
On Nov 28, 2005, at 7:16 PM, Brian Whitman wrote:
Hi Chris, I see that the callback might get called multiple times
per render and goes over what you ask for.
Ignoring stretching (say the stretch was at 1.0) -- in my example,
I looked at the first callback and saw that it starts at synth
buffer position 0 and asks for 11920 samples total during the
render when I ask it to analyse 8192 samples.
But I can't then increase my synth buffer pointer by 11920
samples-- the next time I ask for 8192 samples I want those samples
to be read starting at synth buffer pointer 8192 as the returned
rendered data represents only 8192 samples.
So that was the purpose of "askFor"-- to advance the starting
position within the synth buffer every time I ask for more samples.
Internal to the AU callback, the mSampleTime takes care of sample
position within the analysis buffer.
I have a feeling I'm missing something obvious here though. I'll
keep playing with my pointers.
Brian
_______________________________________________
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