Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Brian Victor <bhv1@psu.edu>
To: alsa-devel@lists.sourceforge.net
Subject: Re: General Guidelines?  (MIDI)
Date: Thu, 16 Jan 2003 12:23:59 -0500	[thread overview]
Message-ID: <20030116172359.GA32330@bhv1.adelphia.net> (raw)
In-Reply-To: <Pine.LNX.4.21.0301161630050.665-100000@summer.quitte>

On Thu, Jan 16, 2003 at 04:32:05PM +0100, Tim Goetze wrote:
>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.

I've tried both, actually.  output() does not show any queued events in
/proc/asound/seq/queues; output_direct() does.  miniArp.c uses
output_direct, and seems to work.  Neither produces any output in my
test program.

I've removed all attachments to wxWindows, so anyone should be able to
compile my test program.  So I don't have to keep sending snippits out
of context, the code is here:

http://www.personal.psu.edu/users/b/h/bhv1/nowx.cc      or
http://www.personal.psu.edu/users/b/h/bhv1/nowx.cc.html (syntax colored)
(g++ nowx.cc -o nowx -lasound)

>you may want to look at alsa-lib/test/playmidi1.c for
>another reference.

That could be useful, but at a glance I don't see anything important in
there that I'm not doing.  This is really perplexing me.

>>(Which begs another question: what does PPQ stand for?  Something per
>>quarter?)
>ticks/quarter (aka 'parts per quarter').

I figured it was something like that.  Thanks.

-- 
Brian


-------------------------------------------------------
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

  reply	other threads:[~2003-01-16 17:23 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 [this message]
2003-01-16 18:14                 ` Takashi Iwai
     [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=20030116172359.GA32330@bhv1.adelphia.net \
    --to=bhv1@psu.edu \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox