re: espeakup

re: espeakup

[Mark Peveto]

Here's the error I was talking about earlier.

Back story:  I'm trying to get console speech.  Since i can't right now, 
I'm doing this from a terminal, which reads badly. Once I type sudo 
espeakup, it'll read the top of the console screen, and the login prompt 
asking for a username.  After that it gives an error which i'll post.  I 
know it's a pulseaudio problem.  Most suggest I get rid of pulseaudio, 
and if that's the only solution there is, I guess i'll have to, but that 
creates more problems when it comes to having the system rediscover new 
sound drivers.  Long explanation short, it jacks things up!

Error follows.

[southernprince@roxie ~]$ sudo espeakup
[sudo] password for southernprince:
[southernprince@roxie ~]$ Assertion 'p' failed at pulse/simple.c:273, 
function pa_simple_write(). Aborting.

It should be noted here that the error does not appear until I start to 
type.  It reads the login prompt, and once i hit the s for 
southernprinc, my username, the error appears.  If I could figure out 
how, I might turn keyecho off, which I wanna do anyway, but I don't know 
if that'd help anything.

There ya have it folks.

Re: espeakup

[Willem Venter]

Hi.
Pulseaudio takes complete control of the audio device, so when other
devices try to use the soundcard through alsa things break.

A work around I use is playing sound using dmix. This means a bit more
processing and possibly a little latency for programs using pulse, but
on the other hand it's better than broken sound.

Remove package pulseaudio-alsa, which provides compatibility layer
between ALSA applications and PulseAudio. After this your ALSA apps
will use ALSA directly without being hooked by Pulse.
Edit /etc/pulse/default.pa.
Find and uncomment lines which load back-end drivers. Add device
parameters as follows. Then find and comment lines which load
autodetect modules.
load-module module-alsa-sink device=dmix
load-module module-alsa-source device=dsnoop
# load-module module-udev-detect
# load-module module-detect

After rebooting pulseaudio won't grab the sound device, but instead
plays it through dmix.

hth
Willem

On 5/26/16, Mark Peveto <southernprince73@gmail.com> wrote:
> Here's the error I was talking about earlier.
>
> Back story:  I'm trying to get console speech.  Since i can't right now,
> I'm doing this from a terminal, which reads badly. Once I type sudo
> espeakup, it'll read the top of the console screen, and the login prompt
> asking for a username.  After that it gives an error which i'll post.  I
> know it's a pulseaudio problem.  Most suggest I get rid of pulseaudio,
> and if that's the only solution there is, I guess i'll have to, but that
> creates more problems when it comes to having the system rediscover new
> sound drivers.  Long explanation short, it jacks things up!
>
> Error follows.
>
> [southernprince@roxie ~]$ sudo espeakup
> [sudo] password for southernprince:
> [southernprince@roxie ~]$ Assertion 'p' failed at pulse/simple.c:273,
> function pa_simple_write(). Aborting.
>
> It should be noted here that the error does not appear until I start to
> type.  It reads the login prompt, and once i hit the s for
> southernprinc, my username, the error appears.  If I could figure out
> how, I might turn keyecho off, which I wanna do anyway, but I don't know
> if that'd help anything.
>
> There ya have it folks.
>
> _______________________________________________
> Speakup mailing list
> Speakup@linux-speakup.org
> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
>

Re: espeakup

[Mark Peveto]

Well, it's sure worth a try.  I'll get started.

Mark Peveto
Registered Linux user number 600552
Sent from vinux using alpine 2.20.10


On Thu, 26 May 2016, Willem Venter wrote:

> Hi.
> Pulseaudio takes complete control of the audio device, so when other
> devices try to use the soundcard through alsa things break.
>
> A work around I use is playing sound using dmix. This means a bit more
> processing and possibly a little latency for programs using pulse, but
> on the other hand it's better than broken sound.
>
> Remove package pulseaudio-alsa, which provides compatibility layer
> between ALSA applications and PulseAudio. After this your ALSA apps
> will use ALSA directly without being hooked by Pulse.
> Edit /etc/pulse/default.pa.
> Find and uncomment lines which load back-end drivers. Add device
> parameters as follows. Then find and comment lines which load
> autodetect modules.
> load-module module-alsa-sink device=dmix
> load-module module-alsa-source device=dsnoop
> # load-module module-udev-detect
> # load-module module-detect
>
> After rebooting pulseaudio won't grab the sound device, but instead
> plays it through dmix.
>
> hth
> Willem
>
> On 5/26/16, Mark Peveto <southernprince73@gmail.com> wrote:
> > Here's the error I was talking about earlier.
> >
> > Back story:  I'm trying to get console speech.  Since i can't right now,
> > I'm doing this from a terminal, which reads badly. Once I type sudo
> > espeakup, it'll read the top of the console screen, and the login prompt
> > asking for a username.  After that it gives an error which i'll post.  I
> > know it's a pulseaudio problem.  Most suggest I get rid of pulseaudio,
> > and if that's the only solution there is, I guess i'll have to, but that
> > creates more problems when it comes to having the system rediscover new
> > sound drivers.  Long explanation short, it jacks things up!
> >
> > Error follows.
> >
> > [southernprince@roxie ~]$ sudo espeakup
> > [sudo] password for southernprince:
> > [southernprince@roxie ~]$ Assertion 'p' failed at pulse/simple.c:273,
> > function pa_simple_write(). Aborting.
> >
> > It should be noted here that the error does not appear until I start to
> > type.  It reads the login prompt, and once i hit the s for
> > southernprinc, my username, the error appears.  If I could figure out
> > how, I might turn keyecho off, which I wanna do anyway, but I don't know
> > if that'd help anything.
> >
> > There ya have it folks.
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@linux-speakup.org
> > http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
> >
> _______________________________________________
> Speakup mailing list
> Speakup@linux-speakup.org
> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
>

Re: espeakup

[Mark Peveto]

Well crud, tried it, and no sound or speech.  *sigh*
Thanks for the suggestion, though.

Mark Peveto
Registered Linux user number 600552
Sent from vinux using alpine 2.20.10


On Thu, 26 May 2016, Willem Venter wrote:

