From: Garett Shulman <shulmang@colorado.edu>
To: alsa-user@lists.sourceforge.net, alsa-devel@lists.sourceforge.net
Subject: sequencer filter client
Date: Fri, 23 Jan 2004 14:26:05 -0700 [thread overview]
Message-ID: <4011916D.4040601@colorado.edu> (raw)
Hello, I am trying to create a very simple midi filter client for the
alsa sequencer based on aseqview-0.1.4. I have alsa 0.9.8. This code
shows the input and the output port in aconnect when executed. And, when
the raw_midi client is connected The callback does get called when I
play keys on my piano. However, Its as though the message is getting
sent back to this client and not on to the next client. The
process_event function keeps getting called over and over again with the
same message when I hit one piano key. It's as though it is sending
itself the message. Any Ideas are greatly appreciated. -Garett
#include "portlib.h"
int process_event(port_t *p, int type, snd_seq_event_t *ev, int
*priate_data)
{
port_write_event(p, ev, 0);
}
int main()
{
unsigned int caps = SND_SEQ_PORT_CAP_WRITE |
SND_SEQ_PORT_CAP_SUBS_WRITE | SND_SEQ_PORT_CAP_READ |
SND_SEQ_PORT_CAP_SUBS_READ;
port_client_t *client = port_client_new("MIDI filter",
SND_SEQ_OPEN_DUPLEX);
port_t *port = port_attach(client, "FILTER port", caps,
SND_SEQ_PORT_TYPE_MIDI_GENERIC);
int *priv_data;
/* add callback */
port_add_callback(port, PORT_MIDI_EVENT_CB,
(port_callback_t)process_event, priv_data);
port_client_do_loop(client);
return port_detach(port);
}
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
next reply other threads:[~2004-01-23 21:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-23 21:26 Garett Shulman [this message]
2004-01-26 13:57 ` sequencer filter client Clemens Ladisch
2004-01-27 3:44 ` Garett Shulman
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=4011916D.4040601@colorado.edu \
--to=shulmang@colorado.edu \
--cc=alsa-devel@lists.sourceforge.net \
--cc=alsa-user@lists.sourceforge.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.