trigger timestamp
Hi all,
From the user space test application , Is it possible to get the
trigger timestamp corresponding to SNDRV_PCM_TRIGGER_START & SNDRV_PCM_TRIGGER_STOP events for audio playback capture?
On Thu, 01 Jul 2021 01:41:29 +0200, Muni Sekhar wrote:
Hi all,
From the user space test application , Is it possible to get the
trigger timestamp corresponding to SNDRV_PCM_TRIGGER_START & SNDRV_PCM_TRIGGER_STOP events for audio playback capture?
That's exactly what trigger_tstamp of snd_pcm_status corresponds for.
HTH,
Takashi
On Thu, Jul 8, 2021 at 4:59 PM Takashi Iwai tiwai@suse.de wrote:
On Thu, 01 Jul 2021 01:41:29 +0200, Muni Sekhar wrote:
Hi all,
From the user space test application , Is it possible to get the
trigger timestamp corresponding to SNDRV_PCM_TRIGGER_START & SNDRV_PCM_TRIGGER_STOP events for audio playback capture?
That's exactly what trigger_tstamp of snd_pcm_status corresponds for.
Does aplay and arecord have any command line options to get the trigger_tstamp? If not how to get it?
HTH,
Takashi
On Thu, 08 Jul 2021 14:19:12 +0200, Muni Sekhar wrote:
On Thu, Jul 8, 2021 at 4:59 PM Takashi Iwai tiwai@suse.de wrote:
On Thu, 01 Jul 2021 01:41:29 +0200, Muni Sekhar wrote:
Hi all,
From the user space test application , Is it possible to get the
trigger timestamp corresponding to SNDRV_PCM_TRIGGER_START & SNDRV_PCM_TRIGGER_STOP events for audio playback capture?
That's exactly what trigger_tstamp of snd_pcm_status corresponds for.
Does aplay and arecord have any command line options to get the trigger_tstamp? If not how to get it?
Implement some code :)
Alternatively you can check the proc output contents in /proc/asound/card*/pcm*/sub*/status. It'd be difficult to see the stop timestamp, though (as the application closes the stream immediately after that).
Takashi
On Thu, Jul 8, 2021 at 6:02 PM Takashi Iwai tiwai@suse.de wrote:
On Thu, 08 Jul 2021 14:19:12 +0200, Muni Sekhar wrote:
On Thu, Jul 8, 2021 at 4:59 PM Takashi Iwai tiwai@suse.de wrote:
On Thu, 01 Jul 2021 01:41:29 +0200, Muni Sekhar wrote:
Hi all,
From the user space test application , Is it possible to get the
trigger timestamp corresponding to SNDRV_PCM_TRIGGER_START & SNDRV_PCM_TRIGGER_STOP events for audio playback capture?
That's exactly what trigger_tstamp of snd_pcm_status corresponds for.
Does aplay and arecord have any command line options to get the trigger_tstamp? If not how to get it?
Implement some code :)
Alternatively you can check the proc output contents in /proc/asound/card*/pcm*/sub*/status. It'd be difficult to see the stop timestamp, though (as the application closes the stream immediately after that).
How to specify if i want the REALTIME/MONOTONIC_RAW trigger_time timestamp type output in /proc/asound/card*/pcm*/sub*/status?
Takashi
-- Thanks, Sekhar
On Thu, 08 Jul 2021 18:11:13 +0200, Muni Sekhar wrote:
On Thu, Jul 8, 2021 at 6:02 PM Takashi Iwai tiwai@suse.de wrote:
On Thu, 08 Jul 2021 14:19:12 +0200, Muni Sekhar wrote:
On Thu, Jul 8, 2021 at 4:59 PM Takashi Iwai tiwai@suse.de wrote:
On Thu, 01 Jul 2021 01:41:29 +0200, Muni Sekhar wrote:
Hi all,
From the user space test application , Is it possible to get the
trigger timestamp corresponding to SNDRV_PCM_TRIGGER_START & SNDRV_PCM_TRIGGER_STOP events for audio playback capture?
That's exactly what trigger_tstamp of snd_pcm_status corresponds for.
Does aplay and arecord have any command line options to get the trigger_tstamp? If not how to get it?
Implement some code :)
Alternatively you can check the proc output contents in /proc/asound/card*/pcm*/sub*/status. It'd be difficult to see the stop timestamp, though (as the application closes the stream immediately after that).
How to specify if i want the REALTIME/MONOTONIC_RAW trigger_time timestamp type output in /proc/asound/card*/pcm*/sub*/status?
It's not provided in a standard tool and you have to write some program by yourself, I suppose.
Takashi
participants (2)
-
Muni Sekhar -
Takashi Iwai