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

[Chris Brannon]

Post by Mark Peveto
Does this list support espeakup as well as standard speakup?

Yes it does.

-- Chris

[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

Post by Chris Brannon

Post by Mark Peveto
Does this list support espeakup as well as standard speakup?

Yes it does.
-- Chris
_______________________________________________
Speakup mailing list
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

[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.

[***@roxie ~]$ sudo espeakup
[sudo] password for 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.

[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

Post by 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.
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
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

[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

Post by 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

Post by 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.
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
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

_______________________________________________
Speakup mailing list
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

[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

Post by 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

Post by 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.
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
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

_______________________________________________
Speakup mailing list
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

[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.

Post by 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

Post by 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

Post by 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.
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
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

_______________________________________________
Speakup mailing list
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

_______________________________________________
Speakup mailing list
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

[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.

Date: Thu, 26 May 2016 15:11:00
Reply-To: Speakup is a screen review system for Linux.
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

Post by 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.
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
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

_______________________________________________
Speakup mailing list
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

--

[Mark Peveto]

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

Post by 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.

Date: Thu, 26 May 2016 15:11:00
Reply-To: Speakup is a screen review system for Linux.
To: Speakup is a screen review system for Linux.
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

Post by 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.
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
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

_______________________________________________
Speakup mailing list
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

[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.

Date: Fri, 27 May 2016 03:40:50
Reply-To: Speakup is a screen review system for Linux.
Subject: Re: espeakup
I've got the talking arch iso here, but when I tried to boot it from
usb, it never would speak.

Post by 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.

Date: Thu, 26 May 2016 15:11:00
Reply-To: Speakup is a screen review system for Linux.
To: Speakup is a screen review system for Linux.
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

Post by 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.
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
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

_______________________________________________
Speakup mailing list
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

--

[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

Post by 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.

Date: Thu, 26 May 2016 15:11:00
Reply-To: Speakup is a screen review system for Linux.
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

Post by 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.
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
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

_______________________________________________
Speakup mailing list
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

--
_______________________________________________
Speakup mailing list
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

[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

Post by 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.

Date: Thu, 26 May 2016 15:11:00
Reply-To: Speakup is a screen review system for Linux.
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

Post by 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.
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
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

_______________________________________________
Speakup mailing list
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

--
_______________________________________________
Speakup mailing list
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

[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" <***@gmail.com>
To: "Speakup is a screen review system for Linux."
<***@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

Post by 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.
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
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

_______________________________________________
Speakup mailing list
***@linux-speakup.org
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

[Rob]

Post by Glenn
I am wondering what eSpeakUp is.

Espeakup is the interface between speakup and espeak--the screen reader and
synth, respectively.

[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.

Post by 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

Post by 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.
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
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

_______________________________________________
Speakup mailing list
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

[Willem Venter]

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

Post by 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.

Post by 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

Post by 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.
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
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

_______________________________________________
Speakup mailing list
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

_______________________________________________
Speakup mailing list
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

[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

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

Post by 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.

Post by 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

Post by 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.
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
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

_______________________________________________
Speakup mailing list
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

_______________________________________________
Speakup mailing list
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

_______________________________________________
Speakup mailing list
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

[Jude DaShiell]

In your user directory, try something like: sudo -H rm -fr

Date: Fri, 27 May 2016 12:20:19
Reply-To: Speakup is a screen review system for Linux.
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

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

Post by 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.

Post by 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

Post by 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.
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
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

_______________________________________________
Speakup mailing list
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

_______________________________________________
Speakup mailing list
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

_______________________________________________
Speakup mailing list
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

_______________________________________________
Speakup mailing list
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

--