From: Takashi Iwai Subject: Re: snd_pcm_status_get_tstamp() Date: Mon, 07 Jan 2008 12:10:39 +0100 Message-ID: References: <20071231165340.GA17734@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 (mail.suse.de [195.135.220.2]) by alsa0.perex.cz (Postfix) with ESMTP id 939302488D for ; Mon, 7 Jan 2008 12:10:39 +0100 (CET) In-Reply-To: <20071231165340.GA17734@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 Development Mailing List List-Id: alsa-devel@alsa-project.org At Mon, 31 Dec 2007 17:53:40 +0100, Lennart Poettering wrote: > > Hi! > > The documentation for snd_pcm_status_get_tstamp() is not really > enlightening. After a call to snd_pcm_status() what data does the > tstamp field actually carry? Some kind of system clock timestamp when > the data in the status struct was valid, or some kind of sound card > clock timestamp that is relative to the point in time where the device > was opened/started? In the normal mode, it's the timestamp at the moment snd_pcm_status() is processed. OTOH, the trigger_tstamp is the time that the trigger callback was called (e.g. the stream starts / stops). The time is the system-wide time, equivalent with the normal gettimeofday(). Takashi