|From:||S. Christian Collins|
|Subject:||Re: [fluid-dev] two questions|
|Date:||Sun, 24 May 2009 10:03:05 -0500|
|User-agent:||Thunderbird 18.104.22.168 (X11/20090409)|
Regarding transposing a channel, have you tried Qmidiroute? I have used Qmidiroute when performing live to send different areas of the keyboard to different channels, and you can transpose not only notes, but controllers as well. You can also do sound layering this way. And... I can't test it, but you should also be able to filter out aftertouch events in this manner.
In my case, I use Rosegarden to send patch change events to the appropriate channels (I have tracks set aside just for this purpose), and then I also have one or more "controller" tracks that are mapped to Qmidiroute. The only additional step is to use aconnectgui to route the first Qmidiroute output port to the Qsynth input.
So, to summarize my Rosegarden setup, I have 16 tracks mapped to Qsynth (channels 1-16 respectively). Each of those 16 tracks initializes its respective Qsynth channel with the desired patch, volume, panning, effects, etc., and can also be used to perform those individual instruments if so desired. Then, I have one ore more "controller" tracks that are set to play through Qmidiroute, according to the appropriate channel. So for example, my first controller track outputs to Qmidiroute channel 1. Qmidiroute then takes that channel's imput and splits the keyboard--the bottom half goes to Qsynth channel 1 and the top half goes to Qsynth channel 2. My second controller track would output to Qmidiroute channel 2, which would have a different set of rules for that channel, and so on.
It's an extremely flexible setup. Qmidiroute is in the Jaunty repositories, but I'm not sure about 8.04.
Hope this helps :)
|[Prev in Thread]||Current Thread||[Next in Thread]|