A few more questions on QT-CA data transfers, and spontaneous AU uninitialization
A few more questions on QT-CA data transfers, and spontaneous AU uninitialization
- Subject: A few more questions on QT-CA data transfers, and spontaneous AU uninitialization
- From: Ray Garcia <email@hidden>
- Date: Mon, 17 Apr 2006 21:35:15 -0500
Back with a few more questions. Upon design discussion, it came up
that the ScheduledAUPlayer unfortunately can't be used since it's
10.4-specific (our minimum preferred compatibility is 10.3.9). So,
back to API discovery.
Is noninterleaved audio treated differently between CoreAudio and and
QuickTime? I get single buffers in the AudioBufferList from Quicktime
- presumably with the individual channels contiguous within the
buffer; while I'm getting an AudioBufferList with one channel per
buffer in the CoreAudio rendering callback? If this is in fact to be
expected, is there a way to control it or do I just rearrange my
buffer copy routines to deal with the inconsistency?
Under what conditions can an initialized AUGraph go to an
uninitialized state? I have a graph which declines to start
(reporting with kAudioUnitErr_Uninitialized) unless I start it
immediately after initialization.
Specifically, I'd like to create the AU graph at time of loading the
movie, and start and stop the graph with mouse-down mouse-up events
in order to conserve CPU. Mouse drag events trigger buffer fills;
filled buffers are passed as pointers through a nonblocking fifo. If
the render callback exhausts its buffer and nothing is in the fifo,
it just feeds silence. In other words, simple as I dare..
Thanks,
-RKG
_______________________________________________
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