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.
Cheers James > -----Original Message----- > 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(). 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.c and various other places where > this codepath leads, but I was quickly lost. I am not sure how this is > all supposed to work and there's not a lot of helpful comments :) > > _snd_pcm_hw_param_set() is returning -22 which I assume is -EINVAL. > This seems to be coming from the alsa-kernel code and that's about where > I got lost. > > Is there not a function to get the optimal periods/periodsize? Maybe > setting up the hw_params explicitly (except for rate and channels) is a > bad way to go about things? > > jack. > > _______________________________________________ > Alsa-devel mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/alsa-devel _______________________________________________ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
