From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0001081]: Clicking noise when short sound files are played.
Date: Fri, 30 Dec 2005 04:01:50 +0100 [thread overview]
Message-ID: <6834cfdabad65476bbcc50a7faebfedf@bugtrack.alsa-project.org> (raw)
The following issue has been CLOSED
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1081>
======================================================================
Reported By: raid517
Assigned To:
======================================================================
Project: ALSA - driver
Issue ID: 1081
Category: CORE - control
Reproducibility: always
Severity: major
Priority: normal
Status: closed
Distribution: Debian
Kernel Version: 2.6.11.7
Resolution: open
Fixed in Version:
======================================================================
Date Submitted: 04-29-2005 07:39 CEST
Last Modified: 12-30-2005 04:01 CET
======================================================================
Summary: Clicking noise when short sound files are played.
Description:
Hi whenever I play .wav files (or any very short sound files) from sites
such as the following, the sound plays fine, but it is always followed by
a slight 'clicking' noise at the exact instant when the sound stops
playing. What causes this - and how do I prevent it?
(Just an example).
http://www.wavsite.com/
GJ
======================================================================
Relationships ID Summary
----------------------------------------------------------------------
related to 0000850 Clicking sound at the end of short audi...
======================================================================
----------------------------------------------------------------------
jdthood - 09-22-05 15:16
----------------------------------------------------------------------
Do you still have this problem?
What sound hardware do you have?
----------------------------------------------------------------------
rlrevell - 12-30-05 04:01
----------------------------------------------------------------------
No response
Issue History
Date Modified Username Field Change
======================================================================
04-29-05 07:39 raid517 New Issue
04-29-05 07:39 raid517 Distribution => Debian
04-29-05 07:39 raid517 Kernel Version => 2.6.11.7
09-22-05 15:16 jdthood Note Added: 0006346
09-22-05 15:17 jdthood Relationship added related to 0000850
09-29-05 10:15 Lucid Issue Monitored: Lucid
12-30-05 04:01 rlrevell Status new => closed
12-30-05 04:01 rlrevell Note Added: 0007197
======================================================================
-------------------------------------------------------
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-30 3:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-30 3:01 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-09-22 13:17 [ALSA - driver 0001081]: Clicking noise when short sound files are played bugtrack
2005-09-22 13:16 bugtrack
2005-04-29 5:39 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=6834cfdabad65476bbcc50a7faebfedf@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