23 Jan
2005
23 Jan
'05
9:11 a.m.
On Sun, 23 Jan 2005 12:44:14 +0100
Jens M Andreasen <jens.andreasen(a)chello.se> wrote:
On lör, 2005-01-22 at 21:22 -0800, Jeffrey Brown
wrote:
Ack, i would definetly go with midi output. This makes setting the
program up a little more difficult for the user (as he has to connect
the midi to something, either a hardware midi synth or a softsynth
(autoconnecting is imho not the right thing to do)). To the OP:
Programming ALSA seq is pretty straightforward, but you might also take
a look at TSE3 [which is a cross platform midi lib]. Alternatively i
think fluidsynth is available in library form, so it can be integrated
into programs..
http://tse3.sf.net
--
Palimm Palimm!
http://affenbande.org/~tapas/
All I'll ever need is a library that will let
me
playback a sample at a certain set of frequencies --
like 6 at a time (bass tone, high tone, and a
four-note chord) -- until keyboard input signals it to
stop. In fact, even that's more than I need -- if
playing a sample is hard, I'd be perfectly happy
listening to square waves.
Perhaps driving a softsynth/sampler would be shortest path? Your job
would then be to figure out how to discover and connect in ALSA, and
then output the relevant note-on/note-off.