> Hi.
> Pulseaudio takes complete control of the audio device, so when other
> devices try to use the soundcard through alsa things break.
>
> A work around I use is playing sound using dmix. This means a bit more
> processing and possibly a little latency for programs using pulse, but
> on the other hand it's better than broken sound.
>
> Remove package pulseaudio-alsa, which provides compatibility layer
> between ALSA applications and PulseAudio. After this your ALSA apps
> will use ALSA directly without being hooked by Pulse.
> Edit /etc/pulse/default.pa.
> Find and uncomment lines which load back-end drivers. Add device
> parameters as follows. Then find and comment lines which load
> autodetect modules.
> load-module module-alsa-sink device=dmix
> load-module module-alsa-source device=dsnoop
> # load-module module-udev-detect
> # load-module module-detect
>
> After rebooting pulseaudio won't grab the sound device, but instead
> plays it through dmix.
>
> hth
> Willem
>
> On 5/26/16, Mark Peveto <southernprince73@gmail.com> wrote:
> > Here's the error I was talking about earlier.
> >
> > Back story:  I'm trying to get console speech.  Since i can't right now,
> > I'm doing this from a terminal, which reads badly. Once I type sudo
> > espeakup, it'll read the top of the console screen, and the login prompt
> > asking for a username.  After that it gives an error which i'll post.  I
> > know it's a pulseaudio problem.  Most suggest I get rid of pulseaudio,
> > and if that's the only solution there is, I guess i'll have to, but that
> > creates more problems when it comes to having the system rediscover new
> > sound drivers.  Long explanation short, it jacks things up!
> >
> > Error follows.
> >
> > [southernprince@roxie ~]$ sudo espeakup
> > [sudo] password for southernprince:
> > [southernprince@roxie ~]$ Assertion 'p' failed at pulse/simple.c:273,
> > function pa_simple_write(). Aborting.
> >
> > It should be noted here that the error does not appear until I start to
> > type.  It reads the login prompt, and once i hit the s for
> > southernprinc, my username, the error appears.  If I could figure out
> > how, I might turn keyecho off, which I wanna do anyway, but I don't know
> > if that'd help anything.
> >
> > There ya have it folks.
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@linux-speakup.org
> > http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
> >
> _______________________________________________
> Speakup mailing list
> Speakup@linux-speakup.org
> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
>

Re: espeakup

[Willem Venter]

Hi Mark.
I'm not sure why this did not work for you. My info comes from this page.
https://wiki.archlinux.org/index.php/PulseAudio
I have successfully used the dmix method on archlinux and also debian.

This specific method relies on pulseaudio to still be installed.
On 5/26/16, Mark Peveto <southernprince73@gmail.com> wrote:
> Well crud, tried it, and no sound or speech.  *sigh*
> Thanks for the suggestion, though.
>
> Mark Peveto
> Registered Linux user number 600552
> Sent from vinux using alpine 2.20.10
>
>
> On Thu, 26 May 2016, Willem Venter wrote:
>
>> Hi.
>> Pulseaudio takes complete control of the audio device, so when other
>> devices try to use the soundcard through alsa things break.
>>
>> A work around I use is playing sound using dmix. This means a bit more
>> processing and possibly a little latency for programs using pulse, but
>> on the other hand it's better than broken sound.
>>
>> Remove package pulseaudio-alsa, which provides compatibility layer
>> between ALSA applications and PulseAudio. After this your ALSA apps
>> will use ALSA directly without being hooked by Pulse.
>> Edit /etc/pulse/default.pa.
>> Find and uncomment lines which load back-end drivers. Add device
>> parameters as follows. Then find and comment lines which load
>> autodetect modules.
>> load-module module-alsa-sink device=dmix
>> load-module module-alsa-source device=dsnoop
>> # load-module module-udev-detect
>> # load-module module-detect
>>
>> After rebooting pulseaudio won't grab the sound device, but instead
>> plays it through dmix.
>>
>> hth
>> Willem
>>
>> On 5/26/16, Mark Peveto <southernprince73@gmail.com> wrote:
>> > Here's the error I was talking about earlier.
>> >
>> > Back story:  I'm trying to get console speech.  Since i can't right now,
>> > I'm doing this from a terminal, which reads badly. Once I type sudo
>> > espeakup, it'll read the top of the console screen, and the login prompt
>> > asking for a username.  After that it gives an error which i'll post.  I
>> > know it's a pulseaudio problem.  Most suggest I get rid of pulseaudio,
>> > and if that's the only solution there is, I guess i'll have to, but that
>> > creates more problems when it comes to having the system rediscover new
>> > sound drivers.  Long explanation short, it jacks things up!
>> >
>> > Error follows.
>> >
>> > [southernprince@roxie ~]$ sudo espeakup
>> > [sudo] password for southernprince:
>> > [southernprince@roxie ~]$ Assertion 'p' failed at pulse/simple.c:273,
>> > function pa_simple_write(). Aborting.
>> >
>> > It should be noted here that the error does not appear until I start to
>> > type.  It reads the login prompt, and once i hit the s for
>> > southernprinc, my username, the error appears.  If I could figure out
>> > how, I might turn keyecho off, which I wanna do anyway, but I don't know
>> > if that'd help anything.
>> >
>> > There ya have it folks.
>> >
>> > _______________________________________________
>> > Speakup mailing list
>> > Speakup@linux-speakup.org
>> > http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
>> >
>> _______________________________________________
>> Speakup mailing list
>> Speakup@linux-speakup.org
>> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
>>
> _______________________________________________
> Speakup mailing list
> Speakup@linux-speakup.org
> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
>

Re: espeakup

[Jude DaShiell]

Once pulseaudio is removed from a machine, running alsactl init should 
initialize all sound cards to default values.  The pulseaudio-alsa 
package has to be deliberately installed on talkingarchlinux at least I 
don't know what sonar or manjaro or f123 do.

On Thu, 26 May 2016, Willem Venter wrote:

