Re: [orca-list] Trouble setting up speech-dispatcher with orca

[Michael Whapples <mwhapples aim com>]

Hello Halim,
That's useful information to know. Its one of the things which made me 
very annoyed about pulseaudio, it wanting to take over the ALSA device 
and all suggestions for allowing ALSA apps to work with it to need to go 
through pulseaudio's ALSA compatibility layer which required pulseaudio 
to run.

Also I agree with you on not wanting extra complexity for a console 
screen reader, the one big reason for a console screen reader is to have 
a system with minimal requirements to work which you can rely on. Adding 
complexity removes that advantage.

Luckily at the moment debian doesn't force pulse on you, but seeing how 
other distros have gone the time might come (I strongly hope it doesn't).

Michael Whapples
On 01/-10/-28163 08:59 PM, Halim Sahin wrote:
> Hi Bill,
>
> Running a consolescreenreader as user isn't a good idea because you will
> loose many comfort features.
> Starting several instances of pulse and managing it through consolekit
> or what ever will not change this.
> Btw I find it is ugly to add this complexity to all console apps only
> for beeing  compatible to pulse-audio or ubuntu' goals.
>
> I am now using an other setup for pa which doesn't block my well working
> alsa:
> I load the modules in my ~/.pulse/default.pa
> and tell them to use alsa's dmix.
> This is currently the best way for .
> me.
> This setup allows speechd running as system service and sblspeakup can
> operate very well.
> Br.
> Halim
>
>
>
>
>
>
>