From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0000648]: aplay -Dspdif produces choppy (beating?) audio from DTS .wav files
Date: Thu, 18 Nov 2004 17:37:32 +0100 [thread overview]
Message-ID: <b671d28ac340b9d178581c7e5e3d39a6@bugtrack.alsa-project.org> (raw)
The following issue has been RESOLVED.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=648>
======================================================================
Reported By: duanev
Assigned To: pzad
======================================================================
Project: ALSA - driver
Issue ID: 648
Category: PCI - emu10k1
Reproducibility: always
Severity: major
Priority: normal
Status: resolved
Distribution: Mandrake 10.1
Kernel Version: Preemptable 2.6.8 kernel
Resolution: fixed
Fixed in Version:
======================================================================
Date Submitted: 11-14-2004 04:24 CET
Last Modified: 11-18-2004 17:37 CET
======================================================================
Summary: aplay -Dspdif produces choppy (beating?) audio from
DTS .wav files
Description:
Sound produced by aplay is not smooth - audio is "chopped up" or appears to
"beat" at about 5Hz.
======================================================================
----------------------------------------------------------------------
rlrevell - 11-17-04 18:21
----------------------------------------------------------------------
Hmm good question. Takashi-san. can we close this, marking it as a
duplicate of bug 646?
----------------------------------------------------------------------
tiwai - 11-18-04 17:37
----------------------------------------------------------------------
Closed now.
Issue History
Date Modified Username Field Change
======================================================================
11-14-04 04:24 duanev New Issue
11-14-04 04:24 duanev Distribution => Mandrake 10.1
11-14-04 04:24 duanev Kernel Version => Preemptable 2.6.8
kernel
11-14-04 04:41 rlrevell Note Added: 0002406
11-14-04 10:02 pzad Note Added: 0002407
11-17-04 07:02 duanev Note Added: 0002433
11-17-04 18:21 rlrevell Note Added: 0002437
11-18-04 17:37 tiwai Status assigned => resolved
11-18-04 17:37 tiwai Resolution open => fixed
11-18-04 17:37 tiwai Note Added: 0002449
======================================================================
-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
next reply other threads:[~2004-11-18 16:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-18 16:37 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-12-20 13:42 [ALSA - driver 0000648]: aplay -Dspdif produces choppy (beating?) audio from DTS .wav files bugtrack
2004-11-17 17:21 bugtrack
2004-11-17 6:02 bugtrack
2004-11-14 9:02 bugtrack
2004-11-14 3:41 bugtrack
2004-11-14 3:24 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=b671d28ac340b9d178581c7e5e3d39a6@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