> Date: Thu, 26 May 2016 15:11:00
> From: Willem Venter <dwillemv@gmail.com>
> Reply-To: Speakup is a screen review system for Linux.
>     <speakup@linux-speakup.org>
> To: Speakup is a screen review system for Linux. <speakup@linux-speakup.org>
> Subject: Re: espeakup
> 
> Hi.
> Pulseaudio takes complete control of the audio device, so when other
> devices try to use the soundcard through alsa things break.
>
> A work around I use is playing sound using dmix. This means a bit more
> processing and possibly a little latency for programs using pulse, but
> on the other hand it's better than broken sound.
>
> Remove package pulseaudio-alsa, which provides compatibility layer
> between ALSA applications and PulseAudio. After this your ALSA apps
> will use ALSA directly without being hooked by Pulse.
> Edit /etc/pulse/default.pa.
> Find and uncomment lines which load back-end drivers. Add device
> parameters as follows. Then find and comment lines which load
> autodetect modules.
> load-module module-alsa-sink device=dmix
> load-module module-alsa-source device=dsnoop
> # load-module module-udev-detect
> # load-module module-detect
>
> After rebooting pulseaudio won't grab the sound device, but instead
> plays it through dmix.
>
> hth
> Willem
>
> On 5/26/16, Mark Peveto <southernprince73@gmail.com> wrote:
>> Here's the error I was talking about earlier.
>>
>> Back story:  I'm trying to get console speech.  Since i can't right now,
>> I'm doing this from a terminal, which reads badly. Once I type sudo
>> espeakup, it'll read the top of the console screen, and the login prompt
>> asking for a username.  After that it gives an error which i'll post.  I
>> know it's a pulseaudio problem.  Most suggest I get rid of pulseaudio,
>> and if that's the only solution there is, I guess i'll have to, but that
>> creates more problems when it comes to having the system rediscover new
>> sound drivers.  Long explanation short, it jacks things up!
>>
>> Error follows.
>>
>> [southernprince@roxie ~]$ sudo espeakup
>> [sudo] password for southernprince:
>> [southernprince@roxie ~]$ Assertion 'p' failed at pulse/simple.c:273,
>> function pa_simple_write(). Aborting.
>>
>> It should be noted here that the error does not appear until I start to
>> type.  It reads the login prompt, and once i hit the s for
>> southernprinc, my username, the error appears.  If I could figure out
>> how, I might turn keyecho off, which I wanna do anyway, but I don't know
>> if that'd help anything.
>>
>> There ya have it folks.
>>
>> _______________________________________________
>> Speakup mailing list
>> Speakup@linux-speakup.org
>> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
>>
> _______________________________________________
> Speakup mailing list
> Speakup@linux-speakup.org
> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

-- 

Re: espeakup

[Mark Peveto]

I've got the talking arch iso here, but when I tried to boot it from 
usb, it never would speak.


On 05/26/2016 05:25 PM, Jude DaShiell wrote:
> Once pulseaudio is removed from a machine, running alsactl init should 
> initialize all sound cards to default values. The pulseaudio-alsa 
> package has to be deliberately installed on talkingarchlinux at least 
> I don't know what sonar or manjaro or f123 do.
>
> On Thu, 26 May 2016, Willem Venter wrote:
>
>> Date: Thu, 26 May 2016 15:11:00
>> From: Willem Venter <dwillemv@gmail.com>
>> Reply-To: Speakup is a screen review system for Linux.
>>     <speakup@linux-speakup.org>
>> To: Speakup is a screen review system for Linux. 
>> <speakup@linux-speakup.org>
>> Subject: Re: espeakup
>>
>> Hi.
>> Pulseaudio takes complete control of the audio device, so when other
>> devices try to use the soundcard through alsa things break.
>>
>> A work around I use is playing sound using dmix. This means a bit more
>> processing and possibly a little latency for programs using pulse, but
>> on the other hand it's better than broken sound.
>>
>> Remove package pulseaudio-alsa, which provides compatibility layer
>> between ALSA applications and PulseAudio. After this your ALSA apps
>> will use ALSA directly without being hooked by Pulse.
>> Edit /etc/pulse/default.pa.
>> Find and uncomment lines which load back-end drivers. Add device
>> parameters as follows. Then find and comment lines which load
>> autodetect modules.
>> load-module module-alsa-sink device=dmix
>> load-module module-alsa-source device=dsnoop
>> # load-module module-udev-detect
>> # load-module module-detect
>>
>> After rebooting pulseaudio won't grab the sound device, but instead
>> plays it through dmix.
>>
>> hth
>> Willem
>>
>> On 5/26/16, Mark Peveto <southernprince73@gmail.com> wrote:
>>> Here's the error I was talking about earlier.
>>>
>>> Back story:  I'm trying to get console speech.  Since i can't right 
>>> now,
>>> I'm doing this from a terminal, which reads badly. Once I type sudo
>>> espeakup, it'll read the top of the console screen, and the login 
>>> prompt
>>> asking for a username.  After that it gives an error which i'll 
>>> post.  I
>>> know it's a pulseaudio problem.  Most suggest I get rid of pulseaudio,
>>> and if that's the only solution there is, I guess i'll have to, but 
>>> that
>>> creates more problems when it comes to having the system rediscover new
>>> sound drivers.  Long explanation short, it jacks things up!
>>>
>>> Error follows.
>>>
>>> [southernprince@roxie ~]$ sudo espeakup
>>> [sudo] password for southernprince:
>>> [southernprince@roxie ~]$ Assertion 'p' failed at pulse/simple.c:273,
>>> function pa_simple_write(). Aborting.
>>>
>>> It should be noted here that the error does not appear until I start to
>>> type.  It reads the login prompt, and once i hit the s for
>>> southernprinc, my username, the error appears.  If I could figure out
>>> how, I might turn keyecho off, which I wanna do anyway, but I don't 
>>> know
>>> if that'd help anything.
>>>
>>> There ya have it folks.
>>>
>>> _______________________________________________
>>> Speakup mailing list
>>> Speakup@linux-speakup.org
>>> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
>>>
>> _______________________________________________
>> Speakup mailing list
>> Speakup@linux-speakup.org
>> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
>

-- 
Mark Peveto
Registered linux number 600552
Sent from sonar using thunderbird.

Re: espeakup

[Jude DaShiell]

You have to wait for that distro to start talking and I do mean wait a 
few minutes after you hit enter after booting the distro.  It is probing 
all of your sound cards, and even if you have usb speakers attached, 
talkingarch will find them and will offer you the opportunity to use 
them.  Hope this helps.

On Fri, 27 May 2016, Mark Peveto wrote:

