Pulse Audio being initiated upon log in or start up of OS not afterwords
 

I got this thing called PalseAudio installed on my VOID Linux system. I too have this thing called Enlightenment Installed. it is classified as a desktop environment. within this classified enviroment it has a terminal emulator named terminology.

This terminal emulator has an option setting under the heading of behavior called "react to key presses" this invokes the terminal emulator to send to the speakers a sound that mimics a hard core old time type writer sound.

it does not produse this sound unless one of two things happen prior to me typing in this terminal emulator to cause it to do so. I have to either open up pavcontrol or start up a moive to invoke PulseAudio to actually start up and work, else I'll get this scratchy noise instead.

Google has not been good to me in helping me to find a solution.
Bad Google Bad! :p

so now I come here to post this question. how do I get PulseAudio to be in that same state it goes into when I start pavcontrol or MPlayer in order to get them chackly sounds of the Hard Core old time type writer without have to first start up pavcontrol or MPlayer first?

SWAG from a non-slacker
 

Don't know because I don't do slack, but once your desktop environment loads (whatever is on top of Enlightenment), there should be something named "System Settings" or similar. Under that, you should find something like "Multimedia" and under that there should be sound configuration options. That should be where you can tell it to use pulseaudio as the default, etc..

Have you tried putting pavucontrol in the startup applications list?

On the menu, Enlightenment-->Settings Panel-->Apps-->Startup Applications.

mmm nope its s gui app if I did that then this really big gui thing would pop open I do suppect .. don't want a have that up and running all of the time.


too it is more for when i am using this term in a different WM mostly I forgot to make mention of that too SOOO SORRY -- but PulseAudio Sucks the only thing I like about it is that it boost the volume more and because it was already installed on this VOID LINUX system I am reluctant to remove it -- having to hope sound will sitll work with just ALSA without having to do all kinds of reconfiguring files, searching fidning editing and rebooting all all that ..


so what ever pavucontrol does when it starts up or what ever takes palce when I start a movie or music needs to take place as soon as I start a WM ... that is the information I need to know. then I can try to figure out how to get that to take place without having to do any of the prior events to get PulaseAudio to kick in.

I'm not at a computer running Enlightenment right now, but I think you can minimize pavucontrol and then tell Enlightenment to remember the state of the window on startup by right-clicking on the icon in the iconbar and following the "Windows-->Remember-->Advanced" prompts.

After reading the documentation for Pulse Audio, I believe what you want to do is run pulse audio as a system daemon instead of a per-user basis. This will ensure that pulse audio is always running. What I believe is happening is your system is using Alsa by default and it isn't configured properly.

So, you could do one of two things:

1. Properly configure alsa to work with your sound card and forget about PulseAudio.
2. Configure PulseAudio to run as a daemon so that it is enabled by default at boot.

Seems like the pulseaudio route may be easiest for you. Here is the documentation that explains how to set up pulseaudio to do this:

https://wiki.freedesktop.org/www/Sof...entation/User/

put this in whatever startup file you have.

This will start the pulseaudio system without waiting for a client app to use the sound system first.

NOOOOooooOOOoooOOOoooOOOoo that doesn't even work I tried it. it just tells me it is already strated and still I get that same ole situation of it not processing sounds properly until I open up pavucontrol or start a movie. who invented this crap anyways, and why is it still even avalabe to use so others put it in their Linux distros for me and others to have to try and deal with it... ahhh aggravation and black coffee do not mix well. ;)

that sounds like I might have to look into that more deeply cpu and resources are not really on top of my list to worry about too much it is just me and my laptop no one else is logged in onto it for secuity worries.


or just rip out PA and hope it doesn't make fixing ASLA a head ache in the process.

Is this sound part of the default terminal app?