I want to try and aim at 8 periods per buffer.
Common sense would tell me that one should be able to set the buffer size first, and then try to set the period size to buffer_size/8. But I
why don't you set the sizes based on frame counts, not time? i suspect you're more likely to get better results.
If the api for setting based on time it present, I would expect to be able to use it.
should be able to use the set_period_size_near call so that it selects the next closest value, so that I achieve a result as close as possible to what I want. This seems to fail with the current setup on some sound cards, but works with other sound cards.
i hope you handle the failure to get buffer_size/8 properly ... you need to be willing to go all the way to buffer_size/2 before concluding that you can't configure the device.
I would expect to be able to use the "set_period_size_near" with direction +1, so if period_size=buffer_size/8 did not work, the alsa-lib would automatically select the next best one, even if it is buffer_size/2, but this seems to fail as well.
--p
Cheers James
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