> Date: Fri, 27 May 2016 03:40:50
> From: Mark Peveto <southernprince73@gmail.com>
> Reply-To: Speakup is a screen review system for Linux.
>     <speakup@linux-speakup.org>
> To: Speakup is a screen review system for Linux. <speakup@linux-speakup.org>
> Subject: Re: espeakup
> 
> I've got the talking arch iso here, but when I tried to boot it from 
> usb, it never would speak.
>
>
> On 05/26/2016 05:25 PM, Jude DaShiell wrote:
>> Once pulseaudio is removed from a machine, running alsactl init should 
>> initialize all sound cards to default values. The pulseaudio-alsa 
>> package has to be deliberately installed on talkingarchlinux at least 
>> I don't know what sonar or manjaro or f123 do.
>>
>> On Thu, 26 May 2016, Willem Venter wrote:
>>
>>> Date: Thu, 26 May 2016 15:11:00
>>> From: Willem Venter <dwillemv@gmail.com>
>>> Reply-To: Speakup is a screen review system for Linux.
>>>     <speakup@linux-speakup.org>
>>> To: Speakup is a screen review system for Linux. 
>>> <speakup@linux-speakup.org>
>>> Subject: Re: espeakup
>>>
>>> Hi.
>>> Pulseaudio takes complete control of the audio device, so when other
>>> devices try to use the soundcard through alsa things break.
>>>
>>> A work around I use is playing sound using dmix. This means a bit more
>>> processing and possibly a little latency for programs using pulse, but
>>> on the other hand it's better than broken sound.
>>>
>>> Remove package pulseaudio-alsa, which provides compatibility layer
>>> between ALSA applications and PulseAudio. After this your ALSA apps
>>> will use ALSA directly without being hooked by Pulse.
>>> Edit /etc/pulse/default.pa.
>>> Find and uncomment lines which load back-end drivers. Add device
>>> parameters as follows. Then find and comment lines which load
>>> autodetect modules.
>>> load-module module-alsa-sink device=dmix
>>> load-module module-alsa-source device=dsnoop
>>> # load-module module-udev-detect
>>> # load-module module-detect
>>>
>>> After rebooting pulseaudio won't grab the sound device, but instead
>>> plays it through dmix.
>>>
>>> hth
>>> Willem
>>>
>>> On 5/26/16, Mark Peveto <southernprince73@gmail.com> wrote:
>>>> Here's the error I was talking about earlier.
>>>>
>>>> Back story:  I'm trying to get console speech.  Since i can't right 
>>>> now,
>>>> I'm doing this from a terminal, which reads badly. Once I type sudo
>>>> espeakup, it'll read the top of the console screen, and the login 
>>>> prompt
>>>> asking for a username.  After that it gives an error which i'll 
>>>> post.  I
>>>> know it's a pulseaudio problem.  Most suggest I get rid of pulseaudio,
>>>> and if that's the only solution there is, I guess i'll have to, but 
>>>> that
>>>> creates more problems when it comes to having the system rediscover new
>>>> sound drivers.  Long explanation short, it jacks things up!
>>>>
>>>> Error follows.
>>>>
>>>> [southernprince@roxie ~]$ sudo espeakup
>>>> [sudo] password for southernprince:
>>>> [southernprince@roxie ~]$ Assertion 'p' failed at pulse/simple.c:273,
>>>> function pa_simple_write(). Aborting.
>>>>
>>>> It should be noted here that the error does not appear until I start to
>>>> type.  It reads the login prompt, and once i hit the s for
>>>> southernprinc, my username, the error appears.  If I could figure out
>>>> how, I might turn keyecho off, which I wanna do anyway, but I don't 
>>>> know
>>>> if that'd help anything.
>>>>
>>>> There ya have it folks.
>>>>
>>>> _______________________________________________
>>>> Speakup mailing list
>>>> Speakup@linux-speakup.org
>>>> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
>>>>
>>> _______________________________________________
>>> Speakup mailing list
>>> Speakup@linux-speakup.org
>>> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
>>
>
>

-- 

Re: espeakup

[Mark Peveto]

No problem.  I noticed the changes yesterday afternoon, so they're recent.

Mark Peveto
Registered Linux user number 600552
Sent from vinux using alpine 2.20.10


On Thu, 26 May 2016, Jude DaShiell wrote:

> Once pulseaudio is removed from a machine, running alsactl init should
> initialize all sound cards to default values.  The pulseaudio-alsa
> package has to be deliberately installed on talkingarchlinux at least I
> don't know what sonar or manjaro or f123 do.
>
> On Thu, 26 May 2016, Willem Venter wrote:
>
> > Date: Thu, 26 May 2016 15:11:00
> > From: Willem Venter <dwillemv@gmail.com>
> > Reply-To: Speakup is a screen review system for Linux.
> >     <speakup@linux-speakup.org>
> > To: Speakup is a screen review system for Linux. <speakup@linux-speakup.org>
> > Subject: Re: espeakup
> >
> > Hi.
> > Pulseaudio takes complete control of the audio device, so when other
> > devices try to use the soundcard through alsa things break.
> >
> > A work around I use is playing sound using dmix. This means a bit more
> > processing and possibly a little latency for programs using pulse, but
> > on the other hand it's better than broken sound.
> >
> > Remove package pulseaudio-alsa, which provides compatibility layer
> > between ALSA applications and PulseAudio. After this your ALSA apps
> > will use ALSA directly without being hooked by Pulse.
> > Edit /etc/pulse/default.pa.
> > Find and uncomment lines which load back-end drivers. Add device
> > parameters as follows. Then find and comment lines which load
> > autodetect modules.
> > load-module module-alsa-sink device=dmix
> > load-module module-alsa-source device=dsnoop
> > # load-module module-udev-detect
> > # load-module module-detect
> >
> > After rebooting pulseaudio won't grab the sound device, but instead
> > plays it through dmix.
> >
> > hth
> > Willem
> >
> > On 5/26/16, Mark Peveto <southernprince73@gmail.com> wrote:
> >> Here's the error I was talking about earlier.
> >>
> >> Back story:  I'm trying to get console speech.  Since i can't right now,
> >> I'm doing this from a terminal, which reads badly. Once I type sudo
> >> espeakup, it'll read the top of the console screen, and the login prompt
> >> asking for a username.  After that it gives an error which i'll post.  I
> >> know it's a pulseaudio problem.  Most suggest I get rid of pulseaudio,
> >> and if that's the only solution there is, I guess i'll have to, but that
> >> creates more problems when it comes to having the system rediscover new
> >> sound drivers.  Long explanation short, it jacks things up!
> >>
> >> Error follows.
> >>
> >> [southernprince@roxie ~]$ sudo espeakup
> >> [sudo] password for southernprince:
> >> [southernprince@roxie ~]$ Assertion 'p' failed at pulse/simple.c:273,
> >> function pa_simple_write(). Aborting.
> >>
> >> It should be noted here that the error does not appear until I start to
> >> type.  It reads the login prompt, and once i hit the s for
> >> southernprinc, my username, the error appears.  If I could figure out
> >> how, I might turn keyecho off, which I wanna do anyway, but I don't know
> >> if that'd help anything.
> >>
> >> There ya have it folks.
> >>
> >> _______________________________________________
> >> Speakup mailing list
> >> Speakup@linux-speakup.org
> >> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
> >>
> > _______________________________________________
> > Speakup mailing list
> > Speakup@linux-speakup.org
> > http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
>
> --
>
> _______________________________________________
> Speakup mailing list
> Speakup@linux-speakup.org
> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
>

