All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brix <brix82@libero.it>
To: alsa-devel@lists.sourceforge.net
Subject: Re: troubles programming with the sequencer
Date: Thu, 29 Jan 2004 21:21:48 +0100	[thread overview]
Message-ID: <20040129212148.07de1671.brix82@libero.it> (raw)
In-Reply-To: <Pine.HPX.4.33n.0401261447190.24795-100000@studcom.urz.uni-halle.de>

On Mon, 26 Jan 2004 14:52:59 +0100 (MET)
Clemens Ladisch <clemens@ladisch.de> wrote:

> The default instrument is 0 (grand piano).

Ok

> You can send program change messages with the sequencer, too.

This is what i do in the set_chan_instr() function, it works fine.

> This does not work on big-endian machines, use char for ch.

Ok

> If the rawmidi device is already opened, it may not be possible for
> the sequencer to open it, too.  Call snd_rawmidi_close, or leave this
> code out altogether.

Now i don't touch anything about instruments and channels, and i don't use any of the rawmidi functions, but it still doesn't work.

> Directly after starting the queue, the program exists, and the queue
> gets destroyed.  Try snd_seq_sync_output.

There is no such library function...
I tried calling sleep() for a few tenth of seconds, hoping the sequencer would flush out anything, but it did not help.

-- 

	Hardware is never old.
	People just choose the wrong OS.


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

  reply	other threads:[~2004-01-29 20:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-23 18:05 troubles programming with the sequencer Brix
2004-01-26 13:52 ` Clemens Ladisch
2004-01-29 20:21   ` Brix [this message]
2004-01-30 13:51   ` Brix

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=20040129212148.07de1671.brix82@libero.it \
    --to=brix82@libero.it \
    --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.