> When I see -22 returned, it normally means wrongly installed drivers.
> Most users who report -22 errors, find the solution is a re-install of alsa
> fixes it.
> This is what I have found from users of xine (http://xine.sf.net) which has
> alsa support.
I'm fairly sure they're installed correct
; From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Jack Moffitt
> Sent: 19 December 2001 07:44
> To: [EMAIL PROTECTED]
> Subject: Re: [Alsa-devel] set_period_size gives error: Invalid argument
>
>
> > You may try to use snd_pcm_hw_set_period_size_near(). Ther
> It seems that there is some code unfinished in the pmac driver
> which is describing hardware constraints. Takashi, could you help us?
But using snd-pcm-oss everything works fine. So I have to think that
odd sample rates work somehow.
jack.
___
Als
On Wed, 19 Dec 2001, Jack Moffitt wrote:
> > You may try to use snd_pcm_hw_set_period_size_near(). There might be some
> > hardware constraints which do not allow to use any integer period size.
> > If you feel it's a bug, let me know.
>
> Same error with that as well. I think this is a bug. I
> You may try to use snd_pcm_hw_set_period_size_near(). There might be some
> hardware constraints which do not allow to use any integer period size.
> If you feel it's a bug, let me know.
Same error with that as well. I think this is a bug. I tried tracing
through the code in src/pcm/pcm_param
On Tue, 18 Dec 2001, Jack Moffitt wrote:
> I noticed today while testing ogg123 that certain streams were failing
> with this message:
>
> ALSA snd_pcm_hw_params_set_period_size error: Invalid argument
>
> I've tried every period size from 0 to 10240 basically, and none of
> them are accepted.
>