Re: espeakup

[Mark Peveto]

Hmm, sorry about that, folks.  I was replying to another message that had deleted before I could hit reply, and so my reply got sent to the wrong list.
*sigh*  I should go back to bed.

Mark Peveto
Registered Linux user number 600552
Sent from vinux using alpine 2.20.10


On Thu, 26 May 2016, Jude DaShiell wrote:

> Once pulseaudio is removed from a machine, running alsactl init should
> initialize all sound cards to default values.  The pulseaudio-alsa
> package has to be deliberately installed on talkingarchlinux at least I
> don't know what sonar or manjaro or f123 do.
>
> On Thu, 26 May 2016, Willem Venter wrote:
>
> > Date: Thu, 26 May 2016 15:11:00
> > From: Willem Venter <dwillemv@gmail.com>
> > Reply-To: Speakup is a screen review system for Linux.
> >     <speakup@linux-speakup.org>
> > To: Speakup is a screen review system for Linux. <speakup@linux-speakup.org>
> > Subject: Re: espeakup
> >
> > Hi.
> > Pulseaudio takes complete control of the audio device, so when other
> > devices try to use the soundcard through alsa things break.
> >
> > A work around I use is playing sound using dmix. This means a bit more
> > processing and possibly a little latency for programs using pulse, but
> > on the other hand it's better than broken sound.
> >
> > Remove package pulseaudio-alsa, which provides compatibility layer
> > between ALSA applications and PulseAudio. After this your ALSA apps
> > will use ALSA directly without being hooked by Pulse.
> > Edit /etc/pulse/default.pa.
> > Find and uncomment lines which load back-end drivers. Add device
> > parameters as follows. Then find and comment lines which load
> > autodetect modules.
> > load-module module-alsa-sink device=dmix
> > load-module module-alsa-source device=dsnoop
> > # load-module module-udev-detect
> > # load-module module-detect
> >
> > After rebooting pulseaudio won't grab the sound device, but instead
> > plays it through dmix.
> >
> > hth
> > Willem
> >
> > On 5/26/16, Mark Peveto <southernprince73@gmail.com> wrote:
> >> Here's the error I was talking about earlier.
> >>
> >> Back story:  I'm trying to get console speech.  Since i can't right now,
> >> I'm doing this from a terminal, which reads badly. Once I type sudo
> >> espeakup, it'll read the top of the console screen, and the login prompt
> >> asking for a username.  After that it gives an error which i'll post.  I
> >> know it's a pulseaudio problem.  Most suggest I get rid of pulseaudio,
> >> and if that's the only solution there is, I guess i'll have to, but that
> >> creates more problems when it comes to having the system rediscover new
> >> sound drivers.  Long explanation short, it jacks things up!
> >>
> >> Error follows.
> >>
> >> [southernprince@roxie ~]$ sudo espeakup
> >> [sudo] password for southernprince:
> >> [southernprince@roxie ~]$ Assertion 'p' failed at pulse/simple.c:273,
> >> function pa_simple_write(). Aborting.
> >>
> >> It should be noted here that the error does not appear until I start to
> >> type.  It reads the login prompt, and once i hit the s for
> >> southernprinc, my username, the error appears.  If I could figure out
> >> how, I might turn keyecho off, which I wanna do anyway, but I don't know
> >> if that'd help anything.
> >>
> >> There ya have it folks.
> >>
> >> _______________________________________________
> >> Speakup mailing list
> >> Speakup@linux-speakup.org
> >> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
> >>
> > _______________________________________________
> > Speakup mailing list
> > Speakup@linux-speakup.org
> > http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
>
> --
>
> _______________________________________________
> Speakup mailing list
> Speakup@linux-speakup.org
> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
>

Re: espeakup

[Glenn]

I am wondering what eSpeakUp is.
I may be clueless here, but I thought that SpeakUp was the screenreader, and 
eSpeak was the synth?
Thanks for any clarification.
Glenn
----- Original Message ----- 
From: "Willem Venter" <dwillemv@gmail.com>
To: "Speakup is a screen review system for Linux." 
<speakup@linux-speakup.org>
Sent: Thursday, May 26, 2016 2:11 PM
Subject: Re: espeakup


Hi.
Pulseaudio takes complete control of the audio device, so when other
devices try to use the soundcard through alsa things break.

A work around I use is playing sound using dmix. This means a bit more
processing and possibly a little latency for programs using pulse, but
on the other hand it's better than broken sound.

Remove package pulseaudio-alsa, which provides compatibility layer
between ALSA applications and PulseAudio. After this your ALSA apps
will use ALSA directly without being hooked by Pulse.
Edit /etc/pulse/default.pa.
Find and uncomment lines which load back-end drivers. Add device
parameters as follows. Then find and comment lines which load
autodetect modules.
load-module module-alsa-sink device=dmix
load-module module-alsa-source device=dsnoop
# load-module module-udev-detect
# load-module module-detect

After rebooting pulseaudio won't grab the sound device, but instead
plays it through dmix.

hth
Willem

