From: Garett Shulman <shulmang@colorado.edu>
To: fluid-dev@nongnu.org, alsa-user@lists.sourceforge.net,
alsa-devel@lists.sourceforge.net
Subject: fluidsynth multiple channels & ladspa
Date: Thu, 05 Feb 2004 17:11:49 -0700 [thread overview]
Message-ID: <4022DBC5.8020704@colorado.edu> (raw)
Hello,
Does anybody know if it is possible to get fluidsynth to output
different instruments on different midi channels to different audio
channels? For example, I would like to send a piano instrument on midi
channel 1 out of channels 1 & 2 of the my delta66 and then have a rhodes
ep on midi channel 2 sent out of channel 3 of the delta66 to an fx
processor.
Also, is there any means to control ladspa parameters with midi signals
in fluidsynth?
Thanks for any info.
-Garett
-------------------------------------------------------
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-02-06 0:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4022DBC5.8020704@colorado.edu \
--to=shulmang@colorado.edu \
--cc=alsa-devel@lists.sourceforge.net \
--cc=alsa-user@lists.sourceforge.net \
--cc=fluid-dev@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox