From: Lee Revell <rlrevell@joe-job.com>
To: Chris Rankin <rankincj@yahoo.com>
Cc: alsa-devel@lists.sourceforge.net, a.villacis@palosanto.com
Subject: Re: ALSA and Wine DirectSound question: Fwd from wine-patches list
Date: Wed, 10 Aug 2005 15:08:45 -0400 [thread overview]
Message-ID: <1123700926.24369.18.camel@mindpipe> (raw)
In-Reply-To: <20050810121434.96950.qmail@web52911.mail.yahoo.com>
On Wed, 2005-08-10 at 13:14 +0100, Chris Rankin wrote:
> I think the Wine developers are seeking enlightenment from an ALSA Guru. (The "World of Warcraft"
> people seem keen to get this patch working, too ;-).) Can anyone help, please?
>
> http://www.winehq.org/hypermail/wine-patches/2005/08/0173.html
This sounds a lot like my theory about what is causing the infamous
crackling problem that has been reported with JACK - the ALSA middle
layer is consistently returning an incorrect hardware pointer which
causes a few samples from the other buffer (assuming a double buffering
scheme) to be overwritten.
Lee
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
next prev parent reply other threads:[~2005-08-10 19:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-10 12:14 ALSA and Wine DirectSound question: Fwd from wine-patches list Chris Rankin
2005-08-10 19:08 ` Lee Revell [this message]
2005-08-11 13:12 ` Takashi Iwai
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=1123700926.24369.18.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=a.villacis@palosanto.com \
--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.