On 5/26/16, Mark Peveto <southernprince73@gmail.com> wrote:
> Here's the error I was talking about earlier.
>
> Back story:  I'm trying to get console speech.  Since i can't right now,
> I'm doing this from a terminal, which reads badly. Once I type sudo
> espeakup, it'll read the top of the console screen, and the login prompt
> asking for a username.  After that it gives an error which i'll post.  I
> know it's a pulseaudio problem.  Most suggest I get rid of pulseaudio,
> and if that's the only solution there is, I guess i'll have to, but that
> creates more problems when it comes to having the system rediscover new
> sound drivers.  Long explanation short, it jacks things up!
>
> Error follows.
>
> [southernprince@roxie ~]$ sudo espeakup
> [sudo] password for southernprince:
> [southernprince@roxie ~]$ Assertion 'p' failed at pulse/simple.c:273,
> function pa_simple_write(). Aborting.
>
> It should be noted here that the error does not appear until I start to
> type.  It reads the login prompt, and once i hit the s for
> southernprinc, my username, the error appears.  If I could figure out
> how, I might turn keyecho off, which I wanna do anyway, but I don't know
> if that'd help anything.
>
> There ya have it folks.
>
> _______________________________________________
> Speakup mailing list
> Speakup@linux-speakup.org
> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
>
_______________________________________________
Speakup mailing list
Speakup@linux-speakup.org
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

Re: espeakup

[Rob]

Glenn <glennervin@cableone.net> wrote:
>I am wondering what eSpeakUp is.
Espeakup is the interface between speakup and espeak--the screen reader and 
synth, respectively. 

Re: espeakup

[Mark Peveto]

Oh, I'm sure it's good information, friend, I'm just not having much 
luck.  Think tha'ts more on my end.  I'm not as good at this as I should be.

Mark Peveto
Registered linux number 600552
Sent from sonar using thunderbird.

On 05/26/2016 02:11 PM, Willem Venter wrote:
> Hi.
> Pulseaudio takes complete control of the audio device, so when other
> devices try to use the soundcard through alsa things break.
>
> A work around I use is playing sound using dmix. This means a bit more
> processing and possibly a little latency for programs using pulse, but
> on the other hand it's better than broken sound.
>
> Remove package pulseaudio-alsa, which provides compatibility layer
> between ALSA applications and PulseAudio. After this your ALSA apps
> will use ALSA directly without being hooked by Pulse.
> Edit /etc/pulse/default.pa.
> Find and uncomment lines which load back-end drivers. Add device
> parameters as follows. Then find and comment lines which load
> autodetect modules.
> load-module module-alsa-sink device=dmix
> load-module module-alsa-source device=dsnoop
> # load-module module-udev-detect
> # load-module module-detect
>
> After rebooting pulseaudio won't grab the sound device, but instead
> plays it through dmix.
>
> hth
> Willem
>
> On 5/26/16, Mark Peveto <southernprince73@gmail.com> wrote:
>> Here's the error I was talking about earlier.
>>
>> Back story:  I'm trying to get console speech.  Since i can't right now,
>> I'm doing this from a terminal, which reads badly. Once I type sudo
>> espeakup, it'll read the top of the console screen, and the login prompt
>> asking for a username.  After that it gives an error which i'll post.  I
>> know it's a pulseaudio problem.  Most suggest I get rid of pulseaudio,
>> and if that's the only solution there is, I guess i'll have to, but that
>> creates more problems when it comes to having the system rediscover new
>> sound drivers.  Long explanation short, it jacks things up!
>>
>> Error follows.
>>
>> [southernprince@roxie ~]$ sudo espeakup
>> [sudo] password for southernprince:
>> [southernprince@roxie ~]$ Assertion 'p' failed at pulse/simple.c:273,
>> function pa_simple_write(). Aborting.
>>
>> It should be noted here that the error does not appear until I start to
>> type.  It reads the login prompt, and once i hit the s for
>> southernprinc, my username, the error appears.  If I could figure out
>> how, I might turn keyecho off, which I wanna do anyway, but I don't know
>> if that'd help anything.
>>
>> There ya have it folks.
>>
>> _______________________________________________
>> Speakup mailing list
>> Speakup@linux-speakup.org
>> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
>>
> _______________________________________________
> Speakup mailing list
> Speakup@linux-speakup.org
> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

Re: espeakup

[Willem Venter]

Can you get access to the files on the disk? You might try deleting
some of the user pulseaudio configs.

On 5/27/16, Mark Peveto <southernprince73@gmail.com> wrote:
> Oh, I'm sure it's good information, friend, I'm just not having much
> luck.  Think tha'ts more on my end.  I'm not as good at this as I should be.
>
> Mark Peveto
> Registered linux number 600552
> Sent from sonar using thunderbird.
>
> On 05/26/2016 02:11 PM, Willem Venter wrote:
>> Hi.
>> Pulseaudio takes complete control of the audio device, so when other
>> devices try to use the soundcard through alsa things break.
>>
>> A work around I use is playing sound using dmix. This means a bit more
>> processing and possibly a little latency for programs using pulse, but
>> on the other hand it's better than broken sound.
>>
>> Remove package pulseaudio-alsa, which provides compatibility layer
>> between ALSA applications and PulseAudio. After this your ALSA apps
>> will use ALSA directly without being hooked by Pulse.
>> Edit /etc/pulse/default.pa.
>> Find and uncomment lines which load back-end drivers. Add device
>> parameters as follows. Then find and comment lines which load
>> autodetect modules.
>> load-module module-alsa-sink device=dmix
>> load-module module-alsa-source device=dsnoop
>> # load-module module-udev-detect
>> # load-module module-detect
>>
>> After rebooting pulseaudio won't grab the sound device, but instead
>> plays it through dmix.
>>
>> hth
>> Willem
>>
>> On 5/26/16, Mark Peveto <southernprince73@gmail.com> wrote:
>>> Here's the error I was talking about earlier.
>>>
>>> Back story:  I'm trying to get console speech.  Since i can't right now,
>>> I'm doing this from a terminal, which reads badly. Once I type sudo
>>> espeakup, it'll read the top of the console screen, and the login prompt
>>> asking for a username.  After that it gives an error which i'll post.  I
>>> know it's a pulseaudio problem.  Most suggest I get rid of pulseaudio,
>>> and if that's the only solution there is, I guess i'll have to, but that
>>> creates more problems when it comes to having the system rediscover new
>>> sound drivers.  Long explanation short, it jacks things up!
>>>
>>> Error follows.
>>>
>>> [southernprince@roxie ~]$ sudo espeakup
>>> [sudo] password for southernprince:
>>> [southernprince@roxie ~]$ Assertion 'p' failed at pulse/simple.c:273,
>>> function pa_simple_write(). Aborting.
>>>
>>> It should be noted here that the error does not appear until I start to
>>> type.  It reads the login prompt, and once i hit the s for
>>> southernprinc, my username, the error appears.  If I could figure out
>>> how, I might turn keyecho off, which I wanna do anyway, but I don't know
>>> if that'd help anything.
>>>
>>> There ya have it folks.
>>>
>>> _______________________________________________
>>> Speakup mailing list
>>> Speakup@linux-speakup.org
>>> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
>>>
>> _______________________________________________
>> Speakup mailing list
>> Speakup@linux-speakup.org
>> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
>
> _______________________________________________
> Speakup mailing list
> Speakup@linux-speakup.org
> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
>

