Re: Getting available sample rate
Re: Getting available sample rate
- Subject: Re: Getting available sample rate
- From: Stéphane Letz <email@hidden>
- Date: Fri, 12 Dec 2008 15:18:37 +0100
}
But it appears that will some devices like Echo Gina, this code only
sees 6 possible values (8000, 11025, 16000, 22050, 32000, 64000)
where 10 are available (8000, 11025, 16000, 22050, 32000, 44100,
48000, 64000, 88200, 96000) as seen by Audio Midi Setup for example.
Could it be:
1) that we always use the AudioDeviceGetProperty call using the
"isInput" parameter to false, event for input only device?
It's possible that could make a difference I suppose, but I don't
think that it would in this case. You could fix the ambiguity by using
AudioObjectGetPropertyData() and using the global scope to fetch the
available sample rates.
2) that we read the mMinimum field of AudioValueRange? (where 2
fields mMinimum and mMaximum are available ?
This seems possible. A device can mix and match ranges with one value
and ranges that cover many values. I believe that AMS filters the list
to only display the common rates.
3) any other reason?
It's always possible that you've hit a bug in the HAL. But since it
seems to do the right thing in AMS, it seems more likely that there is
something else going on here.
-
It appears that some devices declare a range like 5000, 50000 Hz. In
this case I guess that the application should only display and let the
user choose "sensible" values inside the whole range yes?
Is this what is done by AMS ? (that is have a known array of possible
values and display the one that are part of the possible range?)
Thanks
Stephane Letz
_______________________________________________
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