All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Tim Goetze <tim@quitte.de>
Cc: Brian Victor <bhv1@psu.edu>, alsa-devel@lists.sourceforge.net
Subject: Re: General Guidelines?  (MIDI)
Date: Thu, 16 Jan 2003 19:14:14 +0100	[thread overview]
Message-ID: <s5hy95l0xop.wl@alsa2.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.21.0301161630050.665-100000@summer.quitte>

At Thu, 16 Jan 2003 16:32:05 +0100 (CET),
Tim Goetze wrote:
> 
> Brian Victor wrote:
> 
> >On Thu, Jan 16, 2003 at 08:39:23AM +0100, Clemens Ladisch wrote:
> >>Brian Victor wrote:
> >>> Monitoring /proc/asound/seq/queues shows the events being queued, but as
> >>> soon as the queue starts, all 400 notes leave the queue instantly; none
> >>> are played.
> 
> afaik, you should use snd_seq_event_output() instead of
> snd_seq_event_output_direct() -- the latter is supposed
> to by-pass the queue for instant transmission.

well, this is not exact:  snd_seq_event_output_direct() sends the
event without "output buffer" on the user-space.
if the event record has a proper queue value (i.e. event.queue !=
SND_SEQ_QUEUE_DIRECT), it is scheduled on the specified queue.

for by-passing the scheduling on the queue, you need to mark the queue
via snd_seq_ev_set_direct().

snd_seq_event_output() will put the event onto the output buffer.
the buffered events won't be sent and stay on the buffer until either
the buffer becomes full or snd_seq_drain_output() is called
explicitly.

this i/o-buffer was introduced to reduce the amounts of read/write,
ioctls.  this could be implemented more sofisticatedly as a high-level
library...


Takashi


-------------------------------------------------------
This SF.NET email is sponsored by: Thawte.com
Understand how to protect your customers personal information by implementing
SSL on your Apache Web Server. Click here to get our FREE Thawte Apache 
Guide: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0029en

  parent reply	other threads:[~2003-01-16 18:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-11 18:31 General Guidelines? (MIDI) Brian Victor
2003-01-13  9:25 ` Clemens Ladisch
2003-01-13 10:02   ` Takashi Iwai
2003-01-14 21:20     ` Brian Victor
2003-01-15 11:43       ` Clemens Ladisch
2003-01-16  3:27         ` Brian Victor
2003-01-16  7:39           ` Clemens Ladisch
2003-01-16 13:41             ` Brian Victor
2003-01-16 15:32               ` Tim Goetze
2003-01-16 17:23                 ` Brian Victor
2003-01-16 18:14                 ` Takashi Iwai [this message]
     [not found] <E18ZGLH-0005nh-00@sc8-sf-list2.sourceforge.net>
2003-01-16 21:27 ` Pedro Lopez-Cabanillas
2003-01-16 22:37   ` Brian Victor
2003-01-19 22:21     ` Frank van de Pol

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=s5hy95l0xop.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=bhv1@psu.edu \
    --cc=tim@quitte.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.