On Saturday 07 May 2005 19:52, Chris Cannam wrote: > OK, I've just merged the ALSA ports code across to HEAD. > > To repeat the summary from my earlier email: > > The principle is pretty simple. Before, we created a single ALSA > sequencer port, connected it to everything, and marked each outgoing > event as intended for a particular recipient. Now, we create one ALSA > sequencer port for each "playback device" as shown in the device > manager, and connect it according to the "connection" shown in the > device manager. Changes to the connection from external clients (so > long as they result in a 1-1 connection mapping) cause the connection > to be changed in the Rosegarden device manager as well.
I only want to add a little bit to your words: Instead of sending each event to a particular destination, we send now the events to "all subscribers" of the output ports, which means that if you use a external connection manager (qjackctl) to subscribe more programs or devices to some RG's output port, every outgoing event by that port will be delivered at once to all subscribed clients, even if you only see one subscription in the device manager. For instance, you can attach a MIDI monitor program (like KMidiMon) to any Rosegarden output port, and watch the event log while you are still listening the tracks assigned to that port. That is the usual behavior for an ALSA program, but it was not possible to do with RG before. Regards, Pedro ------------------------------------------------------- This SF.Net email is sponsored by: NEC IT Guy Games. Get your fingers limbered up and give it your best shot. 4 great events, 4 opportunities to win big! Highest score wins.NEC IT Guy Games. Play to win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20 _______________________________________________ Rosegarden-devel mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
