Richard Bown wrote: > I presume that was Chris doing some fiddling to our ALSA client/port > specification and I can't work out why it would be to anyone's > benefit to hide our ALSA ports from being manually routed.
Hiding them from kaconnect altogether is probably a bad idea and wasn't really the intention. There are good reasons why reconnecting them from kaconnect isn't a very good idea though: * Rosegarden currently connects to every available port anyway for writing, so I can't see that kaconnect is going to help you very much there. (Actually this is something I've been reconsidering: since we have the principle of connections in the GUI now, we could switch to only connecting to the ports we actually need.) * Changing the record port from kaconnect will work, but only some of the time, and when it fails it'll do so silently (I think it'll fail whenever there was previously no valid record port, because AlsaDriver::m_midiInputPortConnected will never be set to true). And even when it works, it won't update the relevant part of the GUI. So it seems like a bad idea to encourage it. Anyone who tries to do this in preference to finding out how to do it in the GUI itself (which probably means anyone who's used other ALSA apps before using RG) will risk a very bad experience. Alternatively is there some way to respond to being reconnected, so that we can do the same thing as if the user had done it from the GUI? * Similarly, if we did switch over to only making the output connections we actually need, we'd have the same problem with output -- the GUI wouldn't keep track. Chris ------------------------------------------------------- This SF.net email is sponsored by: eBay Get office equipment for less on eBay! http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 _______________________________________________ Rosegarden-devel mailing list [EMAIL PROTECTED] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
