From: The Source <thesourcehim@gmail.com>
To: Sam Lantinga <slouken@libsdl.org>
Cc: alsa-devel@alsa-project.org
Subject: Re: Long-standing SDL ALSA bug
Date: Tue, 13 Oct 2009 07:36:31 +0400 [thread overview]
Message-ID: <4AD3F5BF.4070006@gmail.com> (raw)
In-Reply-To: <3adffa60910121114p54e74010r541c6cee86db6721@mail.gmail.com>
12.10.2009 22:14, Sam Lantinga ?????:
> Hey guys, we're in the process of getting ready to release SDL 1.2.14,
> and we're trying to fix a long standing issue with crackling and pops
> in ALSA with some configurations:
> http://bugzilla.libsdl.org/show_bug.cgi?id=650
>
> What's really puzzling is that we're not able to reproduce it ourselves at all.
>
> I'm attaching the latest versions of the SDL audio files, and I'd
> really appreciate it if you take a look and sanity check our code.
> You can get the full pre-release here:
> http://www.libsdl.org/tmp/SDL-1.2.zip
>
> Thanks!
>
>
>
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>
I may be wrong but I have a feeling that the problem is in the
pulseaudio actually not in alsa.
There's a thing called alsa-plugins-pulseaudio which creates virtual
alsa device. This device sends all sound output to pulseaudio.
Many modern distributions like to use this device as default. And
pulseaudio still has some crackling issues, yes.
next prev parent reply other threads:[~2009-10-13 3:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-12 18:14 Long-standing SDL ALSA bug Sam Lantinga
2009-10-13 3:36 ` The Source [this message]
2009-10-13 5:52 ` Peter Lawler
2009-10-13 7:03 ` Clemens Ladisch
2009-10-13 10:05 ` Sam Lantinga
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=4AD3F5BF.4070006@gmail.com \
--to=thesourcehim@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=slouken@libsdl.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 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.