From mboxrd@z Thu Jan 1 00:00:00 1970 From: Clemens Ladisch Subject: Re: Timing Info Date: Sun, 13 Jun 2010 16:10:19 +0200 Message-ID: <4C14E6CB.2030909@ladisch.de> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by alsa0.perex.cz (Postfix) with ESMTP id A520E244C7 for ; Sun, 13 Jun 2010 16:10:23 +0200 (CEST) In-Reply-To: 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: Paul Dugas Cc: alsa-devel@alsa-project.org List-Id: alsa-devel@alsa-project.org Paul Dugas wrote: > Looks like some processing of the trigger timestamp is what I need Trigger events are starting or stopping of a stream. > What's the "timestamp mode". Does it generate a timestamp each > period? How would I access that timestamp? Set SND_PCM_TSTAMP_ENABLE to generate a timestamp whenever the hardware position is updated. Call snd_pcm_status to read the position and the corresponding timestamp. HTH Clemens