From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - utils 0001304]: Speaker test hangs
Date: Sat, 31 Dec 2005 21:38:01 +0100 [thread overview]
Message-ID: <e0f7743494e758215869bb9ac739643b@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1304>
======================================================================
Reported By: herby
Assigned To:
======================================================================
Project: ALSA - utils
Issue ID: 1304
Category: speakertest
Reproducibility: always
Severity: major
Priority: normal
Status: new
======================================================================
Date Submitted: 08-03-2005 02:46 CEST
Last Modified: 12-31-2005 21:38 CET
======================================================================
Summary: Speaker test hangs
Description:
After applying the patch to the library that took out the check for a
proper "start_threshold" (file .../alsa-lib/src/pcm/pcm.c around lines 834
or so), I attempted to try a speaker test again. It hung right after
outputting "0 - Front Left". I did an strace and the results are included
in the file attached. I attempted to vary the sample rate (to 44.1 kHz)
with little luck. The wierd thing is that I can execute 'aplay' (with the
default device) and get a '.wav' file to play nicely. I can even get a
multi-channel (4 to be exact) ".wav" file to go thru 'aplay'. Why
speaker-test doesn't work is beyond me. The problem is that I appear to
use similar techniques in my own programming as speaker-test, and my
program doesen't do that well. Being as how speaker-test IS part of ALSA,
I thought I would submit the bug report against it.
If other tests need be preformed, I'd be VERY happy to do them.
======================================================================
----------------------------------------------------------------------
rlrevell - 12-30-05 23:24
----------------------------------------------------------------------
Any improvement in later releases?
----------------------------------------------------------------------
herby - 12-31-05 21:38
----------------------------------------------------------------------
I had no problems with later versions.
Issue History
Date Modified Username Field Change
======================================================================
08-03-05 02:46 herby New Issue
08-03-05 02:46 herby File Added: speaker-trace
08-03-05 12:18 tiwai Note Added: 0005621
08-04-05 03:21 herby Note Added: 0005638
08-04-05 14:10 jcdutton Note Added: 0005648
08-04-05 20:21 herby Note Added: 0005652
08-09-05 06:58 herby Note Added: 0005718
08-12-05 08:12 herby Note Added: 0005765
08-12-05 15:47 tiwai Note Added: 0005773
12-30-05 23:24 rlrevell Note Added: 0007288
12-31-05 21:38 herby Note Added: 0007360
======================================================================
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
next reply other threads:[~2005-12-31 20:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-31 20:38 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-12-31 21:07 [ALSA - utils 0001304]: Speaker test hangs bugtrack
2005-12-30 22:24 bugtrack
2005-08-12 13:47 bugtrack
2005-08-12 6:12 bugtrack
2005-08-09 4:58 bugtrack
2005-08-04 18:21 bugtrack
2005-08-04 12:10 bugtrack
2005-08-04 1:21 bugtrack
2005-08-03 10:18 bugtrack
2005-08-03 0:46 bugtrack
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=e0f7743494e758215869bb9ac739643b@bugtrack.alsa-project.org \
--to=bugtrack@alsa-project.org \
--cc=alsa-devel@alsa-project.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox