Hi You'd be able to set a per-client and per-user output if you set speech-dispatcher to go through Pulseaudio. This is already supported, though SD's Pulse code needs some reworking to optimize its speed. The Unix domain sockets wouldn't fix this, all this would do is eliminate the requirement for sd to communicate over TCP locally, meaning it would be a bit faster and would not go down if the networking subsystem dies. As far as I know, Pulseaudio would be the only way to handle the per-client audio streams as things stand now, though in theory support for doing this via ALSA alone could be coded into sd directly. Given that Pulse seems to be the way forward though, and we can already choose the output stream on a per-user basis, it might be a good idea to concentrate on what is already there. On Sun, 2009-04-19 at 11:28 +0000, Michael Whapples wrote:
I have a comment regarding this. My concern/question may be attended to by some of the already propose stuff, I'm just not quite sure whether it could actually work only with what is proposed. My thought is, is there anyway the audio output could be set per user or maybe even per client? By this I mean audio output as in sound card selection. Could the unix sockets connection idea and client spawning solve this? Also while this is only aimed at gnome/orca intergration, how might this impact on a system using gnome but also with speakup in the text console (IE. both gnome and non-gnome clients potentially requiring speech). I have to be honest that I am not fully sure how it might be done and how it might be for a user to use. As an example I am thinking a little how SAPI5 can be used in windows. You have a tool where you can set defaults (including output audio device) but then individual applications using SAPI5 can configure it (again including the audio device) and so override the defaults. Should an application not set something then the default is used. This SAPI5 example may work to an extent for gnome, but it doesn't help for the part how gnome and non-gnome clients may cooperate. Michael Whapples On 23/12/42 19:59, Willie Walker wrote:Hey All: With the planned removal of CORBA from GNOME 3.0, we need to resolve the situation with GNOME speech (GNOME speech currently uses CORBA). Luke Yelavich from Canonical has developed a proposal at http://www.themuso.id.au/speech/speech-dispatcher-orca-integration.txt This proposal uses speech dispatcher as a starting point and has provisions to address a number of considerations for different operating systems and different operating environments. I'd appreciate it if you could review this proposal and provide your constructive feedback. Note that constructive feedback does not include any of the following: 1) This is dumb. 2) How do I configure speech-dispatcher on Ubuntu? 3) Will Cepstral be coming out with new voices? 4) Which netbook should I buy? 5) I cannot navigate my.favorite.page with Orca. Why? 6) Did OOo come out with a new release yet? 7) etc. Note that replying to this message with anything like the above may cause the moderation filtering mechanism I have in place to fire and put you on moderation. So, do the simple thing and be constructive. An example of constructive feedback would be "I'm concerned about feature X. It seems to prevent me from doing Y. As an alternative, I propose Z." Thanks! Will_______________________________________________ Orca-list mailing list Orca-list gnome org http://mail.gnome.org/mailman/listinfo/orca-list Visit http://live.gnome.org/Orca for more information on Orca. The manual is at http://library.gnome.org/users/gnome-access-guide/nightly/ats-2.html The FAQ is at http://live.gnome.org/Orca/FrequentlyAskedQuestions Netiquette Guidelines are at http://live.gnome.org/Orca/FrequentlyAskedQuestions/NetiquetteGuidelines
Attachment:
signature.asc
Description: This is a digitally signed message part