Re: espeakup

[Mark Peveto]

What file names do I look for?  I did a fresh install yesterday afternoon, so yeah, I could try.

Mark Peveto
Registered Linux user number 600552
Sent from vinux using alpine 2.20.10


On Fri, 27 May 2016, Willem Venter wrote:

> Can you get access to the files on the disk? You might try deleting
> some of the user pulseaudio configs.
>
> On 5/27/16, Mark Peveto <southernprince73@gmail.com> wrote:
> > Oh, I'm sure it's good information, friend, I'm just not having much
> > luck.  Think tha'ts more on my end.  I'm not as good at this as I should be.
> >
> > Mark Peveto
> > Registered linux number 600552
> > Sent from sonar using thunderbird.
> >
> > On 05/26/2016 02:11 PM, Willem Venter wrote:
> >> Hi.
> >> Pulseaudio takes complete control of the audio device, so when other
> >> devices try to use the soundcard through alsa things break.
> >>
> >> A work around I use is playing sound using dmix. This means a bit more
> >> processing and possibly a little latency for programs using pulse, but
> >> on the other hand it's better than broken sound.
> >>
> >> Remove package pulseaudio-alsa, which provides compatibility layer
> >> between ALSA applications and PulseAudio. After this your ALSA apps
> >> will use ALSA directly without being hooked by Pulse.
> >> Edit /etc/pulse/default.pa.
> >> Find and uncomment lines which load back-end drivers. Add device
> >> parameters as follows. Then find and comment lines which load
> >> autodetect modules.
> >> load-module module-alsa-sink device=dmix
> >> load-module module-alsa-source device=dsnoop
> >> # load-module module-udev-detect
> >> # load-module module-detect
> >>
> >> After rebooting pulseaudio won't grab the sound device, but instead
> >> plays it through dmix.
> >>
> >> hth
> >> Willem
> >>
> >> On 5/26/16, Mark Peveto <southernprince73@gmail.com> wrote:
> >>> Here's the error I was talking about earlier.
> >>>
> >>> Back story:  I'm trying to get console speech.  Since i can't right now,
> >>> I'm doing this from a terminal, which reads badly. Once I type sudo
> >>> espeakup, it'll read the top of the console screen, and the login prompt
> >>> asking for a username.  After that it gives an error which i'll post.  I
> >>> know it's a pulseaudio problem.  Most suggest I get rid of pulseaudio,
> >>> and if that's the only solution there is, I guess i'll have to, but that
> >>> creates more problems when it comes to having the system rediscover new
> >>> sound drivers.  Long explanation short, it jacks things up!
> >>>
> >>> Error follows.
> >>>
> >>> [southernprince@roxie ~]$ sudo espeakup
> >>> [sudo] password for southernprince:
> >>> [southernprince@roxie ~]$ Assertion 'p' failed at pulse/simple.c:273,
> >>> function pa_simple_write(). Aborting.
> >>>
> >>> It should be noted here that the error does not appear until I start to
> >>> type.  It reads the login prompt, and once i hit the s for
> >>> southernprinc, my username, the error appears.  If I could figure out
> >>> how, I might turn keyecho off, which I wanna do anyway, but I don't know
> >>> if that'd help anything.
> >>>
> >>> There ya have it folks.
> >>>
> >>> _______________________________________________
> >>> Speakup mailing list
> >>> Speakup@linux-speakup.org
> >>> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
> >>>
> >> _______________________________________________
> >> Speakup mailing list
> >> Speakup@linux-speakup.org
> >> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@linux-speakup.org
> > http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
> >
> _______________________________________________
> Speakup mailing list
> Speakup@linux-speakup.org
> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
>

Re: espeakup

[Jude DaShiell]

In your user directory, try something like: sudo -H rm -fr 
./.config/pulseaudio <enter>. On Fri, 27 May 2016, Mark Peveto wrote:

