From: Lennart Poettering <mznyfn@0pointer.de>
To: General PulseAudio Discussion <pulseaudio-discuss@mail.0pointer.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: [pulseaudio-discuss] alsa pulse bugs
Date: Tue, 6 May 2008 21:38:24 +0200 [thread overview]
Message-ID: <20080506193824.GC25436@tango.0pointer.de> (raw)
In-Reply-To: <fvmi82$f7a$1@ger.gmane.org>
On Mon, 05.05.08 09:58, Colin Guthrie (gmane@colin.guthr.ie) wrote:
>
> tom@dbservice.com wrote:
> > I reported three bugs to the alsa bugtracker:
> >
> > https://bugtrack.alsa-project.org/alsa-bug/view.php?id=3942
> > https://bugtrack.alsa-project.org/alsa-bug/view.php?id=3943
> > https://bugtrack.alsa-project.org/alsa-bug/view.php?id=3944
> >
> > It's three bugs after all. Once these are fixed I expect Wine to work.
> > *fingers crossed*
>
> Ace Tom :)
>
> I've cross posted this to the alsa devel list. Hopefully Takashi (who's
> committed some pulse-related stuff recently) will have some insight here.
>
> Re the snd_pcm_delay() including network latency (#3945), this clearly
> makes sense for network streams. Does you proposed fix include this
> delay (albeit with the improvement that it also will drop to 0 if there
> are no samples queued)?
>
> Also re #3942, I believe (but not sure) that the max buffer in the
> glitch free branch has been increased significantly (as it now needs to
> keep some degree of past sound as well as future buffer to allow the
> rewinds to work properly (this is no doubt an inaccurate description of
> why it's needed.... :p)) I'm not sure how this would affect this
> solution, but Lennart will be able to advise better.
Yes, with glitch-free maxlength becomes mostly irrelevant. It should
default to "0" know, to let the server decide.
Lennart
--
Lennart Poettering Red Hat, Inc.
lennart [at] poettering [dot] net ICQ# 11060553
http://0pointer.net/lennart/ GnuPG 0x1A015CC4
next prev parent reply other threads:[~2008-05-06 19:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080505103410.zv8dezd9z44cksoc@dbservice.com>
2008-05-05 8:58 ` alsa pulse bugs Colin Guthrie
2008-05-05 9:11 ` tom
2008-05-05 9:18 ` Colin Guthrie
2008-05-05 9:37 ` tom
2008-05-05 9:44 ` Colin Guthrie
2008-05-05 10:22 ` tom
2008-05-05 10:31 ` Colin Guthrie
2008-05-06 19:38 ` Lennart Poettering [this message]
[not found] ` <20080506193616.GB25436@tango.0pointer.de>
2008-05-07 1:45 ` Colin Guthrie
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=20080506193824.GC25436@tango.0pointer.de \
--to=mznyfn@0pointer.de \
--cc=alsa-devel@alsa-project.org \
--cc=pulseaudio-discuss@mail.0pointer.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.