mplayer complains about:
"alsa-init: unable to set periodsize: Invalid argument."
It may happen that some applications want to set a periodsize that is not
supported by the HW.
Try start something that is known to work like aplay:
$ aplay .wav
The alsaplay should also work, but you must speci
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi
First I'd just like to state that I'm very happy with the way alsa works for
me, good work.
However I'm experiencing problems on a HP Brio BA400 equipped with CS
soundchip. I cannot for sure tell you exactly what version of the chip this
is, since
I have seen several people with this problem, and even seen a few people
who claim they've gotten it working, but I have had absolutely no luck
getting all four channels (and maybe center/LFE?) to play
simultaneously. I'm using alsa 0.9.6 right now, as well as the
xmms-alsa plugin. The card is a
On Wed, 20 Feb 2002, Markus Braun wrote:
> >I posted a fix for this to the alsa-devel list a couple of months
> > ago, but it doesn't seem to have made it to the ALSA source yet. The
> > problem appeared on my Santa Cruz sound card, but it sounds like the
> > same problem.
> >
> >This is
>I posted a fix for this to the alsa-devel list a couple of months
> ago, but it doesn't seem to have made it to the ALSA source yet. The
> problem appeared on my Santa Cruz sound card, but it sounds like the
> same problem.
>
>This is what I wrote:
>
> > After much peering around, tra
Markus Braun <[EMAIL PROTECTED]> writes:
> I have a IBM Thinkpad T21 with a Cirrus Logic CS 4614/22/24 audio
> controller. I have used alsa 0.5.12a and before thet the module from teh
> linux kernel. Both without any problems. Last weekend I switched to alsa
> 0.9.0beta10. Now I have the prob
Hi everybody!
I have a IBM Thinkpad T21 with a Cirrus Logic CS 4614/22/24 audio
controller. I have used alsa 0.5.12a and before thet the module from teh
linux kernel. Both without any problems. Last weekend I switched to alsa
0.9.0beta10. Now I have the problem, that I am only able to start alsa
