All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Davis <paul@linuxaudiosystems.com>
To: alsa-devel@lists.sourceforge.net
Subject: using the sequencer with raw byte streams?
Date: Sun, 20 Jul 2003 19:28:02 -0400	[thread overview]
Message-ID: <200307202328.h6KNS2I01842@linuxaudiosystems.com> (raw)

is there a relatively simple way to use the sequencer with raw byte
streams? i want to create an "ASEQ_Port" type for libmidi++, but
unlike the current support port types, the sequencer seems to be
totally based on typed events. libmidi++ allows applications to format
arbitrary messages and have them delivered to a port. it also has its
own sophisticated parser that includes heavy use of libsigc++ to allow
anonymous notification of many more event types than the sequencer
code currently defines. 

i'd like to find a way to connect these two abstractions together
somehow, since it would make Ardour play "nice" in the set of
sequencer clients that already exist. i can see the "RAW" event type
flag, which looks as if it might work for delivery data to the
sequencer, but i can't see any mechanism for retrieving unparsed data
from the system. can it be done?


-------------------------------------------------------
This SF.net email is sponsored by: VM Ware
With VMware you can run multiple operating systems on a single machine.
WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the
same time. Free trial click here: http://www.vmware.com/wl/offer/345/0

             reply	other threads:[~2003-07-20 23:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-20 23:28 Paul Davis [this message]
2003-07-21 14:44 ` using the sequencer with raw byte streams? Takashi Iwai
2003-07-21 17:18   ` Paul Davis
     [not found]   ` <20030721171249.255CB14C36@Cantor.suse.de>
2003-07-21 17:27     ` Takashi Iwai
2003-07-29 17:24       ` 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=200307202328.h6KNS2I01842@linuxaudiosystems.com \
    --to=paul@linuxaudiosystems.com \
    --cc=alsa-devel@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.