Re: AUTimePitch with the MusicPlayer/AUGraph
Re: AUTimePitch with the MusicPlayer/AUGraph
- Subject: Re: AUTimePitch with the MusicPlayer/AUGraph
- From: Brian Whitman <email@hidden>
- Date: Tue, 18 Apr 2006 20:00:24 -0400
If anyone's interested, I narrowed this down to 2 "facts":
1) You can't have the same audio stream go through both an
AUTimePitch and a "normal" effect AU in the same graph (i.e where
both are output, not in a chain.) I was trying to "split" an
ScheduledSoundPlayer with a MatrixMixer or Splitter into the tmpt and
a sample delay to account for the latency. The time stretched output
cuts out the moment you change the stretch rate < 1.
2) You have to account for "actual play time" on your own if you have
a AUTimePitch format converter in your graph. That is, you can't
schedule a slice at 44100 and expect it to play a second in if you
have any rate other than 1.0.
If either of these are wrong, I'd appreciate corrections.
On Apr 16, 2006, at 8:05 PM, Brian Whitman wrote:
The actual result is that the AUGraph "speeds up"-- at MusicPlayer
time 1.0s, the AUGraph will have read 2.0s worth of samples. My
second frame plays right after the first, at mTimeStamp 22050. I
really just hear the slices one right after another, playing twice
as fast. This screws up the MusicPlayer's "clock" connecting to the
AUGraph-- I can no longer schedule events at the right position if
I don't know what the AUGraph time is. I'm not sure if this is a
bug or a bad implementation on my part.
_______________________________________________
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