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: Thu, 30 Jan 2003 10:35:40 +0100 [thread overview]
Message-ID: <s5hptqfkmj7.wl@alsa2.suse.de> (raw)
In-Reply-To: <20030130001100.60428.qmail@web40603.mail.yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 616 bytes --]
At Thu, 30 Jan 2003 00:11:00 +0000 (GMT),
Chris Rankin wrote:
>
> Hi,
>
> I have just installed the latest ALSA-CVS and I have
> noticed a few oddities:
>
> First, these modules are suddenly being compiled. I
> don't know why:
>
> snd-emu8000-synth.o
> snd-gus-synth.o
> snd-trident-synth.o
because of the last changes of Makefiles...
will be fixed soon.
> More importantly, playing WAV files via my SB Live!
> using aplay is making a nasty, loud "click" sound
> right at the end. It didn't used to do this. Any idea
> which change is causing it, please?
does the attached patch have any influence?
Takashi
[-- Attachment #2: sgbuf-clear.dif --]
[-- Type: application/octet-stream, Size: 435 bytes --]
Index: alsa-driver/acore/pcm_sgbuf.c
===================================================================
RCS file: /suse/tiwai/cvs/alsa/alsa-driver/acore/pcm_sgbuf.c,v
retrieving revision 1.7
diff -u -r1.7 pcm_sgbuf.c
--- alsa-driver/acore/pcm_sgbuf.c 27 Jan 2003 11:05:04 -0000 1.7
+++ alsa-driver/acore/pcm_sgbuf.c 30 Jan 2003 09:34:10 -0000
@@ -146,6 +146,7 @@
#endif
}
+ memset(vmaddr, 0, size);
return vmaddr;
_failed:
next prev parent reply other threads:[~2003-01-30 9:35 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 [this message]
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
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=s5hptqfkmj7.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox