On Fri, 14 Nov 2003, Chris Cheney wrote:
> Jaroslav,
>
> Debian just updated alsa to 0.9.8 recently and so I ran my test
> application against it again. I am still showing that alsa-lib has
> issues when being used with dmix (cmi 8738 hardware) in particular
> when calling snd_pcm_hw_params_set_periods (it fails) when calling
> snd_pcm_hw_params_set_periods_near I get the following information:
>
> periods wanted: 2
> periods dir: 1
> periods got: 2
>
> I told it to set it to periods = 2, it set it to periods = 2, but it
> then said it had set it to an amount of periods greater than what I
> requested (dir = 1), which also indicates when the regular
> snd_pcm_hw_params_set_periods would fail, since alsa-lib thinks it
> couldn't set it to what I requested.
>
> There are more problems using dmix than just this one function such as
> snd_pcm_hw_params_set_buffer_size failing as well.
It's indented to fix broken applications like yours and make them
really ALSA compatible ;-) All ALSA applications must accept also values
which are suggested otherwise it might fail with some hardware. Don't try
to be clever as alsa-lib or the lowlevel driver. You'll fail somewhere.
The dmix works with preset settings in which periods * period_size !=
buffer_size. See _snd_pcm_dmix_open() function (default parameters) for
more details about default values.
Jaroslav
-----
Jaroslav Kysela <[EMAIL PROTECTED]>
Linux Kernel Sound Maintainer
ALSA Project, SuSE Labs
-------------------------------------------------------
This SF. Net email is sponsored by: GoToMyPC
GoToMyPC is the fast, easy and secure way to access your computer from
any Web browser or wireless device. Click here to Try it Free!
https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/g22lp.tmpl
_______________________________________________
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
