From: Josh Lehan <alsa@krellan.com>
To: alsa-devel@alsa-project.org
Subject: Newbie question: Sending untimed MIDI data to ALSA seq
Date: Sat, 09 Jan 2010 15:13:23 -0800 [thread overview]
Message-ID: <4B490D93.1050506@krellan.com> (raw)
Hello.
Newbie question: I'm wondering about sending untimed MIDI data to the
ALSA sequencer subsystem.
The application would be for a "beep"-like program, from the command
line, that instead of making beeps, would play MIDI instruments to make
better-sounding beeps.
I have TiMidity hooked up into ALSA, as a softsynth, and it works just
fine for playing MIDI data sent to it by ALSA.
The "aplaymidi" command works for .MID files, and the "vkeybd" program
works for simulating a keyboard and sending in untimed MIDI data. The
"aseqview" program also works great for watching the notes being played,
as they go by. So, my MIDI software stack appears to be in order. I
don't have a hardware synthesizer hooked up at the moment (my Kawai K1
is showing its age, and a few keys are broken).
I also looked at "amidi", which features a -S option to send in untimed
MIDI bytes, but unfortunately, that addresses an entirely different
namespace. Evidently, it only speaks to "RawMIDI" devices, of which
TiMidity is not.
So, I can't generate untimed MIDI data on my own. I was thinking of
writing a small "midibeep" program that would do this, similar to what
vkeybd does, but without requiring any user interaction.
Does such a program already exist?
Thanks!
Josh
next reply other threads:[~2010-01-09 23:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-09 23:13 Josh Lehan [this message]
2010-01-12 9:48 ` Newbie question: Sending untimed MIDI data to ALSA seq Takashi Iwai
2010-01-13 19:17 ` Josh Lehan
2010-01-12 11:39 ` Clemens Ladisch
2010-01-13 19:22 ` Josh Lehan
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=4B490D93.1050506@krellan.com \
--to=alsa@krellan.com \
--cc=alsa-devel@alsa-project.org \
/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.