> Date: Fri, 27 May 2016 12:20:19
> From: Mark Peveto <southernprince73@gmail.com>
> Reply-To: Speakup is a screen review system for Linux.
>     <speakup@linux-speakup.org>
> To: Speakup is a screen review system for Linux. <speakup@linux-speakup.org>
> Subject: Re: espeakup
> 
> What file names do I look for?  I did a fresh install yesterday afternoon, so yeah, I could try.
>
> Mark Peveto
> Registered Linux user number 600552
> Sent from vinux using alpine 2.20.10
>
>
> On Fri, 27 May 2016, Willem Venter wrote:
>
>> Can you get access to the files on the disk? You might try deleting
>> some of the user pulseaudio configs.
>>
>> On 5/27/16, Mark Peveto <southernprince73@gmail.com> wrote:
>> > Oh, I'm sure it's good information, friend, I'm just not having much
>> > luck.  Think tha'ts more on my end.  I'm not as good at this as I should be.
>> >
>> > Mark Peveto
>> > Registered linux number 600552
>> > Sent from sonar using thunderbird.
>> >
>> > On 05/26/2016 02:11 PM, Willem Venter wrote:
>> >> Hi.
>> >> Pulseaudio takes complete control of the audio device, so when other
>> >> devices try to use the soundcard through alsa things break.
>> >>
>> >> A work around I use is playing sound using dmix. This means a bit more
>> >> processing and possibly a little latency for programs using pulse, but
>> >> on the other hand it's better than broken sound.
>> >>
>> >> Remove package pulseaudio-alsa, which provides compatibility layer
>> >> between ALSA applications and PulseAudio. After this your ALSA apps
>> >> will use ALSA directly without being hooked by Pulse.
>> >> Edit /etc/pulse/default.pa.
>> >> Find and uncomment lines which load back-end drivers. Add device
>> >> parameters as follows. Then find and comment lines which load
>> >> autodetect modules.
>> >> load-module module-alsa-sink device=dmix
>> >> load-module module-alsa-source device=dsnoop
>> >> # load-module module-udev-detect
>> >> # load-module module-detect
>> >>
>> >> After rebooting pulseaudio won't grab the sound device, but instead
>> >> plays it through dmix.
>> >>
>> >> hth
>> >> Willem
>> >>
>> >> On 5/26/16, Mark Peveto <southernprince73@gmail.com> wrote:
>> >>> Here's the error I was talking about earlier.
>> >>>
>> >>> Back story:  I'm trying to get console speech.  Since i can't right now,
>> >>> I'm doing this from a terminal, which reads badly. Once I type sudo
>> >>> espeakup, it'll read the top of the console screen, and the login prompt
>> >>> asking for a username.  After that it gives an error which i'll post.  I
>> >>> know it's a pulseaudio problem.  Most suggest I get rid of pulseaudio,
>> >>> and if that's the only solution there is, I guess i'll have to, but that
>> >>> creates more problems when it comes to having the system rediscover new
>> >>> sound drivers.  Long explanation short, it jacks things up!
>> >>>
>> >>> Error follows.
>> >>>
>> >>> [southernprince@roxie ~]$ sudo espeakup
>> >>> [sudo] password for southernprince:
>> >>> [southernprince@roxie ~]$ Assertion 'p' failed at pulse/simple.c:273,
>> >>> function pa_simple_write(). Aborting.
>> >>>
>> >>> It should be noted here that the error does not appear until I start to
>> >>> type.  It reads the login prompt, and once i hit the s for
>> >>> southernprinc, my username, the error appears.  If I could figure out
>> >>> how, I might turn keyecho off, which I wanna do anyway, but I don't know
>> >>> if that'd help anything.
>> >>>
>> >>> There ya have it folks.
>> >>>
>> >>> _______________________________________________
>> >>> Speakup mailing list
>> >>> Speakup@linux-speakup.org
>> >>> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
>> >>>
>> >> _______________________________________________
>> >> Speakup mailing list
>> >> Speakup@linux-speakup.org
>> >> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
>> >
>> > _______________________________________________
>> > Speakup mailing list
>> > Speakup@linux-speakup.org
>> > http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
>> >
>> _______________________________________________
>> Speakup mailing list
>> Speakup@linux-speakup.org
>> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
>>
> _______________________________________________
> Speakup mailing list
> Speakup@linux-speakup.org
> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

-- 

espeakup

[Mark Peveto]

Does this list support espeakup as well as standard speakup?

Mark Peveto
Registered Linux user number 600552
Sent from vinux using alpine 2.20.10

Re: espeakup

[Chris Brannon]

Mark Peveto <southernprince73@gmail.com> writes:

> Does this list support espeakup as well as standard speakup?

Yes it does.

-- Chris

Re: espeakup

[Mark Peveto]

I'm trying to run espeakup on a manjaro based system.  It and pulseaudio aren't getting along.  As soon as i can recreate the error, I'll send the exact
text.  Many suggest getting rid of pulseaudio, but when I try that it blows my sound all to heck.  I'll write again with the exact error text.

Mark Peveto
Registered Linux user number 600552
Sent from vinux using alpine 2.20.10


On Thu, 26 May 2016, Chris Brannon wrote:

> Mark Peveto <southernprince73@gmail.com> writes:
>
> > Does this list support espeakup as well as standard speakup?
>
> Yes it does.
>
> -- Chris
> _______________________________________________
> Speakup mailing list
> Speakup@linux-speakup.org
> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
>

espeakup

[Techswing33]

Hello,

I'm looking for espeakup. I'm wanting source so I can compile it
trying to get a distro talking.

Thanks.
Dave.

Re: espeakup

[Gregory Nowak]

A web search for espeakup comes back with:

https://github.com/williamh/espeakup/

Greg


On Mon, Jan 18, 2016 at 08:22:31PM -0500, Techswing33 wrote:
> Hello,
> 
> I'm looking for espeakup. I'm wanting source so I can compile it
> trying to get a distro talking.
> 
> Thanks.
> Dave.
> _______________________________________________
> Speakup mailing list
> Speakup@linux-speakup.org
> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

-- 
web site: http://www.gregn.net
gpg public key: http://www.gregn.net/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)
If we haven't been in touch before, e-mail me before adding me to your contacts.

--
Free domains: http://www.eu.org/ or mail dns-manager@EU.org

Re: espeakup

[Janina Sajka]

Try:

ftp://ftp.speakupmodified.org/speakupmodified/fedora/espeakup/

I don't think Bill ever updated the src available there.

Janina

Techswing33 writes:
> Hello,
> 
> I'm looking for espeakup. I'm wanting source so I can compile it
> trying to get a distro talking.
> 
> Thanks.
> Dave.
> _______________________________________________
> Speakup mailing list
> Speakup@linux-speakup.org
> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

-- 

Janina Sajka,	Phone:	+1.443.300.2200
			sip:janina@asterisk.rednote.net
		Email:	janina@rednote.net

Linux Foundation Fellow
Executive Chair, Accessibility Workgroup:	http://a11y.org

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Chair, Accessible Platform Architectures	http://www.w3.org/wai/apa

Espeakup

[Cheryl Homiak]

Well, since I couldn't resolve the issues with using my doubletalk lt at 
boot for the time being, I decided to try espeakup. This was so easy!!! 
All I did was install espeakup, add speakup_soft start=1 to /etc/modules 
and reboot. Very nice!!! I'm also using espeak with orca and so far I'm 
extremely happy with it. In fact, when I logged in to gnome and orca 
started automatically and speech began, speakup, which was still reading 
some of the boot information, didn't even miss a beat and it stopped 
reading bootup information and began reading what I was typing immediately 
when I switched to a text console and started typing. It also doesn't show 
any kind of conflicts so far when using it along with brltty. It's true 
that it doesn't start speaking as early as would a hardware synth working 
from the kernel or initrd but it is working very impressively so far for 
me!!!





-- 
Cheryl

"Where your treasure is, there will your heart be also."