All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Muni Sekhar <munisekharrms@gmail.com>
Cc: alsa-devel <alsa-devel@alsa-project.org>,
	kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: trigger timestamp
Date: Thu, 08 Jul 2021 14:32:56 +0200	[thread overview]
Message-ID: <s5heec956kn.wl-tiwai@suse.de> (raw)
In-Reply-To: <CAHhAz+guERMjmT_bRrgWzMoKkH2S0Zv0JatjpbNJZnLj+RyxXw@mail.gmail.com>

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

WARNING: multiple messages have this Message-ID (diff)
From: Takashi Iwai <tiwai@suse.de>
To: Muni Sekhar <munisekharrms@gmail.com>
Cc: alsa-devel <alsa-devel@alsa-project.org>,
	kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: trigger timestamp
Date: Thu, 08 Jul 2021 14:32:56 +0200	[thread overview]
Message-ID: <s5heec956kn.wl-tiwai@suse.de> (raw)
In-Reply-To: <CAHhAz+guERMjmT_bRrgWzMoKkH2S0Zv0JatjpbNJZnLj+RyxXw@mail.gmail.com>

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

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

  reply	other threads:[~2021-07-08 12:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-30 23:41 trigger timestamp Muni Sekhar
2021-06-30 23:41 ` Muni Sekhar
2021-07-08 11:29 ` Takashi Iwai
2021-07-08 11:29   ` Takashi Iwai
2021-07-08 12:19   ` Muni Sekhar
2021-07-08 12:19     ` Muni Sekhar
2021-07-08 12:32     ` Takashi Iwai [this message]
2021-07-08 12:32       ` Takashi Iwai
2021-07-08 16:11       ` Muni Sekhar
2021-07-08 16:11         ` Muni Sekhar
2021-07-08 16:15         ` Takashi Iwai
2021-07-08 16:15           ` Takashi Iwai

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=s5heec956kn.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=kernelnewbies@kernelnewbies.org \
    --cc=munisekharrms@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.