[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Search]

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> 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>
To: Tim Cross <theophilusx@xxxxxxxxxxx>
Cc: emacspeak <emacspeak@xxxxxxxxxxx>
Subject: Re: different test results
Resent-Date: Fri, 13 Nov 2015 16:23:36 -0500 (EST)
Resent-From: 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>
To: Jude DaShiell <jdashiel@xxxxxxxxxxx>
Cc: emacspeak <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> 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" with a
subject of "unsubscribe" or "help".








--




--
regards,

Tim

--
Tim Cross



|All Past Years |Current Year|


If you have questions about this archive or had problems using it, please contact us.

Contact Info Page