From: Takashi Iwai Subject: Re: What does snd_pcm_delay() actually return? Date: Fri, 13 Jun 2008 08:22:39 +0200 Message-ID: References: <20080609190225.GA4534@tango.0pointer.de> <20080612210005.GC20818@tango.0pointer.de> Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mx1.suse.de (cantor.suse.de [195.135.220.2]) by alsa0.perex.cz (Postfix) with ESMTP id DB4AA243FE for ; Fri, 13 Jun 2008 08:22:39 +0200 (CEST) In-Reply-To: <20080612210005.GC20818@tango.0pointer.de> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: alsa-devel-bounces@alsa-project.org Errors-To: alsa-devel-bounces@alsa-project.org To: Lennart Poettering Cc: alsa-devel@alsa-project.org List-Id: alsa-devel@alsa-project.org At Thu, 12 Jun 2008 23:00:06 +0200, Lennart Poettering wrote: > > On Thu, 12.06.08 14:08, Takashi Iwai (tiwai@suse.de) wrote: > > > AFAIK, the problem here is that the handling of hwptr isn't > > inconsistent in the pulse plugin. The definition of hwptr is the > > point being played (or at least, the point where it was already > > processed). So, it's fine that you take the network latency into > > account for calculation of hwptr like the pulse delay callback > > actually does. > > > > But, then, pointer callback also must contain the same latency. If > > the hwptr with network latency doesn't work well, then delay callback > > shouldn't have the latency as well. > > But we need the network latency in there, because it is necessary for > doing a/v synchronization. The network latency can be quite > substantial. That's why I suggest to fix hwptr to consider the network latency in the first place. > The "hw_ptr/appl_ptr" is just too simple to cover the networked > cases. Likely. The hwptr/applptr model was designed for PCI-DMA h/w, and doesn't suit with the queue style implementation, indeed. IOW, it's optimized for mmap-style access. Takashi