Hi,

i guess it's a bug of either alsa-lib or aplay, not of the driver.
could you check at which user function the operation stops?

I'll be happy to provide any debugging info I can, but I'm not exactly sure what you mean by which user function. The error occurs for both user functions aplay and arecord, or do you mean something else?


This is how far aplay gets:

josh@spleen:/var/tmp$ aplay track_01.wav
Playing WAVE 'track_01.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo


but no sound, just 100% cpu load.


josh@spleen:/var/tmp$ arecord -f cd -d 120 /tmp/blah.wav
Recording WAVE '/tmp/blah.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo


here arecord does write a header:


RIFF$^@^@^@WAVEfmt^P^@^@^@^A^@^B^@D<AC>^@^@^P<B1>^B^@^D^@^P^@data^@^@^@^@


but then jumps to 100% cpu load and doesn't get any further.


-josh



-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel

Reply via email to