On Tuesday 03 June 2003 9:48 am, Chris Cannam wrote: > 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.)
Well in principle yes, but while we're still testing this kind of stuff it's useful to leave it to make sure that we've got everything covered. PLUS if people ever want to use LADCCA to reconnect ALSA devices then we need to be able to allow them to do that. > * Changing the record port from kaconnect will work, but only some > of the time Ok, fair enough. > 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? Yes, there is a mechanism for this. In fact have a look at kaconnect for a simple example. This would of course get a bit fiddly at the sequencer though wouldn't it? > * 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. We currently make all our JACK connections automatically too - but for advanced users this isn't necessarily the way they want to go. If we have a JACK and ALSA "expert" mode config option then we can let people make their own connections (through LADCCA or whatever mechanism). While a feedback mechanism for reconnecting is a possibilityit might all get a bit messily complicated. We could just maybe hide connections as default then and enable them in "expert mode" where the users are supposed to know what they're doing (or are willing to suffer the consequences). What we have now (in terms of connection management) works very well and I don't think we should touch it. BTW - do we have to Doc::syncDevices() everytime we App::setDocument? R ------------------------------------------------------- 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
