Re: [orca-list] Built in Controls for Espeak Pretty Please with Sugar, cheeries, whatever it takes on top :)

[kendell clark <coffeekingms gmail com>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512


hi
Uh yeah that sounds nasty. But if it ever gets done, whoever
accomplishes it will instantly have solved some really brain busting
problems for a lot of blind people, and the cause of tons of rants
about anything and everything that could  possibly be responsible for
pulse messing with things lol. Speaking of pulse, I've talked to the
pulse developers, and they've pretty much disavowed any
responsibility. Basically, it's not our software, it's something else.
Whether this is true or not, I don't know, but for whoever starts work
on this, at least you may not have to try dealing with pulse audio
developers, which can sometimes be a great experience, and sometimes
be frustrating, depending on the phase of the moon.


On 08/29/2014 02:10 AM, Thomas Ward wrote:
> On 8/29/14, Luke Yelavich <themuso ubuntu com> wrote:
> > The big issue with console speech is audio and permissions.
> > Whether you are using Pulse, which by the way uses ALSA, or ALSA
> > directly, there is still the problem of accessing the sound card.
> > Things generally work when you are already logged into a console
> > session. If everything is running and configured to work in the
> > user session, all is well, however you cannot review a terminal
> > where you are logged in, because the software in your user 
> > session doesn't have permission to talk to the audio hardware.
>
> Ah, thanks for explaining that. I wasn't quite clear before what
> the problem was with console speech before, but now I get it. That
> is a nasty problem, and doesn't sound like it is an easy one to
> resolve.
>
> > In Vinux 4, we managed to work up a solution, which whilst still
> > a little buggy, does work. This solution needs to be rewritten to
> > work with Systemd/Logind, and the Systemd part of the solution
> > needs to be sent upstream. We then need to adapt espeak, and
> > speechd-up to work properly, and configure the device node for
> > speakup to be controllable by Systemd to allow user sessions to
> > talk to it.
>
> Ouch! That definitely does not sound like fun. I'm not really 
> qualified to do something like that at this point, but I do not
> envy the person or people who gets stuck with that task. 
> _______________________________________________ orca-list mailing
> list orca-list gnome org 
> https://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
> Log bugs and feature requests at http://bugzilla.gnome.org Find out
> how to help at http://live.gnome.org/Orca/HowCanIHelp
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCgAGBQJUACkEAAoJEGYgJ5/kqBTdhfwQAKg3yhHZZMwQQ0FqAnYCERNL
/rXon2ycesNhbMfVXM758vFVy987obt3xBBTIcqgMv80oViwywOun+fkaocP/GVP
l4Gwby2U8QOkH+yVmsGnp2SWIunTtTmPrOUBcmeC5xGeJB42J/+/v6tJ9KOfh+Lx
+EUHtEYb+Wp0az4LYqy9YJU33JV4Q/8M0Ru5wEOTQQAkk+8vF7nFvxTBNQ2BYTlR
a1q65gJkr31oR0zGvyEZtEZC/kgPhNksArJvoY4uM2zxppWDw4k0xVbPCvOT4o1B
nidlsQLm9Hxvlw9kuY7C1V3oPFzVkahfoHPmgvt316PxykYDMpcDmaDOInCSKg0U
bFmiK1b4vfHF4OEhrrieUuo/Q4MwmO485rg8ujFEd36weafme33fMKekhcB4lBQO
ZKNYhtw4mcBi1DSIV8jdBdDsAKqowzaN4uFc01Y/rkbevFRUQ1MnCCtoBwSh54Jy
Y9BebQKaMatCVT1LRSCoxiOz0AEW90wNB/LBwmHQkzTOuCRXA8wVa9IlArLtmsz1
YUks7NSUMa/sY5+Ax71ct+fqQD2abP3PJ8N0VnuxGI8iFMUqfuQ/S5fOUQbtuHkc
Xku14xj8aIVwXF10G/noHCI+bT/d/D1k/DGMTSJcNVVQt2zc6AKt+U8IhLRmHTDv
gmyKK0s6ADileFzGxuRq
=l70W
-----END PGP SIGNATURE-----