Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| wiki:pulseaudio [2012/10/25 20:45] – [What packages to have onboot] add link aus9 | wiki:pulseaudio [2013/06/25 04:58] (current) – [Create dbus config] fix echo command aus9 | ||
|---|---|---|---|
| Line 91: | Line 91: | ||
| < | < | ||
| mkdir .X.d | mkdir .X.d | ||
| - | echo 'dbus-launch --sh-syntax --exit-with-session' | + | echo "dbus-launch --sh-syntax --exit-with-session" |
| </ | </ | ||
| Please note the dot before and after the capital x please | Please note the dot before and after the capital x please | ||
| Line 158: | Line 158: | ||
| I will repeat, for me, I had no missing errors although a short while ago I did and one stage need to install GConf.tcz but a repeat test seems to have cleared that error. | I will repeat, for me, I had no missing errors although a short while ago I did and one stage need to install GConf.tcz but a repeat test seems to have cleared that error. | ||
| - | **googe non-missing errors**\\ | + | **google |
| After resolving missing packages for the onboot list, you might still have some that appear to be configuration type errors. | After resolving missing packages for the onboot list, you might still have some that appear to be configuration type errors. | ||
| eg | eg | ||
| Line 194: | Line 194: | ||
| reboot to test pulseaudio -v command. If all good, start pavucontrol thru your menu please. | reboot to test pulseaudio -v command. If all good, start pavucontrol thru your menu please. | ||
| - | =====Tweak so PA is always on===== | + | =====Temporary tweak ONLY so PA is always on===== |
| While you are tweaking your config files, edit default.pa and hash out the module that is shutting PA down so lines become | While you are tweaking your config files, edit default.pa and hash out the module that is shutting PA down so lines become | ||
| Line 215: | Line 215: | ||
| Instead of the start command re-click the pavucontrol icon/menu item. | Instead of the start command re-click the pavucontrol icon/menu item. | ||
| - | Once you have tweaked, re-enable the shutdown config option please | + | Once you have tweaked, re-enable the shutdown config option please. If you do do reverse this tweak, you may have issues with some sound applications wanting to use sound device but PA might not " |
| + | |||
| + | This is another negative aspect of PA but you only need to close down paprefs, pavucontrol and stop using PA commands like pacmd and the autostop function will work. | ||
| =====Tweak sample rate===== | =====Tweak sample rate===== | ||
| Line 382: | Line 384: | ||
| =====Network and sharing===== | =====Network and sharing===== | ||
| see http:// | see http:// | ||
| + | |||
| + | =====PA controls sound device issues===== | ||
| + | If you have pavucontrol open, then PA controls your device and won't release. This impacts on microphone testing of arecord as per alsa wiki.\\ | ||
| + | Solution close down all pavucontrol and paprefs and wait about 10 seconds and try again. | ||
| + | |||
| + | You know PA has control when you see an error like this | ||
| + | < | ||
| + | arecord -d 20 -f dat / | ||
| + | ALSA lib pcm_dsnoop.c: | ||
| + | arecord: main:660: audio open error: Device or resource busy | ||
| + | </ | ||
| + | |||
| + | =====PA and mic issues===== | ||
| + | If you want to record using a normal mic, without using any suspender command, PA will be active and not give control to " | ||
| + | |||
| + | But before closing down pavucontrol, | ||
| + | |||
| + | {{wiki: | ||
| + | |||
| + | Now I have deliberately shown a naughty image. I have raised volumes higher than my hardware can do. This proves PA is a post-processor and is a warning do not have volumes set this high....you will have distortion. | ||
| + | |||
| + | Now I reset the volume for me around 80% | ||
| + | |||
| + | Now if your voice on playback has sufficient volume then one issue is resolved. But you can have machine hum. This may be easy to resolve by having your mic input as far away as possible from any fan noise. (B) If you can, consider reducing any fan speeds on your pc. | ||
| + | |||
| + | |||
