From: fons adriaensen <fons.adriaensen@skynet.be>
To: "Kjetil Svalastog Matheussen <k.s.matheussen@notam02.no>"
<k.s.matheussen@notam02.no>
Cc: Alfons Adriaensen <fons.adriaensen@alcatel.be>,
jackit-devel@lists.sourceforge.net,
alsa-devel@lists.sourceforge.net
Subject: Re: [Jackit-devel] Reading alsa midi-data inside the jack client process thread
Date: Fri, 8 Jul 2005 19:34:17 +0200 [thread overview]
Message-ID: <20050708173417.GA4959@linux-1> (raw)
In-Reply-To: <26283.212.169.96.218.1120825827.squirrel@webmail.uio.no>
On Fri, Jul 08, 2005 at 02:30:27PM +0200, Kjetil Svalastog Matheussen <k.s.matheussen@notam02.no> wrote:
> if (snd_seq_event_input_pending (seq,1)) {
> while(snd_seq_event_input(seq,&event);
>
> which I think should do the same... Guess I just have to read the source. :-)
OOPS, I didn't see the 'while' when commenting on this.
AFAICT it will do the same as my code, if you set the seq
to non-blocking mode.
Happy coding !
--
FA
-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted by HP,
AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar
next prev parent reply other threads:[~2005-07-08 17:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-08 10:36 Reading alsa midi-data inside the jack client process thread Kjetil Svalastog Matheussen <k.s.matheussen@notam02.no>
2005-07-08 11:42 ` Alfons Adriaensen
2005-07-08 12:30 ` [Jackit-devel] " Kjetil Svalastog Matheussen <k.s.matheussen@notam02.no>
2005-07-08 15:11 ` Alfons Adriaensen
2005-07-08 16:26 ` Kjetil Svalastog Matheussen <k.s.matheussen@notam02.no>
2005-07-08 17:34 ` fons adriaensen [this message]
2005-07-08 13:57 ` Clemens Ladisch
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=20050708173417.GA4959@linux-1 \
--to=fons.adriaensen@skynet.be \
--cc=alsa-devel@lists.sourceforge.net \
--cc=fons.adriaensen@alcatel.be \
--cc=jackit-devel@lists.sourceforge.net \
--cc=k.s.matheussen@notam02.no \
/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.