All of lore.kernel.org
 help / color / mirror / Atom feed
From: Colin Guthrie <gmane@colin.guthr.ie>
To: pulseaudio-discuss@mail.0pointer.de
Cc: alsa-devel@alsa-project.org
Subject: Re: alsa pulse bugs
Date: Wed, 07 May 2008 02:45:57 +0100	[thread overview]
Message-ID: <fvr1kl$m4$1@ger.gmane.org> (raw)
In-Reply-To: <20080506193616.GB25436@tango.0pointer.de>

Cross posting Lennart's reply to the Alsa list as requested.

Please can you guys apply #3942 and #3944 (see below), as per Lennart's 
recommendations?

Cheers :)

Col

Lennart Poettering wrote:
> On Mon, 05.05.08 10:34, tom@dbservice.com (tom@dbservice.com) wrote:
> 
>> I reported three bugs to the alsa bugtracker:
>>
>> https://bugtrack.alsa-project.org/alsa-bug/view.php?id=3942
> 
> I though I already posted a patch like this a while back. This really
> should be merged!
> 
>> https://bugtrack.alsa-project.org/alsa-bug/view.php?id=3943
> 
> This is not correct. snd_pcm_delay() is the delay that it takes until
> a sample you write now to the PCM stream takes to be played. For PCI
> devices this is usually the same as write_index-read_index, but not
> for virtual devices like PA, and not even for USB.
> 
> This is the only way snd_pcm_delay() has any value for synchronization
> purposes (i.e. syncing video to audio).
> 
> I think there's simply in invalid assumption made by the WINE devs (or
> possible even the MS devs who designed the API): they assume that all
> sound cards are PCI sound cards. Which ain't really true.
> 
> In short: the transport latency *needs* to be taken into account,
> there is no way around this.
> 
>> https://bugtrack.alsa-project.org/alsa-bug/view.php?id=3944
> 
> This looks good to me and should also be applied.
> 
> Could you please post the patch for 3942 and 3944 to the ALSA ml? The
> truth is that the ALSA devs are very good at ignoring the ALSA BTS. If
> you want your stuff merged, post it to the ALSA ML, don't bother with
> the BTS.
> 
> And thank you very much for your patches!
> 
> Lennart
> 

      parent reply	other threads:[~2008-05-07  1:45 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   ` [pulseaudio-discuss] " Lennart Poettering
     [not found] ` <20080506193616.GB25436@tango.0pointer.de>
2008-05-07  1:45   ` Colin Guthrie [this message]

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='fvr1kl$m4$1@ger.gmane.org' \
    --to=gmane@colin.guthr.ie \
    --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.