From: Oliver Freyd <Oliver.Freyd@gmx.de>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: trident (Hoontech 4d Wave NX) dropouts with small buffersize.
Date: Fri, 8 Oct 2004 09:15:06 +0200 [thread overview]
Message-ID: <20041008071505.GA3394@gmx.de> (raw)
In-Reply-To: <s5hacuyu1b1.wl@alsa2.suse.de>
Hello Takashi,
thanks for your reply!
On Thu, Oct 07, 2004 at 03:04:34PM +0200, Takashi Iwai wrote:
> No idea yet, but could you check whether this happens with ALSA native
> apps? For example, you can run aplay with --buffer-size and
> --period-size options. Pass above values to these options and see
> whether the playback works.
>
Yes, I've tried that now, if play some sound with aplay, without
--buffer-size, it works normal. If I use --period-size 512 and
buffer-size 1024, I get that broken sound. Also with period-size 1024 and
buffer-size 2048, I think. Only if I use a buffer-size > 2* period-size
if works ok.
>
> > I'm running debian testing,
> > alsa-source-1.0.5a-3
>
> It's old :)
>
This weekend I'll try to compile the newest alsa-sources :-)
Thanks for your help,
Oliver
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
next prev parent reply other threads:[~2004-10-08 7:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-05 20:13 trident (Hoontech 4d Wave NX) dropouts with small buffersize Oliver Freyd
2004-10-07 13:04 ` Takashi Iwai
2004-10-08 7:15 ` Oliver Freyd [this message]
2004-10-08 16:39 ` Takashi Iwai
2004-10-09 18:41 ` Oliver Freyd
2004-10-11 15:27 ` Takashi Iwai
2004-10-13 20:02 ` Oliver Freyd
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=20041008071505.GA3394@gmx.de \
--to=oliver.freyd@gmx.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=tiwai@suse.de \
/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.