On Tue, 17 Nov 2015, Steve Holmes wrote:
Date: Tue, 17 Nov 2015 14:02:58 From: Steve Holmes <steve@xxxxxxxxxxx> To: Christopher Chaltain <chaltain@xxxxxxxxxxx> Cc: Tim Cross <theophilusx@xxxxxxxxxxx>, Jude DaShiell <jdashiel@xxxxxxxxxxx>, emacspeak <emacspeak@xxxxxxxxxxx> Subject: Re: different test results Sorry, that won't fly here. I want spoken prompts at the login screens for each virtual console. I only run X when I start up gnome with the startx command from a native console. I do not boot my system into GNOME directly. I use the console environment for most of my activity and run GNOME when I need services from there like Firefox, etc. I suppose one could run speakup this way if they booted into X directly. I think the problem we have here is when espeakup and speakup are running system wide from the console environment, Pulseaudio squashes things when it starts up when you run GNOME and pulse is started up for that user session. for speech dispatcher. I think this is why all the contention about pulse and conflicts that so often arise. On Mon, Nov 16, 2015 at 6:53 PM, Christopher Chaltain <chaltain@xxxxxxxxxxx> wrote:I use Speakup with PulseAudio all of the time. I'm using it on vinux 4, but I know there's a work around to use this combination on other distros. For example, here's a post to a Linux accessibility list: It isn't necessary to use systemwide Pulse audio anymore. I use console speech on my Ubuntu box at home which has Pulse Audio installed and configured in the recommended way (not systemwide) and I am able to use Speakup just fine. The trick is to start it from a Gnome Terminal within X: sudo modprobe speakupg_soft start=1 sudo espeakup Just my thoughts, Alex M On 11/16/2015 04:58 PM, Steve Holmes wrote:Well, for me, I use speakup almost all the time on my Linux box. I am not willing to give that up so that pulse audio can be used. I probably use speakup over 80 percent of the time I run Linux. On Mon, Nov 16, 2015 at 2:51 PM, Tim Cross <theophilusx@xxxxxxxxxxx <mailto:theophilusx@xxxxxxxxxxx>> wrote: I?ve never used speakup. I do use speech dispatcher and it works fine with pulseaudio. regards, Tim ? Tim Cross On 17 Nov 2015, at 9:13 AM, Steve Holmes <steve@xxxxxxxxxxx<mailto:steve@xxxxxxxxxxx>> wrote: I think some of the problems with PulseAudio stem from when we try and use Speakup with espeakup. speakup and espeakup run as a central service (I should say espeakup is a central service) where PulseAudio runs as individual user sessions. I want to be able to use speakup at all login prompts and I don't believe this is possible with pulse. Now if I'm wrong about some of this, I would be glad to hear some corective measures. Last thing I want is the inability to use speakup. So I for one has resisted the use of pulse for years. At present, I have to keep pulseaudio binary marked as non-executable so as not to cause the emacspeak espeak module from going silent. If pulseaudio would indeed work while I use speakup, then I could have speech dispatcher run with pulse and hopefully then I could take advantage of full sound support in gnome. So I would be interested if pulse could really be all that trusted. On Mon, Nov 16, 2015 at 1:10 PM, Tim Cross <theophilusx@xxxxxxxxxxx <mailto:theophilusx@xxxxxxxxxxx>> wrote: If your using espeak witch has been compiled to use portAudio rather than native pulseaudio, you will get much better performance/reliability if you re-compile it to use pulseaudio. This involves changing one define in the source and then recompiling. Much much simpler than trying to remove pulseaudio. Not sure why distros still ship espeak with portaudio rather than pulseaudio as the default. Use to make sense when pulseaudio was still a little immature, but these days, it doesn't make a lot of sense. On 17 November 2015 at 01:37, Jude DaShiell <jdashiel@xxxxxxxxxxx <mailto:jdashiel@xxxxxxxxxxx>> wrote: espeak compiled to use portaudio which is distributed in the talkingarch distribution. On Mon, 16 Nov 2015, Christopher Chaltain wrote: Date: Mon, 16 Nov 2015 07:31:39 From: Christopher Chaltain <chaltain@xxxxxxxxxxx <mailto:chaltain@xxxxxxxxxxx>> To: emacspeak <emacspeak@xxxxxxxxxxx <mailto:emacspeak@xxxxxxxxxxx>> Subject: Re: different test results Resent-Date: Mon, 16 Nov 2015 07:31:41 -0500 (EST) Resent-From: emacspeak@xxxxxxxxxxx <mailto:emacspeak@xxxxxxxxxxx> What synthesizer are you talking about and what distribution? I've never noticed an issue with Emacspeak and PulseAudio except when using eSpeak compiled to use PortAudio. Once I recompile eSpeak to use the runtime or PulseAudio options, everything is fine. On 11/16/2015 05:53 AM, Jude DaShiell wrote: emacspeak post-install slows speech rate when running, so I'm not certain pulseaudio is playing all that well with emacspeak. On Mon, 16 Nov 2015, Tim Cross wrote: Date: Sun, 15 Nov 2015 16:17:55 From: Tim Cross <theophilusx@xxxxxxxxxxx <mailto:theophilusx@xxxxxxxxxxx>> To: Jude DaShiell <jdashiel@xxxxxxxxxxx <mailto:jdashiel@xxxxxxxxxxx>> Cc: emacspeak <emacspeak@xxxxxxxxxxx <mailto:emacspeak@xxxxxxxxxxx>> Subject: Re: different test results My question would be why get rid of pulseaudio? Early versions of pulseaudio had performance issues, but that was a long tiime ago. I've been using pulseaudio on multiple systems with both Outloud viavoice and espeak without a problem (though last time I used espeak, I did re-build it and ensure the native pulseaudio support was enabled. Not sure if that is still necessary). On some systems, such as those where I use Outloud ViaVoice, I have to install 32 bit as well as 64 bit libs and it all works flawlessly. Pulseaudio is now the default sound layer on Linux systems and it would be better to embrace it rather than fight against it. It means you no longer need to have custom asoundrc files, have an easy way to set different volume and other characteristics for different sound sources etc. I have tried the remoal of pulseaudio and it can be one, but it is a lot of effort and will 'sneak' back when you decide to install a new program which has any sound support because pulseaudio is often the default config. If you have pulseaudio issues, I would strongly recommend tracking those down and fixing them rather than attempting to remove pulse. While I did need to do some tweaking with older verisons, I've found all the distros I've tried have resolved those issues now and have not needed to do any tweaking of the pulse setup for at least 2+ years. On 15 November 2015 at 23:07, Jude DaShiell <jdashiel@xxxxxxxxxxx <mailto:jdashiel@xxxxxxxxxxx>> wrote: To do this right, I need to learn how to do three things. 1) remove pulseaudio from an existing archlinux system, 2) prevent pulseaudio from installing on pre-existing archlinux system in future, 3) find out how to install an archlinux system without pulseaudio and keep it off newly installed systems. Any help along these lines will be greatfully received. On Fri, 13 Nov 2015, Jude DaShiell wrote: Date: Fri, 13 Nov 2015 16:23:35 From: Jude DaShiell <jdashiel@xxxxxxxxxxx <mailto:jdashiel@xxxxxxxxxxx>> To: Tim Cross <theophilusx@xxxxxxxxxxx <mailto:theophilusx@xxxxxxxxxxx>> Cc: emacspeak <emacspeak@xxxxxxxxxxx <mailto:emacspeak@xxxxxxxxxxx>> Subject: Re: different test results Resent-Date: Fri, 13 Nov 2015 16:23:36 -0500 (EST) Resent-From: emacspeak@xxxxxxxxxxx <mailto:emacspeak@xxxxxxxxxxx> The basic sound output is alsa since pulseaudio doesn't make any sound but does manage alsa. On Mon, 9 Nov 2015, Tim Cross wrote: Date: Sun, 8 Nov 2015 15:36:38 From: Tim Cross <theophilusx@xxxxxxxxxxx <mailto:theophilusx@xxxxxxxxxxx>> To: Jude DaShiell <jdashiel@xxxxxxxxxxx <mailto:jdashiel@xxxxxxxxxxx>> Cc: emacspeak <emacspeak@xxxxxxxxxxx <mailto:emacspeak@xxxxxxxxxxx>> Subject: Re: different test results Are you using alsa or pulseaudio as your basic sound output? I would be surprised if SOX is causing problems. One of the options for playing auditory icons now uses SOX. I've used this as my default for auditory icons on both Linux and OSX for the past few months and it works really well. I am using viavoice outloud on linux rather than espeak though. It isn't clear (to me) from your email exactly what you expected from your tests and what is not working correctly. On 8 November 2015 at 20:54, Jude DaShiell <jdashiel@xxxxxxxxxxx <mailto:jdashiel@xxxxxxxxxxx>> wrote: Before doing the next test, I removed the sox package from the system then rebooted. This time tclsh enter just said espeak next q "this is a test." enter d enter said this is a test. I couldn't find any percent signs on the screen even after hitting the enter key a couple times so I typed exit enter and exited back to the servers directory. With emacspeak starting up on emacs, speech is at normal speed not slower. That sox package and emacspeak may not play nicely together. I put it on the machine to enable recording from microphone into files on the computer originally. -- ----------------------------------------------------------------------------- To unsubscribe from the emacspeak list or change your address on the emacspeak list send mail to "emacspeak-request@xxxxxxxxxxx <mailto: emacspeak-request@xxxxxxxxxxx>" with a subject of "unsubscribe" or "help". -- -- ----------------------------------------------------------------------------- To unsubscribe from the emacspeak list or change your address on the emacspeak list send mail to "emacspeak-request@xxxxxxxxxxx <mailto:emacspeak-request@xxxxxxxxxxx>" with a subject of "unsubscribe" or "help". -- regards, Tim -- Tim Cross-- Christopher (CJ) chaltain at Gmail
--
|All Past Years |Current Year|
If you have questions about this archive or had problems using it, please contact us.