Re: [orca-list] [Fwd: Re: [g-a-devel] Speech-dispatcher/orca integration specification, first draft.]



Here is how I thought unix sockets combined with the spawning of SD would help with achieving what I am asking for.

To help explain, here's an example.

Let's say that my computer boots up to a text console (IE. X/gnome isn't started automatically). I want access to the text console via speakup and software speech using speechd-up. Now I might want the login procedure spoken out so I have speechd-up started in an init script. With the auto-spawning speechd-up will start SD for me and set it to use a configuration set by speechd-up or a default configuration should speechd-up not give a configuration or specify every option. Now speechd-up could connect using unix sockets (reason will come clear in a minute). Now once logged in to the system I may decide I want to use orca in gnome (may be to browse a website using firefox as lynx doesn't manage it) so I start gnome. When orca starts it spawns another SD specifying the configuration (again if not given it could fall back to a user default and if no user default then back to a system default). Now we will have multiple SDs running on the system, so orca will need to connect using a unix socket (that's what I understood the proposal to suggest the reason for unix socket communication in SD would be for). Both instances of SD will have their own configuration (if as I am asking for potentially that configuration difference could even include different audio devices).

Now the limitations I see preventing this are that SD doesn't allow configuration of output audio device by clients and the unix sockets proposal is only per user, rather than per user per client.

As for pulse... Let's put it this way, I haven't had success with it (never even to a point where it is useable let alone useful), many seem to have had trouble with it and I'm not convinced that distributions include it in such a way that it helps us (IE. treating it as a user service rather than a system service, the latter making more sense to me as the audio belongs to the system and we need speech output at other times than as a user, eg. speakup logging into a system). As for the idea of a sound server, esd never caused me problems like pulse, at least if something didn't need to use it, then esd allowed other things access the hardware rather than insisting it goes through a hoop which may not even be there or be working. NOTE: I am still waiting to find out what problem pulse solves, I can only find problems pulse causes, could someone let me know what pulse solves.

Michael Whapples
On 23/12/42 19:59, Jacob Schmude wrote:
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




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]