All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Chris Rankin <rankincj@yahoo.com>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: EMU10K1 - CVS: nasty "click" at end of WAV files, and spurious extra modules.
Date: Mon, 03 Feb 2003 11:51:44 +0100	[thread overview]
Message-ID: <s5h8ywxiqm7.wl@alsa2.suse.de> (raw)
In-Reply-To: <20030131195651.81705.qmail@web40605.mail.yahoo.com>

Hi Chris,

At Fri, 31 Jan 2003 19:56:51 +0000 (GMT),
Chris Rankin wrote:
> 
>  --- Takashi Iwai <tiwai@suse.de> wrote:
> > do you know which version (or date) the driver
> > worked without clicks?
> > there have been not many changes for emu10k1 or pcm
> > stuffs recently.
> 
> On a hunch, I downloaded the alsa-lib-0.9.0rc6 and
> alsa-util-0.9.0rc6 packages and tried those against
> the current CVS version of the kernel modules. There
> is no nasty clicking sound using 0.9.0rc6 userspace.
> 
> Even more interesting:
> 
> alsa-lib 0.9.0rc6 + alsa-utils CVS => CLICK!
> alsa-lib CVS + alsa-utils 0.9.0rc6 => No click.

wow, that's interesting.  thanks for tracking it down.

unfortuantely i cannot reproduce this problem with the combination of
alsa-lib CVS + alsa-utils CVS on my audigy.

is it possible that the behavior depends on the wav file to play?
if the file is not too big, could you send me the example wav file to
trigger this, so that i can test on my machine?


ciao,

Takashi


-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com

  reply	other threads:[~2003-02-03 10:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-30  0:11 EMU10K1 - CVS: nasty "click" at end of WAV files, and spurious extra modules Chris Rankin
2003-01-30  9:35 ` Takashi Iwai
2003-01-30 23:13   ` Chris Rankin
2003-01-31 11:03     ` Takashi Iwai
2003-01-31 19:56       ` Chris Rankin
2003-02-03 10:51         ` Takashi Iwai [this message]
2003-02-03 13:38           ` Chris Rankin
2003-02-05 11:25             ` Takashi Iwai
2003-02-05 23:05               ` Chris Rankin

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=s5h8ywxiqm7.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=rankincj@yahoo.com \
    /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.