From: "Clemens Ladisch" <cladisch@fastmail.net>
To: paul santa clara <kesserich1@comcast.net>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Direct Delivery of NoteOn events
Date: Thu, 26 Oct 2006 09:23:47 +0200 [thread overview]
Message-ID: <1161847427.29328.274258312@webmail.messagingengine.com> (raw)
In-Reply-To: <68553F7D-DBC4-4D0E-A5A4-071B94359269@comcast.net>
paul santa clara wrote:
> On Oct 25, 2006, at 4:25 AM, Clemens Ladisch wrote:
> > What is your program doing after this call?
>
> The function enters into an infinite while{} which bombards alsa with
> events.
Should be OK.
> > If you don't wait until the event has been delivered, the queue
> > with the events still in it will be destroyed.
>
> Hmmm...I'm not sure you what you mean here.
When the program exits, all resources are cleaned up.
> Is there a function i can call to block the thread until ALSA has
> delivered the events?
snd_seq_sync_output_queue(), but this doesn't seem to be your problem.
Please check whether any of the ALSA functions returns an error code.
What gets output when you play to an instance of aseqdump?
Regards,
Clemens
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
next prev parent reply other threads:[~2006-10-26 7:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-23 19:58 Direct Delivery of NoteOn events paul santa clara
2006-10-24 8:00 ` Clemens Ladisch
[not found] ` <99C795AE-FCD2-4E95-ABE0-145AA81EFB58@comcast.net>
2006-10-25 8:25 ` Clemens Ladisch
2006-10-25 23:56 ` paul santa clara
2006-10-26 7:23 ` Clemens Ladisch [this message]
2006-10-26 19:26 ` paul santa clara
-- strict thread matches above, loose matches on Subject: below --
2006-10-24 22:24 paul santa clara
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=1161847427.29328.274258312@webmail.messagingengine.com \
--to=cladisch@fastmail.net \
--cc=alsa-devel@lists.sourceforge.net \
--cc=kesserich1@comcast.net \
/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.