From: Bob Ham <node@users.sourceforge.net>
To: ALSA Development Mailing List <alsa-devel@lists.sourceforge.net>
Cc: Takashi Iwai <tiwai@suse.de>
Subject: Re: timestamps on recorded events
Date: 12 Apr 2002 11:52:25 +0100 [thread overview]
Message-ID: <1018608745.13866.2.camel@insanity> (raw)
In-Reply-To: <s5h8z7ule68.wl@alsa2.suse.de>
On Thu, 2002-04-11 at 11:31, Takashi Iwai wrote:
> // enable time-stamp-update mode
> snd_seq_port_subscribe_set_time_update(subs, 1);
> // if you want to get real-time (not tick), call the
> // following, too
> // snd_seq_port_subscribe_set_time_real(subs, 1);
Does the value of the integer that's passed to either of these functions
make any difference, or is it just their non-zeroness?
Bob
--
Bob Ham: bob@ham.org http://pkl.net/~node/
My music: http://mp3.com/obelisk_uk
GNU Hurd: http://hurd.gnu.org/
next prev parent reply other threads:[~2002-04-12 10:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.33.0204091221050.7128-100000@wotan.suse.de>
2002-04-11 9:42 ` timestamps on recorded events Richard Bown
2002-04-11 10:31 ` Takashi Iwai
2002-04-12 10:52 ` Bob Ham [this message]
2002-04-12 11:01 ` Takashi Iwai
2002-04-12 13:32 ` Richard Bown
2002-04-12 14:06 ` Takashi Iwai
2002-04-12 13:46 Joachim Backhaus
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=1018608745.13866.2.camel@insanity \
--to=node@users.sourceforge.net \
--cc=alsa-devel@lists.sourceforge.net \
--cc=tiwai@suse.de \
/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.