All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josh Buhl <uzs33d@uni-bonn.de>
To: alsa-devel@lists.sourceforge.net
Subject: Re: aplay/arecord hang at 44100 Hz
Date: Tue, 11 Feb 2003 17:47:26 +0100	[thread overview]
Message-ID: <3E49291E.7000307@uni-bonn.de> (raw)
In-Reply-To: <s5hu1fbcfyb.wl@alsa2.suse.de>

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

  reply	other threads:[~2003-02-11 16:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-10  9:16 aplay/arecord hang at 44100 Hz Josh Buhl
2003-02-11  9:41 ` Takashi Iwai
2003-02-11 16:47   ` Josh Buhl [this message]
2003-02-11 17:03     ` Takashi Iwai
2003-02-12  9:01       ` Josh Buhl
2003-02-12  9:29       ` Josh Buhl
2003-02-12 11:48         ` Takashi Iwai
2003-02-12 12:18           ` Josh Buhl
2003-02-12 12:20             ` Takashi Iwai

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3E49291E.7000307@uni-bonn.de \
    --to=uzs33d@uni-bonn.de \
    --cc=alsa-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.