From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - utils 0001304]: Speaker test hangs
Date: Wed, 3 Aug 2005 02:46:42 +0200 [thread overview]
Message-ID: <e0146cf2250bbc3f73279edf41a9f2e0@bugtrack.alsa-project.org> (raw)
The following issue has been SUBMITTED.
======================================================================
<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: 08-03-2005 02:46 CEST
======================================================================
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.
======================================================================
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
======================================================================
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
next reply other threads:[~2005-08-03 0:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-03 0:46 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-08-03 10:18 [ALSA - utils 0001304]: Speaker test hangs bugtrack
2005-08-04 1:21 bugtrack
2005-08-04 12:10 bugtrack
2005-08-04 18:21 bugtrack
2005-08-09 4:58 bugtrack
2005-08-12 6:12 bugtrack
2005-08-12 13:47 bugtrack
2005-12-30 22:24 bugtrack
2005-12-31 20:38 bugtrack
2005-12-31 21:07 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=e0146cf2250bbc3f73279edf41a9f2e0@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