On Sunday 08 Jun 2003 7:23 am, Richard Bown wrote: > Ok, this is something of a common request actually. You have to > bear in mind that our primary objective is making it easy for > people to get up and running with device stuff but there is > definitely also a need for "expert mode" where we only get as far > as creating our own ALSA ports and no further. This is so that > people like yourself and people (say) using LADCCA can have all the > control they want.
Right, and before we go any further with this: I should remind us that the only way we can support aconnect (in anything other than a read-only mode) is to create a port for each of Rosegarden's devices, instead of just creating one port as we do at the moment. Otherwise when you connect Rosegarden's port to another port, Rosegarden will have no way to know which device you intended to connect from. If we're going to do that, then we should probably do it right away (and always do it, not just optionally). I don't think it's true to say that we _need_ to support aconnect, in the sense that it won't add any functionality in principle -- manipulating RG ports interactively using (k)aconnect would allow you to do nothing not already possible in RG alone, and we have a programmatic interface as well (in the sequencer's DCOP interface). It's simply a question of convenience for people using aconnect already -- of course that means practically anyone using ALSA seriously, but I don't think we should forget that it's about convenience rather than raw capability. Chris ------------------------------------------------------- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. _______________________________________________ Rosegarden-devel mailing list [EMAIL PROTECTED] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
