[BRLTTY] some strange issues with brltty 5.3.1

[kendell clark]

hi
Good points, all of them. I'm tired, it's nearly 7 AM and my brain's a
little fuzzy. I didn't mean shame literally, I meant ... if they start
to blow me off you could say something that would convince them to help.
I think what I'll do first is try to get this fixed at the pulse level.
If that fails, you can try to fix brltty to have espeak use alsa,
bypassing pulse. I'm not nearly enough of a programmer to have any idea
how to do so. If I can get this fixed this will affect more than just
brltty, it will also enable speakup to work seemlessly like it's
supposed to. The actual error is a little greek to me, but there's a
"connection refused" message which is crystal clear even to me. Pulse is
refusing to let espeak go through, and that's unacceptable.
Thanks
Kendell Clark

Thanks
Kendell Clark


Dave Mielke wrote:
> [quoted lines by kendell clark on 2016/05/08 at 06:34 -0500]
>
>> Would you or some other programmer be willing to hang out on their irc channel 
>> #pulseaudio on irc.freenode.net in case I need re-enforcements?
> I myself don't like hanging out on IRC channels because it means that I have to 
> read through a lot of other stuff in order to pick out what applies to the 
> issue(s) I'm actually currently caring about. That's why I much prefer email 
> and IM.
>
>> Pulse audio running in system mode isn't an option for our distro either. In 
>> addition to it being complicated to set up,
> I can help you with that. I'd need to do the same thing as you, though, i.e. 
> restudy their documentation. So, should you want me to help, I'll probably beg 
> for a root-capable account to log directly into so that I can just work on it. 
> Then, of course, I'd tell you exactly what I did to get it to work. If you 
> choose this approach then feel free to contact me off list with any security 
> sensitive details.
>
>> I don't like the idea of users being able to affect other user's sounds and 
>> per application volumes being set per system, not per user.
> But you control that. The only accounts that can connect to Pulse Audio are 
> those in the pulse-access group. Of course, if you'd like regular users to be 
> able to play audio (which you should) then, yes, they'd also need to be in that 
> group.
>
> The last time I looked into this kind of stuff, I'm sure what I discovered is 
> that Pulse Audio ultimately uses an ALSA device to communicate to the actual 
> sound card. I'm wondering, therefore, if there might be some way to tell eSpeak 
> to directly use the under-lying ALSA device rather than to go through Pulse 
> Audio.
>
>> So it's  back in the trenches with me. 
> Not necessarily. If eSpeak can be told to directly use ALSA then your problem 
> should be solved.
>
>> Sometimes I
>> wish more people did my job ... 
> We all have that problem in one way or another. :-)
>
> Besides ... Nothing good in life ever comes easily.
>
>> I was hoping you could shame them into helping if that's what it came down to 
>> it. I certainly don't have much luck because I don't know how to get them to 
>> help when they obviously don't really want to.
> I myself don't like shaming people. I believe that we should always be treating 
> others in the very same way that we wish they'd be treating us.
>