From: Mark K. <mk...@co...> - 2004-08-23 21:18:29
|
Pedro Lopez-Cabanillas wrote: > Hi Mark, > > On Monday 23 August 2004 18:36, Mark Knecht wrote: > >> How can I control RG's MIDI routing? > > > Rosegarden has changed a little between 0.9.8 and 0.9.9 on how it manages this > issue, but only regarding the RG input ports (record devices). In the new > Rosegarden 0.9.9 it is possible to use an external connection manager (QJC, > aconnect, etc.) to subscribe any number of event sources to the RG input > port. It is also possible to use Studio->Manage MIDI Devices to manage > record devices. In 0.9.8 you MUST use the Studio manager, and you can select > only one record device at a time. > > The output connections are automatic in both 0.9.8 and 0.9.9. RG always > subscribe its output port to every ALSA sequencer input port existing in the > system. If some new program or device starts when RG is already running, it > is detected and subscribed automatically. You can manage how your connections > are named inside RG using Studio->Manage MIDI devices. This name is > important, because it's used to build the RG instrument's name. To change the > MIDI destination for the events belonging to some track, you must change the > instrument for that track (press the mouse button ald hold it during a while > to open the instrument popup menu). The instrument parameter box has a header > with two labels reflecting this setting. The output connections can't be > managed with an external MIDI connection manager, neither in 0.9.8 nor in > 0.9.9; you must use RG internal functions and procedures to manage your MIDI > output routing. > > Regards, > Pedro > Thanks Pedro. I'm using a slightly older 0.9.9 version from CVS. To ensure I'm up to date I'm building CVS from today since Gentoo doesn't have a maked ebuild for 0.9.9 released in July. However, from my 0.9.9 version I was running this morning it does not appear that RG would pay any attention for QJC. Hopefully that will be better when this build finishes. As for using Studio->Manage MIDI Devices to manage the connections I guess I'll just have to try some more. My first attempt this morning did not make sense. For instance, if I had ZynAddSubFX running, and I changed a connection to that name in Manage MIDI Devices, then the track output started giving me options that make no sense, like MIDI channels the synth won't do anythign with. It was also unclear what I should do if I start mutliple copies of the same synth. Overall it looked like Manage MIDI Devices wants to treat soft synths like they are hardware MIDI ports. Not sure how well that works, but I'll try again this afternoon with new code. Thanks for the time to respond. I do appreciate the clarifications. With best regards, Mark |