Re: should the mBox change my understanding of the CoreAudio API?
Re: should the mBox change my understanding of the CoreAudio API?
- Subject: Re: should the mBox change my understanding of the CoreAudio API?
- From: James McCartney <email@hidden>
- Date: Tue, 2 Sep 2003 16:45:01 -0700
Hi Chris,
The Hammerfall box presents an array of mono streams. That is also what
you are seeing below. For these devices you need to put your data,
noninterleaved, into the buffer list.
On Sep 2, 2003, at 4:05 PM, Christopher Penrose wrote:
After this failure with the mBox, I decided to use a program that I
had coded to poll audio devices to discern a problem. It is my
understanding that a CoreAudio hardware device is configured with a
particular audiostream whose nature can be revealed with the audio
device's associated AudioStreamBasicDescription. Is this correct?
Well, when I poll the mbox, the currently selected hardware, with the
following code:
/* Get the basic device description */
propertySize = sizeof(outputStreamBasicDescription);
status = AudioDeviceGetProperty(outputDeviceID, 0, 0,
kAudioDevicePropertyStreamFormat,
&propertySize,&outputStreamBasicDescription);
and print out the description, the value of mChannelsPerFrame I
receive seems incorrect. My program reveals "1", while mBytesPerFrame
seems correct with a value of "4". Is the digidesign driver bugged
or is my understanding incorrect here? Should I give up until
digidesign fixes the hypothetical bug or do I have something to learn
about polling the description of the currently configured stream?
---
James McCartney
Apple CoreAudio
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.