Skip to contentSkip to conversation

snd_pcm_status_get_tstamp()

DISCUSSION Lennart Poettering 3 participants 5 messages Dec 31, 2007 – Jan 7, 2008

lore
Share & tools
lore
#0 lore raw

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?

Lennart

Signature · 3 lines
Lennart Poettering                        Red Hat, Inc.
lennart [at] poettering [dot] net         ICQ# 11060553
http://0pointer.net/lennart/           GnuPG 0x1A015CC4
#1 lore raw

At Mon, 31 Dec 2007 17:53:40 +0100,

Quoted 9 lines · Lennart Poettering

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

#2 lore raw
Quoted 7 lines · Takashi Iwai
Quoted 6 lines

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?

Quoted 5 lines

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().

So I figure this is always CLOCK_REALTIME?

I am currently using CLOCK_MONOTONIC for most timekeeping in PulseAudio. Would it be possible to add an API to ALSA to allow getting those timestamps in CLOCK_MONOTONIC instead of CLOCK_REALTIME?

Maybe by adding two new time stamp modes, changeble via snd_pcm_sw_params_set_tstamp_mode()?

Also, may I suggest to add the explanation you wrote above to the doxygen docs?

Thanks,

Lennart

Signature · 3 lines
Lennart Poettering                        Red Hat, Inc.
lennart [at] poettering [dot] net         ICQ# 11060553
http://0pointer.net/lennart/           GnuPG 0x1A015CC4
#3 lore raw

At Mon, 7 Jan 2008 16:21:55 +0100,

Quoted 16 lines · Lennart Poettering
Quoted 7 lines · Takashi Iwai
Quoted 6 lines

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?

Quoted 5 lines

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().

Quoted 5 lines

So I figure this is always CLOCK_REALTIME?

I am currently using CLOCK_MONOTONIC for most timekeeping in PulseAudio. Would it be possible to add an API to ALSA to allow getting those timestamps in CLOCK_MONOTONIC instead of CLOCK_REALTIME?

CLOCK_MONOTONIC is already available in the newer version of ALSA-driver. But, the corresponding alsa-lib API isn't implemented yet.

Quoted 5 lines

Maybe by adding two new time stamp modes, changeble via snd_pcm_sw_params_set_tstamp_mode()?

Also, may I suggest to add the explanation you wrote above to the doxygen docs?

A patch is welcome :) That's not the part I've implemented, too.

Takashi

#4 lore raw
Quoted 20 lines · Takashi Iwai

At Mon, 7 Jan 2008 16:21:55 +0100,

Quoted 18 lines · Lennart Poettering
Quoted 7 lines · Takashi Iwai
Quoted 6 lines

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?

Quoted 5 lines

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().

So I figure this is always CLOCK_REALTIME?

Quoted 7 lines
Quoted 3 lines

I am currently using CLOCK_MONOTONIC for most timekeeping in PulseAudio. Would it be possible to add an API to ALSA to allow getting those timestamps in CLOCK_MONOTONIC instead of CLOCK_REALTIME?

CLOCK_MONOTONIC is already available in the newer version of ALSA-driver. But, the corresponding alsa-lib API isn't implemented yet.

Right. I will do this.

Jaroslav

-----
Jaroslav Kysela <[email protected]>
Linux Kernel Sound Maintainer
ALSA Project, Red Hat, Inc.