Re: multiple AUGraphs / Audio Hijack
Re: multiple AUGraphs / Audio Hijack
- Subject: Re: multiple AUGraphs / Audio Hijack
- From: Brian Whitman <email@hidden>
- Date: Thu, 2 Nov 2006 17:39:29 -0500
It depends on where you are getting your input from - that is,
where do these two time pitch AUs expect to get their input from
and how are you handling the buffering requirements for these two
different AUs running at different rates.
In this case-- scheduledsoundplayer AU. Not sure if that's a
"generator"?
So, this should work *depending* on what you want to do:
scheduledsoundplayer1 -> autimepitch1 -> mixer -> defaultoutput
scheduledsoundplayer2 -> autimepitch2 ->
If however, you are using the two AUTP to adjust a notion of tempo
as well, then the above scenario (2 AUTP, 1 MusicPlayer) won't work -
We tried this -- definitely doesn't work. Changing the rate on either
one with stop playing the other one. Our MusicPlayer has a "tempo" of
60bpm, we just schedule stretch and volume changes in seconds. We
don't change the MusicPlayer tempo ever.
We've been letting the MusicPlayer stay at its preset tempo, but
during scheduling we schedule at the "new time" that the AUTPs create
instead of original time. This all seems to work.
I did not know about the AUSubGraph mechanism, that's good. So
assuming the above didn't work, something like this would?
graph0 / musicplayer0
ssp0->autp0->
graph1 / musicplayer1
ssp1->autp1->
graph2 / musicplayer2
graph0->mixer->defaultoutput
graph1->
And then I would schedule stretches with musicplayer0&1 and xfades &
volume with musicplayer2.
_______________________________________________
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