View Full Version : HOWTO: PulseAudio Fixes & System-Wide Equalizer Support
psyke83
May 10th, 2008, 05:26 PM
HOWTO: PulseAudio Fixes & System-Wide Equalizer Support
Overview:
Note 1. Karmic & Jaunty users: If you have dist-upgraded from a previous release, I recommend that you follow the guide to remove obsolete configuration. If you have performed a clean installation, follow the guide only if you are experiencing issues.
Note 2. Jaunty & Intrepid users: due to a bug in the ALSA libraries, your PCM mixer may occasionally become muted or reset to 0% volume. If you cannot hear sound - or hear a faint crackling - refer to Part A, Step 6.
Note 3: OSSv4 users: PulseAudio does not support OSSv4, so this guide will serve no purpose to you. If you have chosen to install OSSv4 and experience issues, you should seek guidance within the threads dedicated to OSSv4. I do not recommend users to install OSSv4 due to compatibility and support issues.
Note 4: Kubuntu users: Don't follow this guide - PulseAudio isn't used in your distribution.
PulseAudio is an advanced sound server which has been included in Ubuntu (i.e. the standard GNOME version) since the release of Hardy Heron (8.04). Unfortunately, Hardy shipped with a suboptimal configuration of PulseAudio which has resulted in users experiencing various problems, ranging from sporadic crashes in Firefox to sound mixing being completely broken. PulseAudio in Intrepid should work by default, but it is quite possible that your configuration is suboptimal. For more information, refer to the FAQ below.
For best results, I recommend all users who are interested in PulseAudio to install the latest release - Karmic Koala (9.10). The developers have done an excellent job with PulseAudio integration and configuration in this release - enough to make this guide virtually obsolete.
When you are ready to follow this guide, this is all you need to know:
Hardy users: Follow Part A & B.
Intrepid users: Follow Part A & C.
Jaunty users: Follow Part A.
Karmic users: Follow Part A.
Additionally:
Appendix A gives general troubleshooting tips - if you have problems, start here.
Appendix B gives useful information on the more advanced/technical features of PulseAudio.
Appendix C gives information on how to properly configure specific applications that may not work with PulseAudio by default, including (but not limited to): WINE, Skype, and all OSS applications.
Appendix D (only for Intrepid and lower) will show you how to enable equalized audio for all applications on your system - this is especially useful for laptop users who experience poor audio quality with their internal speakers.
Frequently Asked Questions
The most common queries are answered here.
Q. What exactly is PulseAudio?
A. From the homepage (http://www.pulseaudio.org/):
PulseAudio is a sound server for POSIX and Win32 systems. A sound server is basically a proxy for your sound applications. It allows you to do advanced operations on your sound data as it passes between your application and your hardware. Things like transferring the audio to a different machine, changing the sample format or channel count and mixing several sounds into one are easily achieved using a sound server.
Simplified: PulseAudio is responsible for playback and mixing of audio on your system. It is not a sound driver - in fact, it runs on top of the Advanced Linux Sound Architecture (http://www.alsa-project.org/) (ALSA). Aside from all the cool effects PulseAudio provides, it serves as a replacement for ALSA's virtual sound mixing device (DmixPlugin (http://alsa.opensrc.org/DmixPlugin), or "dmix") - thus allowing multiple applications to share access to your sound card.
Q. PulseAudio? Bleh! I don't want it on my system.
A. Well... tough! PulseAudio is already installed and active on Hardy and Intrepid by default; it replaces ESD (ESound Daemon) for system sounds, and most of Ubuntu's default applications already use it (Totem, Rhythmbox, and any other applications using the GStreamer framework). Although some high-profile applications support PulseAudio natively (such as VLC and mplayer), most applications use plain ALSA or OSS output, and thus don't have native PulseAudio support.
Q. If PulseAudio is already installed, why do I need this guide?
A. While PulseAudio has been installed by default since Hardy Heron (8.04), we dropped the ball when it came to the configuration part. A quote from the main PulseAudio developer, Lennart Pöttering (http://0pointer.de/blog/projects/jeffrey-stedfast.html):Some distributions did a better job adopting PulseAudio than others. On the good side I certainly have to list Mandriva, Debian, and Fedora. OTOH Ubuntu didn't exactly do a stellar job. They didn't do their homework. Adopting PA in a distribution is a fair amount of work, given that it interfaces with so many different things at so many different places. The integration with other systems is crucial. The information was all out there, communicated on the wiki, the mailing lists and on the PA IRC channel. But if you join and hang around on neither, then you won't get the memo. To my surprise when Ubuntu adopted PulseAudio they moved into one of their 'LTS' releases rightaway. Which I guess can be called gutsy -- on the background that I work for Red Hat and PulseAudio is not part of RHEL at this time. I get a lot of flak from Ubuntu users, and I am pretty sure the vast amount of it is undeserving and not my fault.
When PulseAudio is running, it requires exclusive access to your sound card in order to work correctly as it assumes responsibility for mixing application's sounds instead of ALSA's "dmix" device. If you launch a "regular" application that does not have explicit PulseAudio support, it will most likely try to open the "Dmix" device - and this will deprive PulseAudio of control over the sound card. From the user's perspective, they will observe that audio mixing between applications is broken.
PulseAudio includes ALSA plugins (within the package "libasound2-plugins") which are designed make regular ALSA applications remap audio to the PulseAudio server (and thus avoid mixing problems as described above). Unfortunately, Hardy Heron shipped without these plugins enabled (or even installed) by default, which is causing many, many audio mixing issues for users. To compound the problem, the version of these PulseAudio ALSA plugins in the Hardy repositories do not function correctly, so updated versions are required for ALSA applications to work correctly with PulseAudio.
By following this guide, your system will be configured to use these PulseAudio ALSA plugins for Hardy users (and updated versions of necessary packages will get installed from my PPA (https://launchpad.net/~psyke83/+archive)). Although Intrepid has these plugins installed and configured by default, following this guide is still worthwhile because a) it will ensure you have a clean PulseAudio configuration, and b) you will hopefully gain a better understanding of how PulseAudio works.
Q. I'm glad to hear these issue are fixed in Intrepid, but why the hell aren't they fixed in Hardy already?
A. The simplest answer to this question is: complexity. Hardy is a LTS (Long Term Support) release, and there is a very strict policy towards updates (SRU; even the most trivial of bugfixes are entered into a code review). In order to fix Hardy, many components will require updates and changes, including but not limited to: libflashsupport, ia32-libs, pulseaudio, libasound2, libasound2-plugins, flashplugin-nonfree, nspluginwrapper...
Up until the last moment of Hardy's development cycle, the PulseAudio ALSA plugins weren't functioning correctly, and Flash 9 absolutely would not work without the "evil" libflashsupport library (I say evil, because it caused frequent random crashes in Firefox) - and so it wasn't possible to enact the required changes before the final release. It's possible now, but there would require a huge amount of effort to review and apply these changes.
Q. I followed your guide and PulseAudio still doesn't work!
A. Refer to Appendix A and provide the requested information in your post.
Q. I can't get Skype/WINE/an OSS application/XYZ working correctly with PulseAudio, what can I do?
A. Some applications require some extra configuration, and some applications don't work with PulseAudio - please refer to Appendix C for information on specific applications.
Q. Where can I find the appropriate bug reports related to these issues?
A. If you click on a step number it will link to the appropriate bug report, if one exists.
Part A: Common instructions (Hardy, Intrepid, Jaunty & Karmic)
All users must must follow the steps in this section to guarantee a fully working PulseAudio configuration.
1. Backup (and then delete) your previous configuration files: $ mkdir ~/pulse-backup && cp -r ~/.pulse ~/.asound* /etc/asound.conf /etc/pulse -t ~/pulse-backup/
$ rm -r ~/.pulse ~/.asound*
$ sudo rm /etc/asound.conf
Warning: As always, use caution when removing files on your system. Any typos can potentially cause data loss.
Note: Don't worry if some of these files did not exist on your system.
2. Ensure you have the necessary PulseAudio libraries and configuration utilities installed:
$ sudo apt-get install libasound2-plugins padevchooser libsdl1.2debian-pulseaudio
3 (https://bugs.launchpad.net/bugs/192888). Ensure the evil "libflashsupport" library is not installed:$ sudo apt-get remove --purge libflashsupport flashplugin-nonfree-extrasound
Note: the libflashsupport library was (and to a certain extent, still is) the most common cause of Firefox instability since the Hardy release, because many users have been misled into thinking they must install it to ensure Flash & PulseAudio can work correctly. If you notice any postings that recommend this library to be installed, please reply to the post and point them to this thread, or the bug report linked. The more people that are aware of this issue the better. Thanks!
4. (Karmic users - please skip this step, it's not necessary). Open System/Preferences/Sound. In the Devices section, ensure that all "Sound playback" options are set to Autodetect. Set the "Sound capture" item to "ALSA", or the appropriate hardware definition. Close the application when you're finished.
Note: Choosing PulseAudio for sound capture may result in crashes, so you are advised to choose the "direct" ALSA device instead.
5. Open the PulseAudio Volume Control application ("pavucontrol", or you can launch "Applications/Sound & Video/PulseAudio Device Chooser" and select Volume Control from this applet's menu). In the Output Devices section you will see a listing of the playback devices available on your system. Right-click on the entry that you desire to be made the default playback device on your system and enable the "Default" checkmark. Similarly, navigate to Input Devices, then right-click on the device you wish to set as your default input device (microphone), and ensure the "Default" setting is checked. Close the application when you're finished.
Note: If you are greeted with the error "Connection failed: Connection refused", manually launch PulseAudio before opening the PulseAudio Volume Control application:
$ pulseaudio & pavucontrol6. Ensure that your sound card's PCM mixer is not muted or set to 0% volume (this appears to be a common bug in Intrepid and Jaunty):
$ alsamixer -Dhw
Note: When the PulseAudio ALSA plugins are active, you must explicitly specify your hardware device in alsamixer (marked in blue above), otherwise it will open the PulseAudio mixer.
7. Continue to Part B if you are running Hardy Heron (8.04), or Part C if you are running Intrepid Ibex (8.10). If you are running Karmic Koala (9.10) or Jaunty Jackalope (9.04), you're finished - log out and back in for changes to take effect!
Part B: Hardy Heron (8.04)
Follow the steps in this section only if you are running the Hardy Heron release.
Disclaimer: My PPA contains the necessary packages backported from Intrepid for: PulseAudio, ALSA, Flash 10 and nspluginwrapper. If you upgrade to a newer distribution, or Hardy receives official updates for any of these packages, you will not experience any issues.
0 (https://bugs.launchpad.net/bugs/246911). 64-bit users only: Install "getlibs" and some extra 32-bit libraries that are required for Flash 10 & Skype to function properly:$ wget http://www.boundlesssupremacy.com/Cappy/getlibs/getlibs-all.deb && sudo dpkg -i getlibs-all.deb && rm getlibs-all.deb
$ sudo getlibs -p libnss3-1d libnspr4-0d libcurl3 libasound2-plugins
1. Edit /etc/apt/sources.list:$ gksudo gedit /etc/apt/sources.list
If they don't already exist, add the following lines to the end of this file and save:# PulseAudio Fixes - http://ubuntuforums.org/showthread.php?t=789578
deb http://ppa.launchpad.net/psyke83/ubuntu hardy main
deb-src http://ppa.launchpad.net/psyke83/ubuntu hardy main
2. Add the authentication key for my PPA, update your repositories and upgrade packages:$ sudo apt-key adv --recv-keys --keyserver keyserver.ubuntu.com 16AE4E77 && sudo apt-get update && sudo apt-get dist-upgrade
3 (https://bugs.launchpad.net/bugs/198453). Enable the PulseAudio ALSA plugins:$ asoundconf set-pulseaudio
Note: Please wait until you have upgraded packages in the previous step before running this command. My packages have a patch for "asoundconf" to ensure it enables the PulseAudio plugins correctly.
4. Log out & back in for changes to take effect!
Part C: Intrepid Ibex (8.10)
Follow the steps in this section only if you are running the Intrepid Ibex release.
Disclaimer: Currently there are no updated packages for Intrepid in my PPA (except for an updated nspluginwrapper package for i386 users). I have decided to keep this step in the guide in case I upload any important updates that will not make it into the official repositories. I will never upload any "risky" packages (i.e. highly untested backports), only upgrades that seem compelling and relatively stable.
1. Edit /etc/apt/sources.list:$ gksudo gedit /etc/apt/sources.list
If they don't already exist, add the following lines to the end of this file and save:# PulseAudio Fixes - http://ubuntuforums.org/showthread.php?t=789578
deb http://ppa.launchpad.net/psyke83/ubuntu intrepid main
deb-src http://ppa.launchpad.net/psyke83/ubuntu intrepid main
2. Add the authentication key for my PPA, update your repositories and upgrade packages:$ sudo apt-key adv --recv-keys --keyserver keyserver.ubuntu.com 16AE4E77 && sudo apt-get update && sudo apt-get dist-upgrade
4. Log out & back in for changes to take effect!
Appendix A - General Troubleshooting
This section will outline some general troubleshooting steps you can perform to help identify your problem, and the information I need to help with your issues:
Close all applications that may be accessing the sound card.
Open the "PulseAudio Device Chooser" from Applications/Sound & Video. Click on the applet icon, and click "Volume Control...". Click on the "Playback" tab.
Launch the application you wish to test and allow it to play sound.
Check PulseAudio Volume Control's Playback tab and see if the application displays an entry while the application is (or should be) playing audio.
Here are the possible results within the PulseAudio Volume Control's Playback tab:
The application does plays audio and does list an entry in the Playback tab;
- the application is using PulseAudio correctly.
The application does plays audio and does not list an entry in the Playback tab;
- the application is either accessing your sound card directly or playing sound via ALSA's dmix device. This will prevent PulseAudio from working correctly & cause audio mixing errors.
The application does not play audio and does list an entry in the Playback tab;
- the application is using PulseAudio but there is a problem, such as: a bug in PulseAudio, a problem with your ALSA kernel module or libraries, or your PCM/Master volume is muted.
The application does not play audio and does not list an entry in the Playback tab;
- the application is trying either to access your sound card directly or to play sound via ALSA's dmix device, but the sound card is already in use. This is the opposite case to result B, which will also cause mixing errors.
The PulseAudio Volume Control application displays the error: "Connection failed: Connection refused";
- the PulseAudio daemon is not running.
Other (please specify).
Note: Unless the application you are testing is known to be incompatible with PulseAudio, you should always expect result "A" on a properly configured system.
If you require assistance with a particular application - or simply cannot get PulseAudio to work - provide the following information:
Your distribution version and architecture (e.g. Hardy Heron i386, Intrepid Ibex amd64, etc.).
A listing of your sound devices:$ aplay -l
The verbose output from pulseaudio on your system: $ pkill pulseaudio; sleep 2; pulseaudio -vv
If you are having a problem only with a specific application, specify the application's name and result you received from the instructions above (A-F).
Appendix B: Advanced PulseAudio Configuration
This appendix will explain some of the more advanced/technical features of PulseAudio.
Q. Where are the PulseAudio configuration utilities?
A. Providing you've followed this guide, you can gain access to all the utilities by launching "Applications/Sound & Video/PulseAudio Device Chooser". The applet's icon will appear in your notificiation tray - left-click to see the options.
The main applications you will want to check are the Manager (to see the current server status) and Volume Control (to manipulate the volume and stream settings).
Note: Please don't mess with any of the options until you have established a working configuration by following this guide - otherwise it'll be a nightmare to isolate your problem.
Q. How can I tell if an application is using PulseAudio successfully?
A. The application will give you result "A" from the troubleshooting steps of Appendix A.
Q. How can I change the default playback and/or recording device for my system?
A. Refer to Part A, Step 5.
Q. Is it possible to change to a different playback and/or recording device for an individual application?
A. Yes. Launch the desired application and play some sound (or begin recording), and open the PulseAudio Volume Control. Click the Playback or Recording tab (depending on which you want to change) and right-click on the desired application's entry. Choose the option "Move Stream..." and select the desired output device.
Note: The volume level, sink (playback) and source (recording) settings will be saved automatically for every application you run, so PulseAudio should remember your settings. If you wish to view or delete these saved settings, they're stored in the file "~/.pulse/volume-restore.table".
Q. If I plug in my USB/Bluetooth headset, my external speakers no longer work!
A. This is normal behaviour, as PulseAudio supports "hotplugging" of audio devices. If you plug in a new device, PulseAudio may choose it as the default sink (audio device). Also see Part A, Step 5.
Q. PulseAudio is working correctly, but I am noticing some stuttering on my system. Is there anything I can do to help?
A. Edit the file /etc/pulse/daemon.conf:
$ gksudo gedit /etc/pulse/daemon.conf
Find the following lines (usually at the bottom):
default-fragments = 8
default-fragment-size-msec = 10
Try experimenting with different values for both of these entries. I can't tell you what values are optimal for your system, as each sound card has different buffer sizes and characteristics - therefore you'll need to use trial & error. The default fragment amount and size used by an untweaked PulseAudio installation is 4 and 25, respectively.
Note 1: you must restart pulseaudio for any configuration changes to take effect.
Note 2: If your system was stuttering in versions of Ubuntu prior to Hardy, then you could be suffering from an ALSA kernel issue - these instructions probably won't help.
Q. I'm unhappy about the audio quality / CPU usage of PulseAudio. How do I change this?
A. For the record, PulseAudio should offer superior quality audio playback than ALSA's by default, as PulseAudio uses a higher quality audio resampler. This also means that PulseAudio may use more CPU usage compared to ALSA, unfortunately. If you wish to change the resampler:
Edit /etc/pulse/daemon.conf:$ gksudo gedit /etc/pulse/daemon.conf
Find the following line:resample-method = speex-float-1
You can change the resampler to any of the following, listed in descending order, from highest quality to lowest quality (and therefore, CPU usage):src-sinc-best-quality, src-sinc-medium-quality, src-sinc-fastest, speex-float-{10-0}, speex-fixed-{10-0}, ffmpeg, src-zero-order-hold, src-linear, trivial
Appendix C: Application Compatibility Guide
This appendix will explain how to configure specific applications that may require manual configuration to work with PulseAudio.
OSS applications: You need to launch the application using the "padsp" wrapper. For more information, see "man padsp".
Skype: The latest release of Skype has native PulseAudio support, and does not require special configuration. If you are using an older version, continue reading. Open Skype's Options, then go to Sound Devices. You need to set "Sound Out" and "Ringing" to the "pulse" device, and set "Sound In" to the hardware definition of your microphone. For example, my laptop's microphone is defined as "plughw:I82801DBICH4,0".
WINE: Open the Wine Configuration application ("winecfg"). On the Audio tab, choose the ALSA driver, and leave everything else to default. If your sound stutters, choose the OSS driver instead, and use the "padsp" wrapper to launch the wine executable (via the terminal, or edit your shortcuts).
Audacity (Intrepid users only, version in later distributions work correctly): From the PerfectSetup (http://www.pulseaudio.org/wiki/PerfectSetup) page:
Audacity has now been packaged with a proper "alsa: pulse" device listed, in a ppa for ubuntu intrepid. See https://launchpad.net/~diwic/+archive
Everything else: refer to the Third Party Applications section of the upstream PerfectSetup (http://www.pulseaudio.org/wiki/PerfectSetup#ThirdPartyApplications) wiki page.
Note: Many of the instructions on the PerfectSetup page are either outdated, too distro-agnostic to work on Ubuntu, or have been obsoleted by the fixes in this guide. You should ignore the advice for: ALSA applications, Flash, ESOUND, GNOME, GStreamer Applications, SDL, and Skype.
Appendix D: System-Wide Equalizer
In this section, we will configure PulseAudio to use equalized output, which is especially useful for laptops speakers which have very poor frequency response. If your sound is "tinny" or distorted at high ranges, then this will most likely enhance the quality of your audio.
Warning 1: Karmic users - please ignore these instructions and use the PulseAudio Equalizer Script (http://ubuntuforums.org/showthread.php?t=1308838) instead.
Warning 2: Do not attempt to set up the equalizer until you have followed the other parts of this guide and verified that PulseAudio works correctly using "unmodified" output.
Warning 3: The equalizer may not work on 64 bit systems, as extra 32-bit libraries could be required. If it doesn't work, simply revert the changes you made.
Warning 4: The equalizer currently does not work for Jaunty users, as there seems to be missing LADSPA plugins in the libasound2-plugins package. I'm investigating the issue currently, though you may want to test the Karmic equalizer script (mentioned above).
1. Install the required LADSPA plugins and tools:
$ sudo apt-get install swh-plugins ladspa-sdk
2. Edit ~/.asoundrc:
$ gedit ~/.asoundrc
Append the following text to the bottom of this file and save:
pcm.equalized {
type plug
slave.pcm "equalizer";
}
pcm.equalizer {
type ladspa
# The output from the EQ can either go direct to a hardware device
# (if you have a hardware mixer, e.g. SBLive/Audigy) or it can go
# to the software mixer shown here.
slave.pcm "plughw"
#slave.pcm "plug:dmix"
# Sometimes you may need to specify the path to the plugins,
# especially if you've just installed them. Once you've logged
# out/restarted this shouldn't be necessary, but if you get errors
# about being unable to find plugins, try uncommenting this.
path "/usr/lib/ladspa"
plugins [
{
label mbeq
id 1197
input {
#this setting is here by example, edit to your own taste
#bands: 50hz, 100hz, 156hz, 220hz, 311hz, 440hz, 622hz, 880hz,
# 1250hz, 1750hz, 2500hz, 5000hz, 10000hz, 20000hz
#range: -70 to 30
controls [ -1 -1 -1 -1 -5 -10 -20 -17 -12 -7 -6 -5 -5 0 0 ]
}
}
]
}
Note 1: If you are using the Intrepid or Jaunty release, this file will not exist - that's ok. Simply paste into the new file and save normally.
Note 2: If you have multiple sound cards, the section of this text marked in blue may need to be modified slightly. If you have problems, ask in the thread.
3. Edit /etc/pulse/default.pa:$ gksudo gedit /etc/pulse/default.pa
Find the following line marked in blue:
### Load audio drivers statically (it's probably better to not load
### these drivers manually, but instead use module-hal-detect --
### see below -- for doing this automatically)
#load-module module-alsa-sink
#load-module module-alsa-source device=hw:1,0
#load-module module-oss device="/dev/dsp" sink_name=output source_name=input
Change the line in blue to the following, and save:load-module module-alsa-sink device=equalized
Note: Be sure to also remove the comment (#) at the beginning of the line.
4. Log out & back in for changes to take effect!
That's all folks!
Changelog
Any notable changes to the guide will be mentioned here.
v4.0 - 13/11/08 - Complete re-write. Completely reorganized; Hardy & Intrepid guides merged. Yes, I know it's ridiculously long :P
v4.1 - 16/11/08 - Corrected some errors in the equalizer section, re-arranged guide to avoid problems with enabling ALSA plugins. Hardy users who followed the earlier revision of this guide: please run "asoundconf set-pulseaudio" to resolve any issues.
v4.2 - 23/11/08 - Added a step in Part C; due to a bug in Intrepid, users should verify their PCM volume is not muted.
v4.3 - 11/12/08 - Added a small note for OSSv4 users & information regarding PulseAudio-compatible Audacity packages available for testing.
v4.4 - 06/01/09 - Fixed typo in Skype configuration section.
v4.5 - 21/03/09 - Added note for Jaunty users.
v4.6 - 01/04/09 - Note added to Part A, Step 4.
v4.7 - 23/04/09 - Added Jaunty support.
v4.8 - 12/05/09 - Note added regarding the equalizer for Jaunty users.
v4.9 - 19/05/09 - Added instructions to add repository key, to prevent authentication warnings.
v5.0 - 13/07/09 - Moved PCM zero-volume workaround to Part A.
v5.1 - 24/10/09 - Updated instructions for Karmic users.
hyperair
May 11th, 2008, 11:42 PM
That's a rather interesting way of doing it. I've never thought of using this method for a system-wide equalizer. However, I'd like to point out a few things regarding your default.pa.txt.
This line "load-module module-alsa-sink device=equalized" conflicts with this line "load-module module-hal-detect" on systems where sound mixing is not supported. It doesn't matter if the equalized device's pcm is plug:dmix or plughw:#,#. Once module-alsa-sink is loaded, whether it uses dmix or plughw, Pulseaudio (using plughw) or dmix will grab the sound card all for itself. Then when module-hal-detect tries to load another ALSA sink from HAL, it'll just fail miserably. Pulseaudio will fail to start. This is because module-hal-detect always tries to load a plughw sink.
My suggestion is that you comment out the line loading module-hal-detect. That's the only way it will work for those without hardware sound mixing.
bodger
May 12th, 2008, 01:04 AM
thanks for this. pulse audio was unusable for me until I installed the new kernel. smooth as now, bro.
PinkFloyd102489
May 12th, 2008, 02:26 AM
When reinstalling libflashsupport and flashplugin-nonfree, I got a dependency error because it relied on the older version of libasound2-dev. Simply downloading the new dev package to go along with the new libasound2 fixed this.
Might want to mention that.
psyke83
May 12th, 2008, 07:35 AM
My suggestion is that you comment out the line loading module-hal-detect. That's the only way it will work for those without hardware sound mixing.
Thanks for the feedback, but I'm not sure you're completely correct.
My audio card does not support hardware audio mixing*, and PulseAudio works perfectly with concurrent audio streams here. Additionally, I do believe that other applications can get exclusive access through "pasuspender" (not recommended, but useful for people with specific needs) or perhaps by accident due to the "suspend-on-idle" module.
I have a Philips VOIP080 USB Travel Phone; when I connect it while using the configuration in this HOWTO (i.e. with module-hal-detect active), PulseAudio picks up the phone, plays "startup3.wav" from the sample cache to signify it is working, and changes the default ALSA source to the phone's MIC. If I try to connect the phone without "module-hal-detect" loaded, PulseAudio does not detect its presence at all.
If you can propose a solution that allows hotplugging to work, then please let me know.
* Before PulseAudio was available, I used a LADSPA plugin via "asound.conf" and it was impossible to play concurrent sounds using "plughw", I was forced to use "plug:dmix" (which seemed to cause distorted output via the LADSPA definition). Now it is possible to mix sounds with PulseAudio using "plughw", which indications that a) my sound card doesn't support hardware mixing, and b) this configuration indeed works fine for people who do not have hardware mixing available on their sound cards.
Stunts
May 12th, 2008, 10:17 AM
Hi. I've followed this guide to sole a couple of problems I'm experiencing, but I may have done some damgae and I'm not sure how to roll back...
Installing the Debian packages has removed my flash, wine and teamspeak. I've tried apt-get --reinstall, but I get an error saying that the package cannot be downloadad. Using apt-get remove, says I also have to remove tons of stuff, like ubuntu-desktop. I'll tery and get the hardy deb packages and install them, to see if that solves my problem...
And I tought this was looking really promissing!
BTW, using AMD64 here.
Stunts
May 12th, 2008, 10:37 AM
OK, so getting the .deb packages fou hardy did made the trick. I'm back with wine, teamspeak and flash. I didn't get back to ground 0 tough. The part about the quick flash did work for me. (strangely it was the part that was supposed not to work with AMD64).
Edit: Well, not so good after all. I seem to have lost sound altogether. Pulse audio manager does show up an output when I try to play sounds. Using native ALSA applications also gives me sound. I guess this means that it's an issue with the output of pulse audio... any ideas on how to solve this?
Thanks
psyke83
May 12th, 2008, 01:18 PM
Hi. I've followed this guide to sole a couple of problems I'm experiencing, but I may have done some damgae and I'm not sure how to roll back...
Installing the Debian packages has removed my flash, wine and teamspeak. I've tried apt-get --reinstall, but I get an error saying that the package cannot be downloadad. Using apt-get remove, says I also have to remove tons of stuff, like ubuntu-desktop. I'll tery and get the hardy deb packages and install them, to see if that solves my problem...
And I tought this was looking really promissing!
BTW, using AMD64 here.
Are you sure you followed the instructions properly? I don't see how it could have caused packages to get uninstalled. If you can paste the output of apt-get, that will help a lot.
To revert the changes made, do the following:
$ sudo apt-get update
$ sudo apt-get remove --purge nspluginwrapper libflashsupport swh-plugins libasound2-dev
$ sudo dpkg -P --force-depends pulseaudio
$ sudo apt-get install pulseaudio libasound2/hardy libasound2-plugins/hardy ubuntu-desktop flashplugin-nonfree --reinstall
$ sudo rm /etc/asound.conf
Please don't continue these steps if it elects to uninstall half your system, etc. (though it shouldn't). Be mindful, and post the output here if you're unsure.
psyke83
May 12th, 2008, 01:29 PM
OK, so getting the .deb packages fou hardy did made the trick. I'm back with wine, teamspeak and flash. I didn't get back to ground 0 tough. The part about the quick flash did work for me. (strangely it was the part that was supposed not to work with AMD64).
Edit: Well, not so good after all. I seem to have lost sound altogether. Pulse audio manager does show up an output when I try to play sounds. Using native ALSA applications also gives me sound. I guess this means that it's an issue with the output of pulse audio... any ideas on how to solve this?
Thanks
If you want to try the guide again, I amended the instructions to fix the dependency error you experienced (you run "sudo apt-get install -f" after installing the Debian packages).
Stunts
May 12th, 2008, 02:22 PM
Hi and thanks for the quick answer.
I'll try and do what you suggest. I'm crossing my fingers. =-)
I just thought I could reinstall wine, etc after the changes, when I did it the first time.
Here we go again! =-)
Edit: I have reread the guide with the changes, but:
sudo apt-get install -f
was what uninstalled teamspeak, etc...
Don't get me wrong, I think this how to is very good, and simple to follow. I'll try again and see what I get.
Stunts
May 12th, 2008, 02:41 PM
OK, so here it is, I'm getting the exact same problem when following the guide. I'll post my steps here, after the download.
francisco@MegalaptopII:~/Desktop$ sudo dpkg -i libasound2_1.0.16-2_amd64.deb
[sudo] password for francisco:
(Reading database ... 120383 files and directories currently installed.)
Preparing to replace libasound2 1.0.15-3ubuntu4 (using libasound2_1.0.16-2_amd64.deb) ...
Unpacking replacement libasound2 ...
Setting up libasound2 (1.0.16-2) ...
Processing triggers for libc6 ...
ldconfig deferred processing now taking place
francisco@MegalaptopII:~/Desktop$ sudo dpkg -i libasound2-dev_1.0.16-2_amd64.deb
(Reading database ... 120382 files and directories currently installed.)
Preparing to replace libasound2-dev 1.0.15-3ubuntu4 (using libasound2-dev_1.0.16-2_amd64.deb) ...
Unpacking replacement libasound2-dev ...
Setting up libasound2-dev (1.0.16-2) ...
francisco@MegalaptopII:~/Desktop$ sudo dpkg -i libasound2-plugins_1.0.16-1_amd64.deb
(Reading database ... 120376 files and directories currently installed.)
Preparing to replace libasound2-plugins 1.0.15-1ubuntu3 (using libasound2-plugins_1.0.16-1_amd64.deb) ...
Unpacking replacement libasound2-plugins ...
Setting up libasound2-plugins (1.0.16-1) ...
francisco@MegalaptopII:~/Desktop$ sudo apt-get install -f
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
The following packages will be REMOVED:
flashplugin-nonfree ia32-libs lib32asound2 nspluginwrapper teamspeak-client
wine
0 upgraded, 0 newly installed, 6 to remove and 0 not upgraded.
After this operation, 173MB disk space will be freed.
Do you want to continue [Y/n]?
I just answered "n" and I'm about to do a fallback just like you indicated.
Ideas?
Stunts
May 12th, 2008, 02:46 PM
Hummm, something is wrong again.
When I follow your fallback instructions I get the folowing:
francisco@MegalaptopII:~/Desktop$ sudo apt-get remove --purge nspluginwrapper libflashsupport swh-plugins libasound2-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package swh-plugins is not installed, so not removed
You might want to run `apt-get -f install' to correct these:
The following packages have unmet dependencies:
flashplugin-nonfree: Depends: nspluginwrapper (>= 0.9.91.4-2ubuntu1) but it is not going to be installed
lib32asound2: Depends: libasound2 (= 1.0.15-3ubuntu4) but 1.0.16-2 is to be installed
E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution).
francisco@MegalaptopII:~/Desktop$ sudo apt-get remove --purge nspluginwrapper libflashsupport libasound2-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
You might want to run `apt-get -f install' to correct these:
The following packages have unmet dependencies:
flashplugin-nonfree: Depends: nspluginwrapper (>= 0.9.91.4-2ubuntu1) but it is not going to be installed
lib32asound2: Depends: libasound2 (= 1.0.15-3ubuntu4) but 1.0.16-2 is to be installed
E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution).
francisco@MegalaptopII:~/Desktop$ sudo dpkg -P --force-depends pulseaudio
dpkg: pulseaudio: dependency problems, but removing anyway as you request:
pulseaudio-dbg depends on pulseaudio (= 0.9.10-1ubuntu1).
ubuntu-desktop depends on pulseaudio.
paconfig depends on pulseaudio.
(Reading database ... 120388 files and directories currently installed.)
Removing pulseaudio ...
Purging configuration files for pulseaudio ...
francisco@MegalaptopII:~/Desktop$ sudo apt-get install pulseaudio libasound2/hardy libasound2-plugins/hardy ubuntu-desktop flashplugin-nonfree --reinstall
Reading package lists... Done
Building dependency tree
Reading state information... Done
Selected version 1.0.15-3ubuntu4 (Ubuntu:8.04/hardy) for libasound2
Selected version 1.0.15-1ubuntu3 (Ubuntu:8.04/hardy) for libasound2-plugins
You might want to run `apt-get -f install' to correct these:
The following packages have unmet dependencies:
libasound2-dev: Depends: libasound2 (= 1.0.16-2) but 1.0.15-3ubuntu4 is to be installed
E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution).
This is after the "sudo apt-get update" which goes fine. I just didn't post it because is long and somewhat irrelevant...
Krimpet
May 12th, 2008, 03:43 PM
This all worked quite well for me - it's great to have sound in Flash working again without random crashes, and the equalizer tips worked like a charm - my tinny Inspiron E1405 speakers can finally pump out some volume!
The only bump was with Skype - the ALSA "pulse" device seems to still not work, and I have to continue using the OSS version and padsp like I did before... however, after the tweaks to daemon.conf, the OSS version + padsp no longer has the crackling noises it did before. :)
hyperair
May 12th, 2008, 03:50 PM
This all worked quite well for me - it's great to have sound in Flash working again without random crashes, and the equalizer tips worked like a charm - my tinny Inspiron E1405 speakers can finally pump out some volume!
The only bump was with Skype - the ALSA "pulse" device seems to still not work, and I have to continue using the OSS version and padsp like I did before... however, after the tweaks to daemon.conf, the OSS version + padsp no longer has the crackling noises it did before. :)
What tweaks are you talking about?
Auslegung
May 12th, 2008, 04:21 PM
When doing the very first step and trying to dpkg libasound2-dev_1.0.16-2_i386.deb I get $ sudo dpkg -i /home/jason/Desktop/libasound2-dev_1.0.16-2_i386.deb
(Reading database ... 126496 files and directories currently installed.)
Preparing to replace libasound2-dev 1.0.16-2 (using .../libasound2-dev_1.0.16-2_i386.deb) ...
Unpacking replacement libasound2-dev ...
dpkg: dependency problems prevent configuration of libasound2-dev:
libasound2-dev depends on libc6-dev | libc-dev; however:
Package libc6-dev is not installed.
Package libc-dev is not installed.
dpkg: error processing libasound2-dev (--install):
dependency problems - leaving unconfigured
Errors were encountered while processing:
libasound2-dev
What's going on?
psyke83
May 12th, 2008, 04:37 PM
When doing the very first step and trying to dpkg libasound2-dev_1.0.16-2_i386.deb I get $ sudo dpkg -i /home/jason/Desktop/libasound2-dev_1.0.16-2_i386.deb
(Reading database ... 126496 files and directories currently installed.)
Preparing to replace libasound2-dev 1.0.16-2 (using .../libasound2-dev_1.0.16-2_i386.deb) ...
Unpacking replacement libasound2-dev ...
dpkg: dependency problems prevent configuration of libasound2-dev:
libasound2-dev depends on libc6-dev | libc-dev; however:
Package libc6-dev is not installed.
Package libc-dev is not installed.
dpkg: error processing libasound2-dev (--install):
dependency problems - leaving unconfigured
Errors were encountered while processing:
libasound2-dev
What's going on?
First of all, you are supposed to install all three packages at once via dpkg, not just libasound2-dev.
Secondly, these errors are to be expected and the next command, "sudo apt-get install -f" will resolve dependencies (i.e., installing libc6-dev and libc-dev). You need to install all three packages via dpkg before running this, though!
Note that I have made adjustments to the guide to prevent these (temporary) errors, in case other users get worried.
Auslegung
May 12th, 2008, 04:48 PM
First of all, you are supposed to install all three packages at once via dpkg, not just libasound2-dev.
Secondly, these errors are to be expected and the next command, "sudo apt-get install -f" will resolve dependencies (i.e., installing libc6-dev and libc-dev). You need to install all three packages via dpkg before running this, though!
Note that I have made adjustments to the guide to prevent these (temporary) errors, in case other users get worried.
Thank you, I ended up figuring that out on my own and should've edited my post to not take anyone's time. Sorry. I do have another question, though, that I hope isn't as obvious as my last. You say "Download the attachment "default.conf.txt" found at the bottom of this post and copy it to /etc/pulse/default.conf:" but the file is actually default.pa.txt. I'm confused.
psyke83
May 12th, 2008, 05:00 PM
Thank you, I ended up figuring that out on my own and should've edited my post to not take anyone's time. Sorry. I do have another question, though, that I hope isn't as obvious as my last. You say "Download the attachment "default.conf.txt" found at the bottom of this post and copy it to /etc/pulse/default.conf:" but the file is actually default.pa.txt. I'm confused.
You didn't waste anyone's time, in fact you spotted a mistake & it's been fixed, thanks a lot! Just so you know, you're supposed to copy "default.pa.txt" to "/etc/pulse/default.pa".
psyke83
May 12th, 2008, 05:07 PM
Hummm, something is wrong again.
When I follow your fallback instructions I get the folowing:
francisco@MegalaptopII:~/Desktop$ sudo apt-get remove --purge nspluginwrapper libflashsupport swh-plugins libasound2-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package swh-plugins is not installed, so not removed
You might want to run `apt-get -f install' to correct these:
The following packages have unmet dependencies:
flashplugin-nonfree: Depends: nspluginwrapper (>= 0.9.91.4-2ubuntu1) but it is not going to be installed
lib32asound2: Depends: libasound2 (= 1.0.15-3ubuntu4) but 1.0.16-2 is to be installed
E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution).
francisco@MegalaptopII:~/Desktop$ sudo apt-get remove --purge nspluginwrapper libflashsupport libasound2-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
You might want to run `apt-get -f install' to correct these:
The following packages have unmet dependencies:
flashplugin-nonfree: Depends: nspluginwrapper (>= 0.9.91.4-2ubuntu1) but it is not going to be installed
lib32asound2: Depends: libasound2 (= 1.0.15-3ubuntu4) but 1.0.16-2 is to be installed
E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution).
francisco@MegalaptopII:~/Desktop$ sudo dpkg -P --force-depends pulseaudio
dpkg: pulseaudio: dependency problems, but removing anyway as you request:
pulseaudio-dbg depends on pulseaudio (= 0.9.10-1ubuntu1).
ubuntu-desktop depends on pulseaudio.
paconfig depends on pulseaudio.
(Reading database ... 120388 files and directories currently installed.)
Removing pulseaudio ...
Purging configuration files for pulseaudio ...
francisco@MegalaptopII:~/Desktop$ sudo apt-get install pulseaudio libasound2/hardy libasound2-plugins/hardy ubuntu-desktop flashplugin-nonfree --reinstall
Reading package lists... Done
Building dependency tree
Reading state information... Done
Selected version 1.0.15-3ubuntu4 (Ubuntu:8.04/hardy) for libasound2
Selected version 1.0.15-1ubuntu3 (Ubuntu:8.04/hardy) for libasound2-plugins
You might want to run `apt-get -f install' to correct these:
The following packages have unmet dependencies:
libasound2-dev: Depends: libasound2 (= 1.0.16-2) but 1.0.15-3ubuntu4 is to be installed
E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution).
This is after the "sudo apt-get update" which goes fine. I just didn't post it because is long and somewhat irrelevant...
Unfortunately the "uninstall" instructions I gave you seem to cause problems on AMD64 systems, I'm on i386 here so I wasn't able to test.
Also, your final line suggests that you didn't remove libasound2-dev, perhaps you misread my instructions.
psyke83
May 12th, 2008, 05:11 PM
What tweaks are you talking about?
I believe Krimpet was referring to the "optional" step of Part C, which is also necessary for my system, otherwise any OSS applications using "padsp" stutter *extremely*. It's obvious it doesn't happen for everyone, if you take a look at the respective bug reports.
Stunts
May 12th, 2008, 05:41 PM
Unfortunately the "uninstall" instructions I gave you seem to cause problems on AMD64 systems, I'm on i386 here so I wasn't able to test.
Also, your final line suggests that you didn't remove libasound2-dev, perhaps you misread my instructions.
I think that might be the problem. Everything I do in apt-get after I install that package gives me that error. Maybe something is wrong with the package? I mean debian-ubuntu wise in AMD64?
Oh well, I have found a solution, I just quit Pulse audio, and now I'm using everything thru ALSA.
It's working better than I expected, surprisingly...
Krimpet
May 12th, 2008, 06:19 PM
I believe Krimpet was referring to the "optional" step of Part C, which is also necessary for my system, otherwise any OSS applications using "padsp" stutter *extremely*. It's obvious it doesn't happen for everyone, if you take a look at the respective bug reports.
Indeed, this was what I was referring to - the "optional" edits to daemon.conf have greatly improved the sound quality of padsp applications that were stuttering badly before. (I'm using a Dell Inspiron E1405 with an Intel 82801G sound card, which appears to be a quite similar setup to yours).
I'm not sure though whether padsp's stuttering was fixed by the daemon.conf tweak alone, or a combination of that _and_ the distupgrade (part C, 1-3) is what fixed it; perhaps someone running stock Hardy could make that edit their daemon.conf and see if that alone stops padsp from stuttering?
This is very good news for the legions of currently angry Skype users, by the way. :mrgreen:
Grone1985
May 12th, 2008, 08:05 PM
Hi, Thanks for your How-To... I a getting this dependencies problem.. I just want to make sure about something...
I installed the packages and after that I created the file... All that went OK but then I got that error with the dependencies and to correct it I ran the 'sudo apt-get install -f' and got this... Should I say yes or not? I'm not sure about all the things it says it needs to uninstall...
maitreyi@maitreyi-laptop:~$ sudo apt-get install -f
[sudo] password for maitreyi:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
The following packages were automatically installed and are no longer required:
lib32ncurses5 libc6-i386 skype-common lib32gcc1 lib32nss-mdns lib32z1
lib32stdc++6
Use 'apt-get autoremove' to remove them.
The following packages will be REMOVED:
flashplugin-nonfree ia32-libs lib32asound2 nspluginwrapper skype-static-oss
0 upgraded, 0 newly installed, 5 to remove and 0 not upgraded.
After this operation, 122MB disk space will be freed.
Thanks!
psyke83
May 12th, 2008, 08:31 PM
Hi, Thanks for your How-To... I a getting this dependencies problem.. I just want to make sure about something...
I installed the packages and after that I created the file... All that went OK but then I got that error with the dependencies and to correct it I ran the 'sudo apt-get install -f' and got this... Should I say yes or not? I'm not sure about all the things it says it needs to uninstall...
Please, don't uninstall anything yet. Can you try following Part A again (reload the page to see v1.6 of the HOWTO), and see if it fixes your problem? Please post the output of the same command i.e., "sudo apt-get install -f" if you still have problems.
Thanks.
psyke83
May 12th, 2008, 08:34 PM
Stunts,
Can you try Part A again too?
Afterwards, try:$ sudo apt-get install -f
$ sudo apt-get install ubuntu-desktop
...and it wants to install packages (*not* remove), please allow it.
Thanks!
Grone1985
May 12th, 2008, 08:47 PM
Please, don't uninstall anything yet. Can you try following Part A again (reload the page to see v1.6 of the HOWTO), and see if it fixes your problem? Please post the output of the same command i.e., "sudo apt-get install -f" if you still have problems.
Thanks.
Thanks! That fixed the dependencies problem... I will reboot now and check what happends... I'll post back with more info on the results... Thanks again!
Grone1985
May 12th, 2008, 08:56 PM
So... now I have no sound at all... And Skype doesn't want to load... I have the OSS version... Help please?
psyke83
May 12th, 2008, 09:02 PM
So... now I have no sound at all... And Skype doesn't want to load... I have the OSS version... Help please?
Try:
$ sudo apt-get install flashplugin-nonfree ia32-libs nspluginwrapper skype-static-oss skype-common lib32ncurses5 libc6-i386 lib32gcc1 lib32nss-mdns lib32z1 lib32stdc++6 ubuntu-desktop --reinstall
$ sudo apt-get install -f
You may need to provide more information, e.g. did you allow other packages to be uninstalled that wasn't listed in your post?
Grone1985
May 12th, 2008, 11:03 PM
I have sound now but Skype doesn't load and no, I haven't done anything else than what I've posted here. Also I don't understand the equalizer thing.. can you explain that to me a little more?
THanks!
psyke83
May 13th, 2008, 07:47 AM
I have sound now but Skype doesn't load and no, I haven't done anything else than what I've posted here.
I'm not sure why Skype won't load, all I can suggest is that you completely remove it and reinstall.
$ sudo apt-get remove --purge skype skype-common skype-static skype-static-oss
Try different versions of skype, e.g. the ALSA build, the static ALSA build or the OSS build, and if it doesn't work, paste any terminal output from skype here.
Also I don't understand the equalizer thing.. can you explain that to me a little more?
This HOWTO uses the mbeq (Multiband EQ) LADSPA audio processing plugin with settings suitable for laptop users. This is a general description of an equalization filter: http://en.wikipedia.org/wiki/Equalization_filter
If you read the links for Part D you'll see my post where I explain how some Windows XP drivers use "hidden" EQ software for some sound cards in laptops, and Linux/ALSA cannot do the same, causing audio to sound worse on Linux (unfortunately).
We can accomplish something similar using LADSPA plugins (there are links in the HOWTO). LADPA has much more flexibility than a simple equalizer, though; with the right LADSPA plugin, you can modify your sound output to make every voice sound like Chipmunks (...why you would want to do that is another question ;)), add reverb, white noise, crossfade, etc. etc. You are limited only to the plugins available to you.
Stunts
May 13th, 2008, 08:28 AM
Hi! I've seen your suggestion.
I'm at work right now and I can't try it, but I'll do it when I get home.
I'll let you know the outcome.
Grone1985
May 13th, 2008, 09:44 AM
Ok, so now Skype is not loading because it claims that libasound.so.2 doesn't exist...
maitreyi@maitreyi-laptop:~$ padsp skype
skype: error while loading shared libraries: libasound.so.2: cannot open shared object file: No such file or directory
but the thing is that libasound.so.2 is installed but it is in '/emul/ia32-linux/usr/lib' so I'm guessing there must be a way to tell Skype that libasound.so.2 is actually installed and where it is... But how is that?
Thanks!
psyke83
May 13th, 2008, 10:19 AM
Ok, so now Skype is not loading because it claims that libasound.so.2 doesn't exist...
maitreyi@maitreyi-laptop:~$ padsp skype
skype: error while loading shared libraries: libasound.so.2: cannot open shared object file: No such file or directory
but the thing is that libasound.so.2 is installed but it is in '/emul/ia32-linux/usr/lib' so I'm guessing there must be a way to tell Skype that libasound.so.2 is actually installed and where it is... But how is that?
Thanks!
No, that's the 32bit version of the library. I would imagine that you're missing the 64bit version. The following should restore Hardy's original versions:
$ sudo apt-get install libasound2/hardy lib32asound2/hardy libasound2-dev/hardy lib32asound2-dev/hardy libasound2-plugins/hardy
If this doesn't help, please post the output of $ dpkg -l | grep asound
Auslegung
May 13th, 2008, 11:15 AM
I've done everything in your How-to and when I make a call in Skype, I still sound like a retarded robot. Not sure if your how-to was meant to address that issue, but I had hoped so. Any ideas? I've spent hours changing the Volume Control alsamixer thing, so any ideas outside of that?
psyke83
May 13th, 2008, 11:45 AM
I've done everything in your How-to and when I make a call in Skype, I still sound like a retarded robot. Not sure if your how-to was meant to address that issue, but I had hoped so. Any ideas? I've spent hours changing the Volume Control alsamixer thing, so any ideas outside of that?
Does Skype work properly if pulseaudio isn't running? (You may need to remove /etc/asound.conf temporarily to check)
Auslegung
May 13th, 2008, 12:30 PM
Does Skype work properly if pulseaudio isn't running? (You may need to remove /etc/asound.conf temporarily to check)
Skype was sounding bad before I followed your how-to, and now nothing has changed. At some point you suggest going to Options then Sound Devices and making it pulse audio, but the only option it gives me is /dev/dsp for sound in, sound out, and ringing and there are no other options to change it to. How can I force it to pulse audio?
psyke83
May 13th, 2008, 12:40 PM
Skype was sounding bad before I followed your how-to, and now nothing has changed. At some point you suggest going to Options then Sound Devices and making it pulse audio, but the only option it gives me is /dev/dsp for sound in, sound out, and ringing and there are no other options to change it to. How can I force it to pulse audio?
Did you read the "General Tips" section? It depends on what version of Skype you have; judging from your comment about /dev/dsp it is the OSS version.
For the OSS version, you need to run the padsp wrapper, i.e. "padsp skype"
For the ALSA version, you need to go to Skype's Options/Sound Devices and select the "pulse" device.
Both versions of Skype work for me; sound playback (e.g. login, dialing sounds) is fine, but I get the "robotic voice" problem when playing back recorded audio. However, that problem existed for me even before PulseAudio was installed. My laptop is dual-boot and I notice poor quality Skype playback (test123) in Ubuntu - even without PulseAudio. On XP it's much better. I wonder if this has anything to do with it; Linux version: 2.0.0.68, Windows version: 3.8
Auslegung
May 13th, 2008, 01:06 PM
Did you read the "General Tips" section? It depends on what version of Skype you have; judging from your comment about /dev/dsp it is the OSS version.
For the OSS version, you need to run the padsp wrapper, i.e. "padsp skype"
For the ALSA version, you need to go to Skype's Options/Sound Devices and select the "pulse" device.
Both versions of Skype work for me; sound playback (e.g. login, dialing sounds) is fine, but I get the "robotic voice" problem when playing back recorded audio. However, that problem existed for me even before PulseAudio was installed. My laptop is dual-boot and I notice poor quality Skype playback (test123) in Ubuntu - even without PulseAudio. On XP it's much better. I wonder if this has anything to do with it; Linux version: 2.0.0.68, Windows version: 3.8
Yes, I read the general comments and tried the padsa or whatever. Same thing. I've tried Skype static, OSS, regular, everything that's in Synaptic and it's all the same. I'd really like to get rid of my cell phone and it's enormous bill and use only Skype, but Skype seems hell-bent on preventing me from ever using it.
soulone
May 13th, 2008, 02:27 PM
Both versions of Skype work for me; sound playback (e.g. login, dialing sounds) is fine, but I get the "robotic voice" problem when playing back recorded audio. However, that problem existed for me even before PulseAudio was installed. My laptop is dual-boot and I notice poor quality Skype playback (test123) in Ubuntu - even without PulseAudio. On XP it's much better. I wonder if this has anything to do with it; Linux version: 2.0.0.68, Windows version: 3.8
I too have the "robotic voice" problem. But it happens after I switched from 7.10 to 8.04. In Gutsy I use ALSA and Skype works pretty, so I'm sure it's caused by the new Pulse Audio system.
Though both version of Skype running but problem persists, I've tried every step in the first post but in vain.
Anyone knows any answer?
Grone1985
May 14th, 2008, 07:44 PM
Ok... So I tried what you suggested but I get this... and I don't really know if I should downgrade those files...
maitreyi@maitreyi-laptop:~$ sudo apt-get install libasound2/hardy lib32asound2/hardy libasound2-dev/hardy lib32asound2-dev/hardy libasound2-plugins/hardy
Reading package lists... Done
Building dependency tree
Reading state information... Done
Selected version 1.0.15-3ubuntu4 (Ubuntu:8.04/hardy) for libasound2
Selected version 1.0.15-3ubuntu4 (Ubuntu:8.04/hardy) for lib32asound2
Selected version 1.0.15-3ubuntu4 (Ubuntu:8.04/hardy) for libasound2-dev
Selected version 1.0.15-3ubuntu4 (Ubuntu:8.04/hardy) for lib32asound2-dev
Selected version 1.0.15-1ubuntu3 (Ubuntu:8.04/hardy) for libasound2-plugins
Suggested packages:
libasound2-doc
The following packages will be DOWNGRADED:
lib32asound2 lib32asound2-dev libasound2 libasound2-dev libasound2-plugins
0 upgraded, 0 newly installed, 5 downgraded, 0 to remove and 0 not upgraded.
Need to get 1494kB/1811kB of archives.
After this operation, 20.5kB of additional disk space will be used.
Do you want to continue [Y/n]?
Let me know, thanks!
psyke83
May 14th, 2008, 07:50 PM
Ok... So I tried what you suggested but I get this... and I don't really know if I should downgrade those files...
maitreyi@maitreyi-laptop:~$ sudo apt-get install libasound2/hardy lib32asound2/hardy libasound2-dev/hardy lib32asound2-dev/hardy libasound2-plugins/hardy
Reading package lists... Done
Building dependency tree
Reading state information... Done
Selected version 1.0.15-3ubuntu4 (Ubuntu:8.04/hardy) for libasound2
Selected version 1.0.15-3ubuntu4 (Ubuntu:8.04/hardy) for lib32asound2
Selected version 1.0.15-3ubuntu4 (Ubuntu:8.04/hardy) for libasound2-dev
Selected version 1.0.15-3ubuntu4 (Ubuntu:8.04/hardy) for lib32asound2-dev
Selected version 1.0.15-1ubuntu3 (Ubuntu:8.04/hardy) for libasound2-plugins
Suggested packages:
libasound2-doc
The following packages will be DOWNGRADED:
lib32asound2 lib32asound2-dev libasound2 libasound2-dev libasound2-plugins
0 upgraded, 0 newly installed, 5 downgraded, 0 to remove and 0 not upgraded.
Need to get 1494kB/1811kB of archives.
After this operation, 20.5kB of additional disk space will be used.
Do you want to continue [Y/n]?
Let me know, thanks!
Well, do you want to restore your system to its original state, i.e. before you tried this guide?
If you want to restore PulseAudio to its original state:
a) yes, allow the packages to be downgraded, then:
b) $ sudo dpkg -P --force-depends pulseaudio
$ sudo apt-get install pulseaudio
$ sudo rm /etc/asound.conf
Grone1985
May 14th, 2008, 11:31 PM
What I want is to install libasound.so.2 which is what I was going to do (as you suggested me to do) when I got that message. In other words... What I want is to try Skype to see if this guide helps the sound problems but I can't because it says that it's missing libasound.so.2... Can I do that without downgrading all those files?
Thanks!
psyke83
May 15th, 2008, 09:47 AM
What I want is to install libasound.so.2 which is what I was going to do (as you suggested me to do) when I got that message. In other words... What I want is to try Skype to see if this guide helps the sound problems but I can't because it says that it's missing libasound.so.2... Can I do that without downgrading all those files?
Thanks!
Can you try following "Appendix 2: Removal Instructions", then checking if your system works normally (i.e. *before* you used this HOWTO)?
If you no longer get errors about libasound.so.2, you can try starting the guide again from scratch.
psyke83
May 15th, 2008, 09:50 AM
Hi everyone,
I re-wrote "Part B" to fix Flash*. A better solution is to install the beta version (10) of the plugin from Adobe Labs (http://labs.adobe.com). I have provided the upgraded "flashplugin-nonfree" package as I don't expect Hardy to get this update for some time (more than likely they would wait for version 10 final). If you already followed this HOWTO previously, you just need to run through Part B again.
*Still I386 only, sorry.
ferrarix
May 15th, 2008, 10:26 AM
So I followed the whole tutorial. That per se works but Skype is still giving me problems.
I configured Skype to use Pulse instead and that solved the "Problem with audio playback" message, but it only gives off sound for a split of a second at the very beginning and then nothing.
I tried the static oss version together with the "padsp" thing. Still no use.
I need Skype because family and friends are on it. Impossible to convert them all on to Ekiga.
The only part of this tutorial which I didn't follow was Part D, as I'm not a laptop user.
Moreover, when I close Skype now, it hangs and I'd have to kill the process. This happens both on the normal version and the satic OSS version.
Any ideas anyone please? I "fell in love" with Ubuntu but this thing is really bugging me right now.
My specifications:
ASUS P4V8X-X Motherboard
450Watts PSU
Intel Pentium 4 3.00GHz HT (Dual-Core)
1GB DDR400 PC3200 RAM (1 module)
Gainward NVIDIA GeForce 6200
AC'97 Audio Chipset, built-in
No overclocking
Other sounds work fine (ex. MP3 playback).
Thanks.
psyke83
May 15th, 2008, 10:32 AM
Moreover, when I close Skype now, it hangs and I'd have to kill the process. This happens both on the normal version and the satic OSS version.
Any ideas anyone please? I "fell in love" with Ubuntu but this thing is really bugging me right now.
Did you follow the "optional" step in Part C? On my system, Skype tends to skip *a lot* (both the ALSA and OSS version) unless I adjust the fragment values.
Can you do me another favour? Install "neverball" and make sure it's using the "libsdl1.2debian-alsa" backend, i.e.:
$ sudo apt-get install neverball libsdl1.2debian-alsa
Launch neverball and let me know if sound works, or if it crashes. That may be a similar problem to Skype.
Thanks!
ferrarix
May 15th, 2008, 12:33 PM
No I haven't done the optional step.
Tried Neverball and it also lacks sound, and just as Skype did, I had to kill the process to be able to close it down.
Gonna try again with the optional step (Part C), and thanks for your help. Will keep you updated. :)
BTW, Do I have to reboot after doing the optional part?
psyke83
May 15th, 2008, 12:41 PM
No I haven't done the optional step.
Tried Neverball and it also lacks sound, and just as Skype did, I had to kill the process to be able to close it down.
Gonna try again with the optional step (Part C), and thanks for your help. Will keep you updated. :)
BTW, Do I have to reboot after doing the optional part?
Restarting the "pulseaudio" process should be enough (i.e. log out and back in).
Just so you know, I experienced crashes with Skype and neverball as well, but the updated libasound2/libasound2-plugins from Debian unstable completely solved that problem. Did you skip Part A, by any chance?
ferrarix
May 15th, 2008, 12:44 PM
So I did the optional part.
The problem remained. There is no change I can detect anywhere. I even rebooted my PC.
What do you think I can do to be able to use Skype?
Thanks.
hyperair
May 15th, 2008, 12:51 PM
Get Skype OSS and run it with "padsp skype" instead of just "skype".
Alternatively, follow this: http://ubuntuforums.org/showpost.php?p=4526841&postcount=10
It's a howto I prepared ages back. Forgot to mention it earlier.
ferrarix
May 15th, 2008, 01:00 PM
I had already done the padsp thing (and done it again now). It doesn't work.
This is what I wrote in the terminal:
-desktop:~/Documents/Software Downloaded/Skype/skype_static-2.0.0.68-oss$ padsp skype
Will look into that link now.
hyperair
May 15th, 2008, 01:04 PM
I had already done the padsp thing (and done it again now). It doesn't work.
This is what I wrote in the terminal:
Will look into that link now.
What was the output? If you don't show the output then nobody can help you with the padsp method.
ferrarix
May 15th, 2008, 01:05 PM
Oh Skype just opened normally. Isn't that what I was supposed to see?
Please bear with me cause I'm still a noob with Ubuntu :).
psyke83
May 15th, 2008, 01:07 PM
So I did the optional part.
The problem remained. There is no change I can detect anywhere. I even rebooted my PC.
What do you think I can do to be able to use Skype?
Thanks.
All I can suggest is you double-check you have installed the Debian unstable packages as mentioned in Part A; the issues you're having were solved for me using those updated packages.
My final suggestion for the moment is:
1. Make sure you've installed the updated packages via Part A.
2. Open a terminal, and kill the current pulseaudio server:
$ pkill pulseaudio
3. Launch pulseaudio in verbose mode:
$ pulseaudio -vv
4. Open a second terminal, launch skype (either the ALSA version, making sure it is configured to use the "pulse" audio device, or the OSS version via "padsp skype").
5. Watch pulseaudio's output on the first terminal, see if any output is related to skype and paste anything you think may be relevant here.
Another idea is to launch the PulseAudio Volume Control and watch to see if Skype or neverball list themselves as Playback clients.
Finally, if nothing else works, try hyperair's guide or KillerKiwi's here: http://ubuntuforums.org/showthread.php?t=790889
Note that each has its advantages and disadvantages: hyperair's configures PulseAudio to use dmix, which introduces extra latency, and KillerKiwi's guide blocks all sound while Skype is using audio. Both should work for you.
hyperair
May 15th, 2008, 01:15 PM
Oh Skype just opened normally. Isn't that what I was supposed to see?
Please bear with me cause I'm still a noob with Ubuntu :).
If you still didn't have sound after using padsp, then you didn't follow what I said about getting Skype OSS. The default version is using ALSA. You need to download Skype static OSS or skype-oss through Medibuntu's repository.
As for neverball, I believe it uses SDL. Make sure you have the Pulseaudio plugin for SDL. The package to be installed is libsdl1.2debian-pulseaudio from the universe repository.
ferrarix
May 15th, 2008, 01:22 PM
@hyperair: I downloaded Skype OSS from here (http://www.skype.com/go/getskype-linux-oss) as I couldn't get the Medibuntu Repository (http://www.medibuntu.org/repository.php) working (I'm on Ubuntu 8.04 Hardy).
@psyke83: Thanks. Will give them a try soon.
psyke83
May 15th, 2008, 01:24 PM
@hyperair: I downloaded Skype OSS from here (http://www.skype.com/go/getskype-linux-oss) as I couldn't get the Medibuntu Repository (http://www.medibuntu.org/repository.php) working (I'm on Ubuntu 8.04 Hardy).
You're looking at an outdated link. This is the most up-to-date: https://help.ubuntu.com/community/Medibuntu
ferrarix
May 15th, 2008, 01:26 PM
This is what I got in verbose mode:
"ALSA plug-in [skype]"
I: client.c: Freed 73 "ALSA plug-in [skype]"
I: protocol-native.c: connection died.
I: client.c: Created 74 "Native client (UNIX socket client)"
I: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
I: protocol-native.c: Enabled SHM for new connection
I: client.c: Client 74 changed name from "Native client (UNIX socket client)" to "ALSA plug-in [skype]"
I: client.c: Freed 74 "ALSA plug-in [skype]"
I: protocol-native.c: connection died.
I: client.c: Created 75 "Native client (UNIX socket client)"
I: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
I: protocol-native.c: Enabled SHM for new connection
I: client.c: Client 75 changed name from "Native client (UNIX socket client)" to "ALSA plug-in [skype]"
I: client.c: Freed 75 "ALSA plug-in [skype]"
I: protocol-native.c: connection died.
I: client.c: Created 76 "Native client (UNIX socket client)"
I: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
I: protocol-native.c: Enabled SHM for new connection
I: client.c: Client 76 changed name from "Native client (UNIX socket client)" to "ALSA plug-in [skype]"
I: client.c: Freed 76 "ALSA plug-in [skype]"
I: protocol-native.c: connection died.
I: client.c: Created 77 "Native client (UNIX socket client)"
I: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
I: protocol-native.c: Enabled SHM for new connection
I: client.c: Client 77 changed name from "Native client (UNIX socket client)" to "ALSA plug-in [skype]"
I: client.c: Freed 77 "ALSA plug-in [skype]"
I: protocol-native.c: connection died.
I: client.c: Created 78 "Native client (UNIX socket client)"
I: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
I: protocol-native.c: Enabled SHM for new connection
I: client.c: Client 78 changed name from "Native client (UNIX socket client)" to "ALSA plug-in [skype]"
I: client.c: Freed 78 "ALSA plug-in [skype]"
I: protocol-native.c: connection died.
I: client.c: Created 79 "Native client (UNIX socket client)"
I: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
I: protocol-native.c: Enabled SHM for new connection
I: client.c: Client 79 changed name from "Native client (UNIX socket client)" to "ALSA plug-in [skype]"
I: client.c: Freed 79 "ALSA plug-in [skype]"
I: protocol-native.c: connection died.
I: client.c: Created 80 "Native client (UNIX socket client)"
I: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
I: protocol-native.c: Enabled SHM for new connection
I: client.c: Client 80 changed name from "Native client (UNIX socket client)" to "ALSA plug-in [skype]"
I: client.c: Freed 80 "ALSA plug-in [skype]"
I: protocol-native.c: connection died.
I: client.c: Created 81 "Native client (UNIX socket client)"
I: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
I: protocol-native.c: Enabled SHM for new connection
I: client.c: Client 81 changed name from "Native client (UNIX socket client)" to "ALSA plug-in [skype]"
I: client.c: Freed 81 "ALSA plug-in [skype]"
I: protocol-native.c: connection died.
I: client.c: Created 82 "Native client (UNIX socket client)"
I: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
I: protocol-native.c: Enabled SHM for new connection
I: client.c: Client 82 changed name from "Native client (UNIX socket client)" to "ALSA plug-in [skype]"
I: client.c: Freed 82 "ALSA plug-in [skype]"
I: protocol-native.c: connection died.
I: client.c: Created 83 "Native client (UNIX socket client)"
I: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
I: protocol-native.c: Enabled SHM for new connection
I: client.c: Client 83 changed name from "Native client (UNIX socket client)" to "ALSA plug-in [skype]"
I: client.c: Freed 83 "ALSA plug-in [skype]"
I: protocol-native.c: connection died.
I: client.c: Created 84 "Native client (UNIX socket client)"
I: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
I: protocol-native.c: Enabled SHM for new connection
I: client.c: Client 84 changed name from "Native client (UNIX socket client)" to "ALSA plug-in [skype]"
I: client.c: Freed 84 "ALSA plug-in [skype]"
I: protocol-native.c: connection died.
I: client.c: Created 85 "Native client (UNIX socket client)"
I: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
I: protocol-native.c: Enabled SHM for new connection
I: client.c: Client 85 changed name from "Native client (UNIX socket client)" to "ALSA plug-in [skype]"
I: client.c: Freed 85 "ALSA plug-in [skype]"
I: protocol-native.c: connection died.
I: client.c: Created 86 "Native client (UNIX socket client)"
I: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
I: protocol-native.c: Enabled SHM for new connection
I: client.c: Client 86 changed name from "Native client (UNIX socket client)" to "ALSA plug-in [skype]"
I: client.c: Freed 86 "ALSA plug-in [skype]"
I: protocol-native.c: connection died.
I: client.c: Created 87 "Native client (UNIX socket client)"
I: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
I: protocol-native.c: Enabled SHM for new connection
I: client.c: Client 87 changed name from "Native client (UNIX socket client)" to "ALSA plug-in [skype]"
I: client.c: Freed 87 "ALSA plug-in [skype]"
I: protocol-native.c: connection died.
I: client.c: Created 88 "Native client (UNIX socket client)"
I: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
I: protocol-native.c: Enabled SHM for new connection
I: client.c: Client 88 changed name from "Native client (UNIX socket client)" to "ALSA plug-in [skype]"
I: client.c: Freed 88 "ALSA plug-in [skype]"
I: protocol-native.c: connection died.
I: client.c: Created 89 "Native client (UNIX socket client)"
I: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
I: protocol-native.c: Enabled SHM for new connection
I: client.c: Client 89 changed name from "Native client (UNIX socket client)" to "ALSA plug-in [skype]"
I: client.c: Freed 89 "ALSA plug-in [skype]"
I: protocol-native.c: connection died.
I: client.c: Created 90 "Native client (UNIX socket client)"
I: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
I: protocol-native.c: Enabled SHM for new connection
I: client.c: Client 90 changed name from "Native client (UNIX socket client)" to "ALSA plug-in [skype]"
I: client.c: Freed 90 "ALSA plug-in [skype]"
I: protocol-native.c: connection died.
I: client.c: Created 91 "Native client (UNIX socket client)"
I: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
I: protocol-native.c: Enabled SHM for new connection
I: client.c: Client 91 changed name from "Native client (UNIX socket client)" to "ALSA plug-in [skype]"
I: client.c: Freed 91 "ALSA plug-in [skype]"
I: protocol-native.c: connection died.
I: client.c: Created 92 "Native client (UNIX socket client)"
I: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
I: protocol-native.c: Enabled SHM for new connection
I: client.c: Client 92 changed name from "Native client (UNIX socket client)" to "ALSA plug-in [skype]"
I: client.c: Freed 92 "ALSA plug-in [skype]"
I: protocol-native.c: connection died.
I: client.c: Created 93 "Native client (UNIX socket client)"
I: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
I: protocol-native.c: Enabled SHM for new connection
I: client.c: Client 93 changed name from "Native client (UNIX socket client)" to "ALSA plug-in [skype]"
I: client.c: Freed 93 "ALSA plug-in [skype]"
I: protocol-native.c: connection died.
I: client.c: Created 94 "Native client (UNIX socket client)"
I: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
I: protocol-native.c: Enabled SHM for new connection
I: client.c: Client 94 changed name from "Native client (UNIX socket client)" to "ALSA plug-in [skype]"
I: client.c: Freed 94 "ALSA plug-in [skype]"
I: protocol-native.c: connection died.
I: client.c: Created 95 "Native client (UNIX socket client)"
I: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
I: protocol-native.c: Enabled SHM for new connection
I: client.c: Client 95 changed name from "Native client (UNIX socket client)" to "ALSA plug-in [skype]"
I: client.c: Freed 95 "ALSA plug-in [skype]"
I: protocol-native.c: connection died.
I: client.c: Created 96 "Native client (UNIX socket client)"
I: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
I: protocol-native.c: Enabled SHM for new connection
I: client.c: Client 96 changed name from "Native client (UNIX socket client)" to "ALSA plug-in [skype]"
I: client.c: Freed 96 "ALSA plug-in [skype]"
I: protocol-native.c: connection died.
I: client.c: Created 97 "Native client (UNIX socket client)"
I: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
I: protocol-native.c: Enabled SHM for new connection
I: client.c: Client 97 changed name from "Native client (UNIX socket client)" to "ALSA plug-in [skype]"
I: client.c: Freed 97 "ALSA plug-in [skype]"
I: protocol-native.c: connection died.
I: client.c: Created 98 "Native client (UNIX socket client)"
I: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
I: protocol-native.c: Enabled SHM for new connection
I: client.c: Client 98 changed name from "Native client (UNIX socket client)" to "ALSA plug-in [skype]"
I: client.c: Freed 98 "ALSA plug-in [skype]"
I: protocol-native.c: connection died.
I: client.c: Created 99 "Native client (UNIX socket client)"
I: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
I: protocol-native.c: Enabled SHM for new connection
I: client.c: Client 99 changed name from "Native client (UNIX socket client)" to "ALSA plug-in [skype]"
I: client.c: Freed 99 "ALSA plug-in [skype]"
I: protocol-native.c: connection died.
I: client.c: Created 100 "Native client (UNIX socket client)"
I: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
I: protocol-native.c: Enabled SHM for new connection
I: client.c: Client 100 changed name from "Native client (UNIX socket client)" to "ALSA plug-in [skype]"
I: client.c: Freed 100 "ALSA plug-in [skype]"
I: protocol-native.c: connection died.
I: client.c: Created 101 "Native client (UNIX socket client)"
I: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
I: protocol-native.c: Enabled SHM for new connection
I: client.c: Client 101 changed name from "Native client (UNIX socket client)" to "ALSA plug-in [skype]"
I: client.c: Freed 101 "ALSA plug-in [skype]"
I: protocol-native.c: connection died.
I: client.c: Created 102 "Native client (UNIX socket client)"
I: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
I: protocol-native.c: Enabled SHM for new connection
I: client.c: Client 102 changed name from "Native client (UNIX socket client)" to "ALSA plug-in [skype]"
I: client.c: Freed 102 "ALSA plug-in [skype]"
I: protocol-native.c: connection died.
I: client.c: Created 103 "Native client (UNIX socket client)"
I: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
I: protocol-native.c: Enabled SHM for new connection
I: client.c: Client 103 changed name from "Native client (UNIX socket client)" to "ALSA plug-in [skype]"
I: client.c: Freed 103 "ALSA plug-in [skype]"
I: protocol-native.c: connection died.
I: client.c: Created 104 "Native client (UNIX socket client)"
I: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
I: protocol-native.c: Enabled SHM for new connection
I: client.c: Client 104 changed name from "Native client (UNIX socket client)" to "ALSA plug-in [skype]"
I: client.c: Freed 104 "ALSA plug-in [skype]"
I: protocol-native.c: connection died.
I: client.c: Created 105 "Native client (UNIX socket client)"
I: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
I: protocol-native.c: Enabled SHM for new connection
I: client.c: Client 105 changed name from "Native client (UNIX socket client)" to "ALSA plug-in [skype]"
I: client.c: Freed 105 "ALSA plug-in [skype]"
I: protocol-native.c: connection died.
I: client.c: Created 106 "Native client (UNIX socket client)"
I: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
I: protocol-native.c: Enabled SHM for new connection
I: client.c: Client 106 changed name from "Native client (UNIX socket client)" to "ALSA plug-in [skype]"
I: client.c: Freed 106 "ALSA plug-in [skype]"
I: protocol-native.c: connection died.
I: client.c: Created 107 "Native client (UNIX socket client)"
I: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
I: protocol-native.c: Enabled SHM for new connection
I: client.c: Client 107 changed name from "Native client (UNIX socket client)" to "ALSA plug-in [skype]"
I: client.c: Freed 107 "ALSA plug-in [skype]"
I: protocol-native.c: connection died.
I: client.c: Created 108 "Native client (UNIX socket client)"
I: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
I: protocol-native.c: Enabled SHM for new connection
I: client.c: Client 108 changed name from "Native client (UNIX socket client)" to "ALSA plug-in [skype]"
I: client.c: Freed 108 "ALSA plug-in [skype]"
I: protocol-native.c: connection died.
I: client.c: Created 109 "Native client (UNIX socket client)"
I: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
I: protocol-native.c: Enabled SHM for new connection
I: client.c: Client 109 changed name from "Native client (UNIX socket client)" to "ALSA plug-in [skype]"
I: client.c: Freed 109 "ALSA plug-in [skype]"
I: protocol-native.c: connection died.
I: client.c: Created 110 "Native client (UNIX socket client)"
I: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
I: protocol-native.c: Enabled SHM for new connection
I: client.c: Client 110 changed name from "Native client (UNIX socket client)" to "ALSA plug-in [skype]"
I: client.c: Freed 110 "ALSA plug-in [skype]"
I: protocol-native.c: connection died.
I: client.c: Created 111 "Native client (UNIX socket client)"
I: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
I: protocol-native.c: Enabled SHM for new connection
I: client.c: Client 111 changed name from "Native client (UNIX socket client)" to "ALSA plug-in [skype]"
I: client.c: Freed 111 "ALSA plug-in [skype]"
I: protocol-native.c: connection died.
I: client.c: Created 112 "Native client (UNIX socket client)"
I: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
I: protocol-native.c: Enabled SHM for new connection
I: client.c: Client 112 changed name from "Native client (UNIX socket client)" to "ALSA plug-in [skype]"
I: client.c: Freed 112 "ALSA plug-in [skype]"
I: protocol-native.c: connection died.
I: client.c: Created 113 "Native client (UNIX socket client)"
I: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
I: protocol-native.c: Enabled SHM for new connection
I: client.c: Client 113 changed name from "Native client (UNIX socket client)" to "ALSA plug-in [skype]"
I: client.c: Freed 113 "ALSA plug-in [skype]"
I: protocol-native.c: connection died.
I: client.c: Created 114 "Native client (UNIX socket client)"
I: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
I: protocol-native.c: Enabled SHM for new connection
I: client.c: Client 114 changed name from "Native client (UNIX socket client)" to "ALSA plug-in [skype]"
I: client.c: Freed 114 "ALSA plug-in [skype]"
I: protocol-native.c: connection died.
I: client.c: Created 115 "Native client (UNIX socket client)"
I: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
I: protocol-native.c: Enabled SHM for new connection
I: client.c: Client 115 changed name from "Native client (UNIX socket client)" to "ALSA plug-in [skype]"
I: client.c: Freed 115 "ALSA plug-in [skype]"
I: protocol-native.c: connection died.
I: client.c: Created 116 "Native client (UNIX socket client)"
I: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
I: protocol-native.c: Enabled SHM for new connection
I: client.c: Client 116 changed name from "Native client (UNIX socket client)" to "ALSA plug-in [skype]"
I: client.c: Freed 116 "ALSA plug-in [skype]"
I: protocol-native.c: connection died.
I: client.c: Created 117 "Native client (UNIX socket client)"
I: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
I: protocol-native.c: Enabled SHM for new connection
I: client.c: Client 117 changed name from "Native client (UNIX socket client)" to "ALSA plug-in [skype]"
I: client.c: Freed 117 "ALSA plug-in [skype]"
I: protocol-native.c: connection died.
I: client.c: Created 118 "Native client (UNIX socket client)"
I: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
I: protocol-native.c: Enabled SHM for new connection
I: client.c: Client 118 changed name from "Native client (UNIX socket client)" to "ALSA plug-in [skype]"
I: client.c: Freed 118 "ALSA plug-in [skype]"
I: protocol-native.c: connection died.
I: client.c: Created 119 "Native client (UNIX socket client)"
I: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
I: protocol-native.c: Enabled SHM for new connection
I: client.c: Client 119 changed name from "Native client (UNIX socket client)" to "ALSA plug-in [skype]"
I: client.c: Freed 119 "ALSA plug-in [skype]"
I: protocol-native.c: connection died.
I: client.c: Created 120 "Native client (UNIX socket client)"
I: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
I: protocol-native.c: Enabled SHM for new connection
I: client.c: Client 120 changed name from "Native client (UNIX socket client)" to "ALSA plug-in [skype]"
I: client.c: Freed 120 "ALSA plug-in [skype]"
I: protocol-native.c: connection died.
I: client.c: Created 121 "Native client (UNIX socket client)"
I: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
I: protocol-native.c: Enabled SHM for new connection
I: client.c: Client 121 changed name from "Native client (UNIX socket client)" to "ALSA plug-in [skype]"
I: client.c: Freed 121 "ALSA plug-in [skype]"
I: protocol-native.c: connection died.
I: client.c: Created 122 "Native client (UNIX socket client)"
I: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
I: protocol-native.c: Enabled SHM for new connection
I: client.c: Client 122 changed name from "Native client (UNIX socket client)" to "ALSA plug-in [skype]"
I: client.c: Freed 122 "ALSA plug-in [skype]"
I: protocol-native.c: connection died.
I: client.c: Created 123 "Native client (UNIX socket client)"
I: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
I: protocol-native.c: Enabled SHM for new connection
I: client.c: Client 123 changed name from "Native client (UNIX socket client)" to "ALSA plug-in [skype]"
I: client.c: Freed 123 "ALSA plug-in [skype]"
I: protocol-native.c: connection died.
I: client.c: Created 124 "Native client (UNIX socket client)"
I: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
I: protocol-native.c: Enabled SHM for new connection
I: client.c: Client 124 changed name from "Native client (UNIX socket client)" to "ALSA plug-in [skype]"
I: client.c: Freed 124 "ALSA plug-in [skype]"
I: protocol-native.c: connection died.
I: client.c: Created 125 "Native client (UNIX socket client)"
I: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
I: protocol-native.c: Enabled SHM for new connection
I: client.c: Client 125 changed name from "Native client (UNIX socket client)" to "ALSA plug-in [skype]"
I: client.c: Freed 125 "ALSA plug-in [skype]"
I: protocol-native.c: connection died.
I: client.c: Created 126 "Native client (UNIX socket client)"
I: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
I: protocol-native.c: Enabled SHM for new connection
I: client.c: Client 126 changed name from "Native client (UNIX socket client)" to "ALSA plug-in [skype]"
I: client.c: Freed 126 "ALSA plug-in [skype]"
I: protocol-native.c: connection died.
I: client.c: Created 127 "Native client (UNIX socket client)"
I: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
I: protocol-native.c: Enabled SHM for new connection
I: client.c: Client 127 changed name from "Native client (UNIX socket client)" to "ALSA plug-in [skype]"
I: client.c: Freed 127 "ALSA plug-in [skype]"
I: protocol-native.c: connection died.
I: client.c: Created 128 "Native client (UNIX socket client)"
I: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
I: protocol-native.c: Enabled SHM for new connection
I: client.c: Client 128 changed name from "Native client (UNIX socket client)" to "ALSA plug-in [skype]"
I: client.c: Freed 128 "ALSA plug-in [skype]"
I: protocol-native.c: connection died.
I: client.c: Created 129 "Native client (UNIX socket client)"
I: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
I: protocol-native.c: Enabled SHM for new connection
I: client.c: Client 129 changed name from "Native client (UNIX socket client)" to "ALSA plug-in [skype]"
I: client.c: Freed 129 "ALSA plug-in [skype]"
I: protocol-native.c: connection died.
I: client.c: Created 130 "Native client (UNIX socket client)"
I: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
I: protocol-native.c: Enabled SHM for new connection
I: client.c: Client 130 changed name from "Native client (UNIX socket client)" to "ALSA plug-in [skype]"
I: client.c: Freed 130 "ALSA plug-in [skype]"
I: protocol-native.c: connection died.
I: client.c: Created 131 "Native client (UNIX socket client)"
I: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
I: protocol-native.c: Enabled SHM for new connection
I: client.c: Client 131 changed name from "Native client (UNIX socket client)" to "ALSA plug-in [skype]"
I: client.c: Freed 131 "ALSA plug-in [skype]"
I: protocol-native.c: connection died.
I: client.c: Created 132 "Native client (UNIX socket client)"
I: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
I: protocol-native.c: Enabled SHM for new connection
I: client.c: Client 132 changed name from "Native client (UNIX socket client)" to "ALSA plug-in [skype]"
I: client.c: Freed 132 "ALSA plug-in [skype]"
I: protocol-native.c: connection died.
I: client.c: Created 133 "Native client (UNIX socket client)"
I: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
I: protocol-native.c: Enabled SHM for new connection
I: client.c: Client 133 changed name from "Native client (UNIX socket client)" to "ALSA plug-in [skype]"
I: client.c: Freed 133 "ALSA plug-in [skype]"
I: protocol-native.c: connection died.
I: client.c: Created 134 "Native client (UNIX socket client)"
I: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
I: protocol-native.c: Enabled SHM for new connection
I: client.c: Client 134 changed name from "Native client (UNIX socket client)" to "ALSA plug-in [skype]"
I: client.c: Freed 134 "ALSA plug-in [skype]"
I: protocol-native.c: connection died.
I: client.c: Created 135 "Native client (UNIX socket client)"
I: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
I: protocol-native.c: Enabled SHM for new connection
I: client.c: Client 135 changed name from "Native client (UNIX socket client)" to "ALSA plug-in [skype]"
I: client.c: Freed 135 "ALSA plug-in [skype]"
I: protocol-native.c: connection died.
D: module-suspend-on-idle.c: Source alsa_input.pci_1106_3059_sound_card_0_alsa_capture _0 becomes idle.
I: client.c: Created 136 "Native client (UNIX socket client)"
I: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
I: protocol-native.c: Enabled SHM for new connection
I: client.c: Client 136 changed name from "Native client (UNIX socket client)" to "ALSA plug-in [skype]"
I: client.c: Freed 136 "ALSA plug-in [skype]"
I: protocol-native.c: connection died.
D: module-suspend-on-idle.c: Source alsa_input.pci_1106_3059_sound_card_0_alsa_capture _0 becomes idle.
I: source-output.c: Freeing output 0 "ALSA Capture"
I: client.c: Freed 18 "ALSA plug-in [skype]"
I: protocol-native.c: connection died.
I: client.c: Created 137 "Native client (UNIX socket client)"
I: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
I: protocol-native.c: Enabled SHM for new connection
I: client.c: Client 137 changed name from "Native client (UNIX socket client)" to "ALSA plug-in [skype]"
I: client.c: Freed 137 "ALSA plug-in [skype]"
I: protocol-native.c: connection died.
I: client.c: Created 138 "Native client (UNIX socket client)"
I: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
I: protocol-native.c: Enabled SHM for new connection
I: client.c: Client 138 changed name from "Native client (UNIX socket client)" to "ALSA plug-in [skype]"
I: client.c: Freed 138 "ALSA plug-in [skype]"
I: protocol-native.c: connection died.
I: client.c: Created 139 "Native client (UNIX socket client)"
I: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
I: protocol-native.c: Enabled SHM for new connection
I: client.c: Client 139 changed name from "Native client (UNIX socket client)" to "ALSA plug-in [skype]"
I: client.c: Freed 139 "ALSA plug-in [skype]"
I: protocol-native.c: connection died.
I: client.c: Created 140 "Native client (UNIX socket client)"
I: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
I: protocol-native.c: Enabled SHM for new connection
I: client.c: Client 140 changed name from "Native client (UNIX socket client)" to "ALSA plug-in [skype]"
I: client.c: Freed 140 "ALSA plug-in [skype]"
I: protocol-native.c: connection died.
I: client.c: Created 141 "Native client (UNIX socket client)"
I: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
I: protocol-native.c: Enabled SHM for new connection
I: client.c: Client 141 changed name from "Native client (UNIX socket client)" to "ALSA plug-in [skype]"
I: client.c: Freed 141 "ALSA plug-in [skype]"
I: protocol-native.c: connection died.
I: module-suspend-on-idle.c: Source alsa_input.pci_1106_3059_sound_card_0_alsa_capture _0 idle for too long, suspending ...
I: module-alsa-source.c: Device suspended...
D: module-suspend-on-idle.c: Sink alsa_output.pci_1106_3059_sound_card_0_alsa_playba ck_0 becomes idle.
D: module-suspend-on-idle.c: Sink alsa_output.pci_1106_3059_sound_card_0_alsa_playba ck_0 becomes idle.
I: sink-input.c: Freeing output 0 "ALSA Playback"
I: client.c: Freed 15 "ALSA plug-in [skype]"
I: protocol-native.c: connection died.
I: module-suspend-on-idle.c: Sink alsa_output.pci_1106_3059_sound_card_0_alsa_playba ck_0 idle for too long, suspending ...
I: module-alsa-sink.c: Device suspended...
psyke83
May 15th, 2008, 01:27 PM
As for neverball, I believe it uses SDL. Make sure you have the Pulseaudio plugin for SDL. The package to be installed is libsdl1.2debian-pulseaudio from the universe repository.
Can you do me a favour? Intentionally install libsdl1.2debian-alsa, make sure you've followed Part A, and see if neverball works with PulseAudio (after restarting pulseaudio). It seems the ALSA pcm_pulse plugin can redirect SDL applications without even requiring libsdl1.2debian-pulseaudio, but it requires the updated Debian unstable packages.
You'll do me a big favour to verify this, so I can report it on the relevant bug reports.
hyperair
May 15th, 2008, 01:28 PM
As far as I know, Skype and Pulseaudio's ALSA plugin never worked with Ubuntu Hardy. Not once. You'd see Skype in the clients list, but you won't hear sound.
@psyke83: Sorry, but I'm on Archlinux at the moment. However, I agree with you that ALSA's pcm_pulse plugin can redirect SDL applications successfully. However, sound is choppy. I've tested this with Frozen Bubble both on Ubuntu and ArchLinux.
MemoryDump
May 15th, 2008, 01:30 PM
I have 2 soundcards. (Audigy2 and a onboard device)
How do I set 1 to use Pulse and the other to use Alsa (or whatever)? or can both use pulse while keeping sounds separate?
Right now I have my Audigy2 hooked up to my speakers and everything "seems" to be working properly.
Now what I want to do/setup is that my second sound card strictly for my headset/mic. (voip chat and ventrilo)
As you can see by the attached screenshots it lists how my sound properties are set for my speakers (Sound Events & Music and Movies). I also have some settings set for my Audio Conference. Now using OSS as it shows I can hear the test sounds in my headset, however no matter what setting I choose in the dropdown for Sound capture I don't hear anything. I tried the "Test Sound" option and that did work where I could here sound in my headset.
I've been through every sound level screen I could find to make sure MIC was enabled and volume levels were maxed out.
I REALLY need help with this! I've been pulling my hair out ever since I upgraded to 8.04 with Pulse and haven't had much luck :(
This WAS working under Gutsy.
aplay -l
aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: ICH5 [Intel ICH5], device 0: Intel ICH [Intel ICH5]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: ICH5 [Intel ICH5], device 4: Intel ICH - IEC958 [Intel ICH5 - IEC958]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: Audigy2 [Audigy 2 ZS [SB0350]], device 0: emu10k1 [ADC Capture/Standard PCM Playback]
Subdevices: 32/32
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
Subdevice #2: subdevice #2
Subdevice #3: subdevice #3
Subdevice #4: subdevice #4
Subdevice #5: subdevice #5
Subdevice #6: subdevice #6
Subdevice #7: subdevice #7
Subdevice #8: subdevice #8
Subdevice #9: subdevice #9
Subdevice #10: subdevice #10
Subdevice #11: subdevice #11
Subdevice #12: subdevice #12
Subdevice #13: subdevice #13
Subdevice #14: subdevice #14
Subdevice #15: subdevice #15
Subdevice #16: subdevice #16
Subdevice #17: subdevice #17
Subdevice #18: subdevice #18
Subdevice #19: subdevice #19
Subdevice #20: subdevice #20
Subdevice #21: subdevice #21
Subdevice #22: subdevice #22
Subdevice #23: subdevice #23
Subdevice #24: subdevice #24
Subdevice #25: subdevice #25
Subdevice #26: subdevice #26
Subdevice #27: subdevice #27
Subdevice #28: subdevice #28
Subdevice #29: subdevice #29
Subdevice #30: subdevice #30
Subdevice #31: subdevice #31
card 1: Audigy2 [Audigy 2 ZS [SB0350]], device 2: emu10k1 efx [Multichannel Capture/PT Playback]
Subdevices: 8/8
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
Subdevice #2: subdevice #2
Subdevice #3: subdevice #3
Subdevice #4: subdevice #4
Subdevice #5: subdevice #5
Subdevice #6: subdevice #6
Subdevice #7: subdevice #7
card 1: Audigy2 [Audigy 2 ZS [SB0350]], device 3: emu10k1 [Multichannel Playback]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: Audigy2 [Audigy 2 ZS [SB0350]], device 4: p16v [p16v]
Subdevices: 1/1
Subdevice #0: subdevice #0
arecord -l
arecord -l
**** List of CAPTURE Hardware Devices ****
card 0: ICH5 [Intel ICH5], device 0: Intel ICH [Intel ICH5]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: ICH5 [Intel ICH5], device 1: Intel ICH - MIC ADC [Intel ICH5 - MIC ADC]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: ICH5 [Intel ICH5], device 2: Intel ICH - MIC2 ADC [Intel ICH5 - MIC2 ADC]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: ICH5 [Intel ICH5], device 3: Intel ICH - ADC2 [Intel ICH5 - ADC2]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: Audigy2 [Audigy 2 ZS [SB0350]], device 0: emu10k1 [ADC Capture/Standard PCM Playback]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: Audigy2 [Audigy 2 ZS [SB0350]], device 1: emu10k1 mic [Mic Capture]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: Audigy2 [Audigy 2 ZS [SB0350]], device 2: emu10k1 efx [Multichannel Capture/PT Playback]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: Audigy2 [Audigy 2 ZS [SB0350]], device 4: p16v [p16v]
Subdevices: 1/1
Subdevice #0: subdevice #0
ANY help will be greatly appreciated !! :D
ferrarix
May 15th, 2008, 01:30 PM
@psyke83: I already have it installed, together with all of Part A of your first post and the sound doesn't work.
Will check the repository.
hyperair
May 15th, 2008, 01:40 PM
I have 2 soundcards. (Audigy2 and a onboard device)
How do I set 1 to use Pulse and the other to use Alsa (or whatever)? or can both use pulse while keeping sounds separate?
Right now I have my Audigy2 hooked up to my speakers and everything "seems" to be working properly.
Now what I want to do/setup is that my second sound card strictly for my headset/mic. (voip chat and ventrilo)
As you can see by the attached screenshots it lists how my sound properties are set for my speakers (Sound Events & Music and Movies). I also have some settings set for my Audio Conference. Now using OSS as it shows I can hear the test sounds in my headset, however no matter what setting I choose in the dropdown for Sound capture I don't hear anything. I tried the "Test Sound" option and that did work where I could here sound in my headset.
I've been through every sound level screen I could find to make sure MIC was enabled and volume levels were maxed out.
I REALLY need help with this! I've been pulling my hair out ever since I upgraded to 8.04 with Pulse and haven't had much luck :(
This WAS working under Gutsy.
aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: ICH5 [Intel ICH5], device 0: Intel ICH [Intel ICH5]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: ICH5 [Intel ICH5], device 4: Intel ICH - IEC958 [Intel ICH5 - IEC958]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: Audigy2 [Audigy 2 ZS [SB0350]], device 0: emu10k1 [ADC Capture/Standard PCM Playback]
Subdevices: 32/32
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
Subdevice #2: subdevice #2
Subdevice #3: subdevice #3
Subdevice #4: subdevice #4
Subdevice #5: subdevice #5
Subdevice #6: subdevice #6
Subdevice #7: subdevice #7
Subdevice #8: subdevice #8
Subdevice #9: subdevice #9
Subdevice #10: subdevice #10
Subdevice #11: subdevice #11
Subdevice #12: subdevice #12
Subdevice #13: subdevice #13
Subdevice #14: subdevice #14
Subdevice #15: subdevice #15
Subdevice #16: subdevice #16
Subdevice #17: subdevice #17
Subdevice #18: subdevice #18
Subdevice #19: subdevice #19
Subdevice #20: subdevice #20
Subdevice #21: subdevice #21
Subdevice #22: subdevice #22
Subdevice #23: subdevice #23
Subdevice #24: subdevice #24
Subdevice #25: subdevice #25
Subdevice #26: subdevice #26
Subdevice #27: subdevice #27
Subdevice #28: subdevice #28
Subdevice #29: subdevice #29
Subdevice #30: subdevice #30
Subdevice #31: subdevice #31
card 1: Audigy2 [Audigy 2 ZS [SB0350]], device 2: emu10k1 efx [Multichannel Capture/PT Playback]
Subdevices: 8/8
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
Subdevice #2: subdevice #2
Subdevice #3: subdevice #3
Subdevice #4: subdevice #4
Subdevice #5: subdevice #5
Subdevice #6: subdevice #6
Subdevice #7: subdevice #7
card 1: Audigy2 [Audigy 2 ZS [SB0350]], device 3: emu10k1 [Multichannel Playback]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: Audigy2 [Audigy 2 ZS [SB0350]], device 4: p16v [p16v]
Subdevices: 1/1
Subdevice #0: subdevice #0
ANY help will be greatly appreciated !! :D
One of PulseAudio's major features is the ability to switch from sound sink to sound sink transparently. Since you have an Audigy you shouldn't have a problem with Skype, as that supports hardware mixing. Just configure Skype to use the Audigy, and use PulseAudio with its default settings. Then using pavucontrol, select which sink you want to use.
MemoryDump
May 15th, 2008, 01:51 PM
thanks for the quick reply.
I'm not using Skype, but even if I were, the Pulse manager only seems to see my Audigy2 card. This is perhaps where I'm having the biggest problem understanding.. how in fact this manager works and how you add more devices to it.. or even how to configure them individually. :(
One of PulseAudio's major features is the ability to switch from sound sink to sound sink transparently. Since you have an Audigy you shouldn't have a problem with Skype, as that supports hardware mixing. Just configure Skype to use the Audigy, and use PulseAudio with its default settings. Then using pavucontrol, select which sink you want to use.
psyke83
May 15th, 2008, 01:54 PM
As far as I know, Skype and Pulseaudio's ALSA plugin never worked with Ubuntu Hardy. Not once. You'd see Skype in the clients list, but you won't hear sound.
I noticed the same, but Debian unstable's libasound2/libasound2-plugins versions actually work.
@psyke83: Sorry, but I'm on Archlinux at the moment. However, I agree with you that ALSA's pcm_pulse plugin can redirect SDL applications successfully. However, sound is choppy. I've tested this with Frozen Bubble both on Ubuntu and ArchLinux.
I believe I know why that is. SDL applications using libsdl1.2debian-alsa appear to quickly open and close hundreds of PulseAudio connections per minute. Sounds actually works, but it can be choppy. Using libsdl1.2debian-pulseaudio, just one (stable) connection is opened.
I notice the same behaviour with Skype (ALSA), which may explain the choppy sound. It seems there are still bugs remaining in libasound2-plugins, therefore. Hopefully if someone can confirm this behaviour for me, we can make some progress in getting it fixed.
hyperair
May 15th, 2008, 01:58 PM
I noticed the same, but Debian unstable's libasound2/libasound2-plugins versions actually work.
I believe I know why that is. SDL applications using libsdl1.2debian-alsa appear to quickly open and close hundreds of PulseAudio connections per minute. Sounds actually works, but it can be choppy. Using libsdl1.2debian-pulseaudio, just one (stable) connection is opened.
I notice the same behaviour with Skype (ALSA), which may explain the choppy sound. It seems there are still bugs remaining in libasound2-plugins, therefore. Hopefully if someone can confirm this behaviour for me, we can make some progress in getting it fixed.
Awesome! Wait, let me try it out over here. If it happens on Archlinux as well then it's definitely an upstream bug ;)
thanks for the quick reply.
I'm not using Skype, but even if I were, the Pulse manager only seems to see my Audigy2 card. This is perhaps where I'm having the biggest problem understanding.. how in fact this manager works and how you add more devices to it.. or even how to configure them individually. :(
Make sure you have module-hal-detect enabled in your /etc/pulse/default.pa
psyke83
May 15th, 2008, 02:10 PM
Awesome! Wait, let me try it out over here. If it happens on Archlinux as well then it's definitely an upstream bug ;)
Please see here: http://packages.debian.org/changelogs/pool/main/a/alsa-plugins/alsa-plugins_1.0.16-1/changelog
It's entirely possible that upstream do not have the fixes required to make Skype function, as Debian seems to have applied custom patches. You may want to check Debian's diff in case you get disappointed with the result on Arch ;).
ferrarix
May 15th, 2008, 02:29 PM
I re-installed Skype OSS using your Medibuntu Repository link. Works now :).
The only problem that remains is the shaky sound. Did the optional Part and still didn't solve it. Any ideas? At least I'm happy I'm getting somewhere :D.
Thanks.
hyperair
May 15th, 2008, 02:29 PM
You were right about the multiple connections thing. When I tried initiating a call, it opened and closed 55 connections. Then it stopped and complained of a prob with audio playback.
psyke83
May 15th, 2008, 02:47 PM
You were right about the multiple connections thing. When I tried initiating a call, it opened and closed 55 connections. Then it stopped and complained of a prob with audio playback.
Did you make sure to manually set "pulse" for all the options in Options/Sound Devices? If it's set to "default", then PulseAudio will not pick it up properly (even though the "default" device should map to PulseAudio). I have the problem of multiple connections, but only see the "Problem with audio playback" message if the proper "pulse" device is not set.
I tried running Fedora 9 and added the proper asound.conf (from Part A), and Skype works correctly when set to the "pulse" device. it's choppy, although I presume it's due to the "multiple connections" bug.
ferrarix
May 15th, 2008, 02:58 PM
So any ideas on how to solve the choppy sound (multiple connections) problem?
I'm still new at this, but different (maybe even older) versions of Pulse can help? Or some other audio controller?
psyke83
May 15th, 2008, 03:00 PM
So any ideas on how to solve the choppy sound (multiple connections) problem?
I'm still new at this, but different (maybe even older) versions of Pulse can help? Or some other audio controller?
You can try tweaking the fragment values (Part C, optional step) or try one the alternative guides mentioned before.
Hopefully this bug will get fixed, though.
hyperair
May 15th, 2008, 03:14 PM
My word, you're right! O_o IT WORKED! But I took a look at pavucontrol, and Skype kept blinking! That means the bug is in libasound then?
ferrarix
May 15th, 2008, 03:34 PM
So I modified the daemon.conf file to make it as best as possible. It's not perfect but it's loads better. The only problem is when I hear my own voice back (Skype Test call). That is very choppy but it could be because the choppy effect is acting twice (one for sending my voice and another time when I listen back to it).
Anyway, here is my updated code:
; default-fragments = 4
; default-fragment-size-msec = 0.05
Hope it helps :)
I won't be able to stay longer here tonight, but I'll come and check back for updates tomorrow morning. See ya and thanks for all the help :).
psyke83
May 15th, 2008, 03:57 PM
Anyway, here is my updated code:
; default-fragments = 4
; default-fragment-size-msec = 0.05
Hope it helps :).
Just so you know, the character " ; " is the comment code, meaning that it causes those lines to get completely ignored... Therefore you're using the default PulseAudio values.
ferrarix
May 16th, 2008, 03:27 AM
Just so you know, the character " ; " is the comment code, meaning that it causes those lines to get completely ignored... Therefore you're using the default PulseAudio values.
Oh I'm so much of a noob! I imagined that but when I saw that the whole file was like that, I thought that that was the way Pulse works.
Thanks, will give a try. Then I simply imagined the change? lol.
ferrarix
May 16th, 2008, 09:13 AM
default-fragments = 8
default-fragment-size-msec = 5
So I re-modified it and did it like this. The incoming sound works perfect :D but when it comes for me to hear my own voice (Skype Call test service), the sound is completely distorted, making my voice impossible to understand. The microphone works fine, it's part of a Labtec headset I bought around 4 weeks ago and Sound Recorder records my voice well.
Any idea, how can I fix the last step remaining please?
Thanks in advance.
BTW, my Internet connection is working fine as well so it's not a connection problem.
http://www.speedtest.net/result/272121736.png
ADD: Ok found what is the problem on my sent voice, but I'm completely clueless as to how I'm supposed to fix it.
Look at this screenshot I just took and you'll see that there is a high sent packet loss (shown with the arrow).
http://img84.imageshack.us/img84/6553/skypeprobkz6.png
hyperair
May 16th, 2008, 09:18 AM
default-fragments = 8
default-fragment-size-msec = 5
So I re-modified it and did it like this. The incoming sound works perfect :D but when it comes for me to hear my own voice (Skype Call test service), the sound is completely distorted, making my voice impossible to understand. The microphone works fine, it's part of a Labtec headset I bought around 4 weeks ago and Sound Recorder records my voice well.
Any idea, how can I fix the last step remaining please?
Thanks in advance.
BTW, my Internet connection is working fine as well so it's not a connection problem.
http://www.speedtest.net/result/272121736.png
Experiment with your "Sound In" device. It doesn't need to use pulse.
psyke83
May 16th, 2008, 01:23 PM
Any idea, how can I fix the last step remaining please?
Look at this screenshot I just took and you'll see that there is a high sent packet loss (shown with the arrow).
Unfortunately packet loss *does* mean it is also a network issue (at least partially). Skype uses a custom P2P network (based on the old Kazaa filesharing network) and it can be affected by restrictive routers, ISP throttling, etc. Make sure your router has UDP configured, for example.
But as hyperair mentioned, it's probably because of Pulse. You should experiment with the Microphone/"Sound out" device; try to configure it to use the microphone directly and not the "pulse" device.
As a general rule of thumb, if your voice plays back clearly with the Sound Recorder (I'm not sure, but I think the default sound capture device for GStreamer is set to ALSA, not Pulse), then Skype should work the same.
ferrarix
May 16th, 2008, 01:34 PM
Thanks for your replies.
I can't modify the audio input as I only have 1 choice in the list (I used to have around 5 before doing the edits in the first post).
Sound in: /dev/dsp
Sound out: /dev/dsp
Ringing: /dev/dsp
Will try to forward a port on my ADSL router. BTW, I didn't have any probs with Skype when I had on Vista before I put Ubuntu, so I kinda believe it's not the router. Anyway I'm gonna give it a try.
ferrarix
May 16th, 2008, 01:44 PM
UPDATE: I forwarded the port. Used the port found under Skype>Options>Connections
Made no difference. Sound I send is disastrous. The one I receive is close to perfect though.
Uhm what do you think can be the problem?
psyke83
May 16th, 2008, 01:47 PM
Thanks for your replies.
I can't modify the audio input as I only have 1 choice in the list (I used to have around 5 before doing the edits in the first post).
Sound in: /dev/dsp
Sound out: /dev/dsp
Ringing: /dev/dsp
Will try to forward a port on my ADSL router. BTW, I didn't have any probs with Skype when I had on Vista before I put Ubuntu, so I kinda believe it's not the router. Anyway I'm gonna give it a try.
Ok, you're using the OSS version of skype (in Medibuntu, that's skype-oss-static). Try installing the package "skype" instead (that's the ALSA version). You do not need to use "padsp" for the ALSA version, so launch Skype normally.
When you run Skype, you'll see different options presented in Options/Sound Devices. Set "Sound In" to "pulse" and set "Sound Out" to your microphone device.
kamitsukai
May 16th, 2008, 03:33 PM
Just to let you know that this workaround wont work if you have the game "Teeworlds" installed as it sounds like your in a fish tank when you shoot each other... :)
hyperair
May 16th, 2008, 03:45 PM
I'd like to mention that Skype 2.0.0.68 works fine for me using ALSA's pcm_pulse plugin. My configuration is as follows:
Sound In: SiS SI7012 (hw:SI7012,0)
Sound Out: pulse
Ringing: pulse
My send packet loss is approximately 13-19%, but my recv packet loss is approximately 0.3-0.4%. My voice sounds just fine when I receive it from Skype Test Call, but the lady's voice telling instructions comes slightly jittered at times.
Meson
May 16th, 2008, 04:15 PM
Has anyone had any luck with this HOWTO and a Dell docking station? I have the same sound card as the original poster, Psyke83, "Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 01)" in my Latitude D800, docked with the D/Port. But this howto does not fix my problems. I think it has something to do with audio coming out of the dock at line-level - an issue I had in Gutsy as well.
Currently, sound out of the laptop speakers themselves works fine, but I'm using external speakers connected to the dock.
psyke83
May 16th, 2008, 04:59 PM
Has anyone had any luck with this HOWTO and a Dell docking station? I have the same sound card as the original poster, Psyke83, "Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 01)" in my Latitude D800, docked with the D/Port. But this howto does not fix my problems. I think it has something to do with audio coming out of the dock at line-level - an issue I had in Gutsy as well.
Currently, sound out of the laptop speakers themselves works fine, but I'm using external speakers connected to the dock.
Meson, so what is your problem? Stuttering sound, or simply no sound while connected to the external speakers?
Remember that PulseAudio is not a sound card driver, it picks up sound from ALSA. If your problem is with ALSA, configuring PulseAudio will not and cannot help.
If your problem is getting *any* sound, I suggest you forget about PulseAudio and start experimenting with the switches in "alsamixer" (many of which are hidden by default in the GNOME Volume Applet) to see if you can get sound working that way.
Meson
May 16th, 2008, 05:07 PM
Meson, so what is your problem? Stuttering sound, or simply no sound while connected to the external speakers?
I guess stuttering is a good way to describe it. I've been saying it sounds like the speakers are blown out. My problem is not no sound at all.
psyke83
May 16th, 2008, 05:13 PM
I guess stuttering is a good way to describe it. I've been saying it sounds like the speakers are blown out. My problem is not no sound at all.
I'm not sure how the docking station functions, e.g. if audio output uses a different device.
In the case of Part D (the EQ) in my HOWTO, it defines the device to use as "plughw", which basically means the default hw device, usually "hw0,0". If you can find out the proper hardware device it should be, try editing /etc/asound.conf, then replace "plughw" with "plughw:x,y" where x,y is the proper hardware device.
It's a bit messy, though.
How is your sound when using Windows?
psyke83
May 16th, 2008, 05:16 PM
I'd like to mention that Skype 2.0.0.68 works fine for me using ALSA's pcm_pulse plugin. My configuration is as follows:
Sound In: SiS SI7012 (hw:SI7012,0)
Sound Out: pulse
Ringing: pulse
My send packet loss is approximately 13-19%, but my recv packet loss is approximately 0.3-0.4%. My voice sounds just fine when I receive it from Skype Test Call, but the lady's voice telling instructions comes slightly jittered at times.
Adjusting the fragment values helps the jitter in Skype. As we talked about before, it seems skype opens and closes dozens of connection per second, and I have a feeling that a larger buffer means a longer wait for the buffer to be filled, causing sound to stutter as the connection keeps closing and reopening. Remember this is just a workaround for a bug, not a real fix ;).
psyke83
May 16th, 2008, 08:36 PM
Just to let you know that this workaround wont work if you have the game "Teeworlds" installed as it sounds like your in a fish tank when you shoot each other... :)
I just tried this game and it seems that it tries to directly connect to a hardware device. This is bad programming and means it bypasses PulseAudio. You should ask the authors to add proper support.
Edit: http://www.teeworlds.com/forum/viewtopic.php?id=1221
Meson
May 17th, 2008, 11:58 AM
How is your sound when using Windows?
I wouldn't know. Although my brother has a similar laptop with the docking station and Windows XP - everything works fine.
So if I go to my Sound Options and explicitly select ALSA for sound events and music+movies, and still have a problem, the issue is definitely not PulseAudio?
psyke83
May 17th, 2008, 12:13 PM
I wouldn't know. Although my brother has a similar laptop with the docking station and Windows XP - everything works fine.
So if I go to my Sound Options and explicitly select ALSA for sound events and music+movies, and still have a problem, the issue is definitely not PulseAudio?
If you followed this guide, no. When an application tries to use ALSA output, it will be directed to PulseAudio (because of modifications to /etc/asound.conf).
To check if it's caused by PulseAudio, you need to "pkill pulseaudio", delete /etc/asound.conf and see if sound works ok afterwards.
00arthuryu
May 17th, 2008, 12:53 PM
omg! it worked!
I think I love you <3 lol
:lolflag:
Meson
May 17th, 2008, 12:54 PM
you need to "pkill pulseaudio", delete /etc/asound.conf and see if sound works ok afterwards.
Ok, major breakthrough, my sound works nicely after this. I guess I need to tweak the fragment number and size in /etc/pulse/daemon.conf. Odd though as I have the same card as you. Do I need to restart anything after modifying this file or do the changes take affect immediately?
psyke83
May 17th, 2008, 02:15 PM
Ok, major breakthrough, my sound works nicely after this. I guess I need to tweak the fragment number and size in /etc/pulse/daemon.conf. Odd though as I have the same card as you. Do I need to restart anything after modifying this file or do the changes take affect immediately?
They take effect after restarting pulseaudio. You can log out and back in, or:
$ pkill pulseaudio
$ pulseaudio
ferrarix
May 17th, 2008, 03:49 PM
Hey thanks to you all.
Skype is working fine. Installed the normal Ubuntu/Debian version as suggested and set it as following:
Sound In: VIA 8237 (hw:V8237,0)
Sound Out: pulse
Ringing: pulse
The packet loss is now close to zero.
Thank you all :popcorn::KS:):guitar::D
klap-in
May 17th, 2008, 05:42 PM
I looking for how to change the equalizer. I found on Archlinux some information about it. (http://wiki.archlinux.org/index.php/ALSA#System-Wide_Equalizer).
Also the next comment about controls in asound.conf, what helps me in the right the direction:
...
input {
controls [ -5 -5 -5 -5 -5 -10 -20 -15 -10 -10 -10 -10 -10 -3 -2 ]
...
#this setting is here by example, edit to your own taste
#bands: 50hz, 100hz, 156hz, 220hz, 311hz, 440hz, 622hz, 880hz, 1250hz, 1750hz, 25000hz,
#50000hz, 10000hz, 20000hz
My question is here what do the numbers mean in controls [ ... ]? Is this the change you want in decibels? So you can leave it zero when a part of the bandwidth should not change?
psyke83
May 17th, 2008, 07:05 PM
Hey thanks to you all.
Skype is working fine. Installed the normal Ubuntu/Debian version as suggested and set it as following:
Sound In: VIA 8237 (hw:V8237,0)
Sound Out: pulse
Ringing: pulse
The packet loss is now close to zero.
Thank you all :popcorn::KS:):guitar::D
Ok, but packet loss in Skype refers to network activity; a misconfigured PulseAudio can skip like crazy even with 0% packet loss. Glad it's working fine for you, though!
psyke83
May 17th, 2008, 07:20 PM
input {
controls [ -5 -5 -5 -5 -5 -10 -20 -15 -10 -10 -10 -10 -10 -3 -2 ]
...
#this setting is here by example, edit to your own taste
#bands: 50hz, 100hz, 156hz, 220hz, 311hz, 440hz, 622hz, 880hz, 1250hz, 1750hz, 25000hz,
#50000hz, 10000hz, 20000hz
My question is here what do the numbers mean in controls [ ... ]? Is this the change you want in decibels? So you can leave it zero when a part of the bandwidth should not change?
The numbers in controls [ ] are indeed parameters, but it's complicated. The amount of parameters as well as their lower and upper limits are different for each LADSPA plugin. In the above example, the plugin "mbeq" is an Equalizer that allows you to adjust those bands.
You will need to find a program that exposes the LADSPA parameters to know how to change them effectively.
In the package "ladspa-sdk" you can get a listing of installed plugins via "listplugins" and you can see the available parameters for a single plugin via "analyseplugin". Here is the information for the plugin used in this HOWTO:
conn@inspiron:~$ analyseplugin /usr/lib/ladspa/mbeq_1197.so
Plugin Name: "Multiband EQ"
Plugin Label: "mbeq"
Plugin Unique ID: 1197
Maker: "Steve Harris <steve@plugin.org.uk>"
Copyright: "GPL"
Must Run Real-Time: No
Has activate() Function: Yes
Has deativate() Function: No
Has run_adding() Function: Yes
Environment: Normal or Hard Real-Time
Ports: "50Hz gain (low shelving)" input, control, -70 to 30, default 0
"100Hz gain" input, control, -70 to 30, default 0
"156Hz gain" input, control, -70 to 30, default 0
"220Hz gain" input, control, -70 to 30, default 0
"311Hz gain" input, control, -70 to 30, default 0
"440Hz gain" input, control, -70 to 30, default 0
"622Hz gain" input, control, -70 to 30, default 0
"880Hz gain" input, control, -70 to 30, default 0
"1250Hz gain" input, control, -70 to 30, default 0
"1750Hz gain" input, control, -70 to 30, default 0
"2500Hz gain" input, control, -70 to 30, default 0
"3500Hz gain" input, control, -70 to 30, default 0
"5000Hz gain" input, control, -70 to 30, default 0
"10000Hz gain" input, control, -70 to 30, default 0
"20000Hz gain" input, control, -70 to 30, default 0
"Input" input, audio
"Output" output, audio
"latency" output, control
If you install Audacious* and the extra plugins (audacious-plugins-extra), there is a plugin that allows you to apply a LADSPA plugin and adjust the parameters via a GUI in realtime.
I am no expert with LADSPA plugins, so you're better off doing your own research. At the very least you have the answer to your questions (see the anaylseplugin output); the bands are listed and you can see that defining a control as "0" effectively leaves the band unchanged.
* Remember that if you set up the system-wide EQ via Part D and try to experiment with Audacious' LADSPA plugin, you will hear output filtered *twice*. This is not a good thing. Therefore, you must remove the "pcm.equalizer" section from asound.conf before messing with Audacious.
beytun
May 19th, 2008, 08:49 AM
Part A,B and C worked for me :) Great job. Thanks a lot. Now i can watch flash videos with firefox 3 beta 5 while playing music in rhythmbox and watching video in movie player. No crashes in firefox and no stuttering audio. Now i will try Part D to hear some more good sound :)
vprasaj
May 19th, 2008, 09:16 AM
Stuttering problem is gone.
I did Part A and C on my 32 bit ubuntu hardy (mint elyssa beta). Flash was ok before.
For my 5.1 sound i edited /etc/pulse/daemon.conf and changed
; default-sample-channels = 2
to
default-sample-channels = 6
Now my sound system is complete! :)
Thank you psyke83!
beytun
May 19th, 2008, 10:24 AM
Now i did what Part D says but after that there i couldn't get any sound from my pc except rhythmbox. I tried to watch flash video on youtube and listen mp3 on imeem.com in firefox3b5. Even i couldn't hear the sound when i logged on. The worse thing is that when i try to play a video in movie player my pc totaly got locked. I also try to run movie player with comand
$ padsp totem
Then i modified /etc/asound.conf like in Part A and changed the /etc/pulse/default.pa with the original one. Firefox and the other things except movie player got fixed.
Now i will uninstall "swh-plugins" package with command
$ sudo apt-get remove swh-plugins
then try run movie player properly.
Does any one have any idea what is wrong with this things? I am using toshiba A105-S4094.
beytun
May 19th, 2008, 10:31 AM
I removed the package and now movie player works fine too. Is it possible that movie player and swh-plugins have some disconformity?
klap-in
May 19th, 2008, 02:53 PM
@psyke83
Thanks for the help about the plugins.
But first I have fix pulseaudio itself..
I guess pulseaudio doesn't what it should. I have managed that in now starts it self. In stead of give a segmentation fault. PulseAudio Manager works also. But different programs didn't play sound.
At this moment part A and B I have done. Part D was installed, but I have removed it again, but that seems not the problem.
Rhythmbox didn't give sound.
De output of verbose is displayed below. When pulseaudio is start. I start Rhythmbox and try to play a number, but that fail and give the last lines of the output below. When some dutch message are a problem, say it, then I will translate them.
Do you have an advise what to do?
..:~$ pkill pulseaudio
..:~$ pulseaudio -vv
I: main.c: We're in the group 'pulse-rt', allowing real-time and high-priority scheduling.
I: core-util.c: Successfully gained nice level -11.
W: pid.c: Stale PID file, overwriting.
I: main.c: setrlimit(RLIMIT_NICE, (31, 31)) failed: Bewerking niet toegestaan
I: main.c: setrlimit(RLIMIT_RTPRIO, (9, 9)) failed: Bewerking niet toegestaan
I: main.c: This is PulseAudio 0.9.10
I: main.c: Page size is 4096 bytes
I: main.c: Dude, your kernel stinks! The chef's recommendation today is Linux with high-resolution timers enabled!
D: cli-command.c: Checking for existance of '/usr/lib/pulse-0.9/modules/module-hal-detect.so': success
I: module-hal-detect.c: Trying capability alsa
D: module-hal-detect.c: Not loaded device /org/freedesktop/Hal/devices/computer_alsa_timer
D: module-hal-detect.c: Not loaded device /org/freedesktop/Hal/devices/computer_alsa_sequencer
D: module-hal-detect.c: Not loaded device /org/freedesktop/Hal/devices/pci_10de_59_sound_card_0_alsa_playback_2
D: module-hal-detect.c: Not loaded device /org/freedesktop/Hal/devices/pci_10de_59_sound_card_0_alsa_capture_1
D: module-hal-detect.c: Loading module-alsa-sink with arguments 'device_id=0 sink_name=alsa_output.pci_10de_59_sound_card_0_als a_playback_0'
D: alsa-util.c: Trying front:0...
W: alsa-util.c: Device front:0 doesn't support 44100 Hz, changed to 48000 Hz.
I: module-alsa-sink.c: Successfully opened device front:0.
I: module-alsa-sink.c: Successfully enabled mmap() mode.
ALSA lib control.c:909:(snd_ctl_open_noupdate) Invalid CTL front:0
I: alsa-util.c: Unable to attach to mixer front:0: Bestand of map bestaat niet
I: alsa-util.c: Successfully attached to mixer 'hw:0'
I: alsa-util.c: Using mixer control "Master".
I: sink.c: Created sink 0 "alsa_output.pci_10de_59_sound_card_0_alsa_playback _0" with sample spec "s16le 2ch 48000Hz"
I: source.c: Created source 0 "alsa_output.pci_10de_59_sound_card_0_alsa_playback _0.monitor" with sample spec "s16le 2ch 48000Hz"
I: module-alsa-sink.c: Using 4 fragments of size 4408 bytes.
I: alsa-util.c: All 2 channels can be mapped to mixer channels. Using hardware volume control.
D: module-alsa-sink.c: Thread starting up
D: rtpoll.c: Acquired POSIX realtime signal SIGRTMIN+29
I: module-alsa-sink.c: Starting playback.
I: module.c: Loaded "module-alsa-sink" (index: #0; argument: "device_id=0 sink_name=alsa_output.pci_10de_59_sound_card_0_als a_playback_0").
D: module-hal-detect.c: Loading module-alsa-source with arguments 'device_id=0 source_name=alsa_input.pci_10de_59_sound_card_0_al sa_capture_0'
D: alsa-util.c: Trying front:0...
W: alsa-util.c: Device front:0 doesn't support 44100 Hz, changed to 48000 Hz.
I: module-alsa-source.c: Successfully opened device front:0.
I: module-alsa-source.c: Successfully enabled mmap() mode.
ALSA lib control.c:909:(snd_ctl_open_noupdate) Invalid CTL front:0
I: alsa-util.c: Unable to attach to mixer front:0: Bestand of map bestaat niet
I: alsa-util.c: Successfully attached to mixer 'hw:0'
I: alsa-util.c: Using mixer control "Capture".
I: source.c: Created source 1 "alsa_input.pci_10de_59_sound_card_0_alsa_capture_0" with sample spec "s16le 2ch 48000Hz"
I: module-alsa-source.c: Using 4 fragments of size 4408 bytes.
I: alsa-util.c: All 2 channels can be mapped to mixer channels. Using hardware volume control.
D: module-alsa-source.c: Thread starting up
D: rtpoll.c: Acquired POSIX realtime signal SIGRTMIN+28
I: module.c: Loaded "module-alsa-source" (index: #1; argument: "device_id=0 source_name=alsa_input.pci_10de_59_sound_card_0_al sa_capture_0").
D: module-hal-detect.c: Not loaded device /org/freedesktop/Hal/devices/pci_10de_59_sound_card_0_alsa_control__1
I: module-hal-detect.c: Loaded 2 modules.
I: module.c: Loaded "module-hal-detect" (index: #2; argument: "").
D: cli-command.c: Checking for existance of '/usr/lib/pulse-0.9/modules/module-esound-protocol-unix.so': success
I: module.c: Loaded "module-esound-protocol-unix" (index: #3; argument: "").
I: protocol-native.c: loading cookie from disk.
I: module.c: Loaded "module-native-protocol-unix" (index: #4; argument: "").
I: module.c: Loaded "module-volume-restore" (index: #5; argument: "").
D: module-default-device-restore.c: No previous default sink setting, ignoring.
D: module-default-device-restore.c: Restored default source 'alsa_input.pci_10de_59_sound_card_0_alsa_capture_ 0'.
I: module.c: Loaded "module-default-device-restore" (index: #6; argument: "").
I: module.c: Loaded "module-rescue-streams" (index: #7; argument: "").
D: module-suspend-on-idle.c: Sink alsa_output.pci_10de_59_sound_card_0_alsa_playback _0 becomes idle.
D: module-suspend-on-idle.c: Source alsa_output.pci_10de_59_sound_card_0_alsa_playback _0.monitor becomes idle.
D: module-suspend-on-idle.c: Source alsa_input.pci_10de_59_sound_card_0_alsa_capture_0 becomes idle.
I: module.c: Loaded "module-suspend-on-idle" (index: #8; argument: "").
D: cli-command.c: Checking for existance of '/usr/lib/pulse-0.9/modules/module-gconf.so': success
I: module.c: Loaded "module-gconf" (index: #9; argument: "").
D: cli-command.c: Checking for existance of '/usr/lib/pulse-0.9/modules/module-x11-publish.so': success
D: module-x11-publish.c: using already loaded auth cookie.
I: module.c: Loaded "module-x11-publish" (index: #10; argument: "").
I: main.c: Daemon startup complete.
D: module-hal-detect.c: dbus: interface=org.freedesktop.DBus, path=/org/freedesktop/DBus, member=NameAcquired
I: module-suspend-on-idle.c: Source alsa_input.pci_10de_59_sound_card_0_alsa_capture_0 idle for too long, suspending ...
I: module-alsa-source.c: Device suspended...
I: module-suspend-on-idle.c: Source alsa_output.pci_10de_59_sound_card_0_alsa_playback _0.monitor idle for too long, suspending ...
I: module-suspend-on-idle.c: Sink alsa_output.pci_10de_59_sound_card_0_alsa_playback _0 idle for too long, suspending ...
I: module-alsa-sink.c: Device suspended...
I: client.c: Created 0 "Native client (UNIX socket client)"
I: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
I: protocol-native.c: Enabled SHM for new connection
I: client.c: Client 0 changed name from "Native client (UNIX socket client)" to "Rhythmbox"
I: client.c: Freed 0 "Rhythmbox"
I: protocol-native.c: connection died.
I: client.c: Created 1 "Native client (UNIX socket client)"
I: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
I: protocol-native.c: Enabled SHM for new connection
I: client.c: Client 1 changed name from "Native client (UNIX socket client)" to "Rhythmbox"
I: client.c: Freed 1 "Rhythmbox"
I: protocol-native.c: connection died.
I: client.c: Created 2 "Native client (UNIX socket client)"
I: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
I: protocol-native.c: Enabled SHM for new connection
I: client.c: Client 2 changed name from "Native client (UNIX socket client)" to "Rhythmbox"
I: client.c: Freed 2 "Rhythmbox"
I: protocol-native.c: connection died.
I: client.c: Created 3 "Native client (UNIX socket client)"
I: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
I: protocol-native.c: Enabled SHM for new connection
I: client.c: Client 3 changed name from "Native client (UNIX socket client)" to "PulseAudio Manager"
D: sound-file.c: POSIX_FADV_SEQUENTIAL succeeded.
D: memblock.c: Memory block too large for pool: 1361924 > 16376
D: core-scache.c: Playing sample "pulse-hotplug" on "alsa_output.pci_10de_59_sound_card_0_alsa_playback _0"
D: core-util.c: posix_madvise() failed (or doesn't exist), trying mlock(): Ongeldige bestandsdescriptor
D: core-util.c: mlock() worked fine!
I: module-alsa-sink.c: Trying resume...
I: module-alsa-sink.c: Resumed successfully...
I: module-alsa-sink.c: Starting playback.
D: module-suspend-on-idle.c: Sink alsa_output.pci_10de_59_sound_card_0_alsa_playback _0 becomes idle.
D: module-suspend-on-idle.c: Sink alsa_output.pci_10de_59_sound_card_0_alsa_playback _0 becomes busy.
I: resampler.c: Using resampler 'speex-float-3'
I: resampler.c: Using float32le as working format.
I: resampler.c: Choosing speex quality setting 3.
I: sink-input.c: Created input 0 "sample:pulse-hotplug" on alsa_output.pci_10de_59_sound_card_0_alsa_playback _0 with sample spec s16le 2ch 44100Hz and channel map front-left,front-right
D: memblock.c: Memory block too large for pool: 17624 > 16376
D: module-suspend-on-idle.c: Sink alsa_output.pci_10de_59_sound_card_0_alsa_playback _0 becomes idle.
D: module-suspend-on-idle.c: Sink alsa_output.pci_10de_59_sound_card_0_alsa_playback _0 becomes idle.
I: sink-input.c: Freeing output 0 "sample:pulse-hotplug"
I: module-suspend-on-idle.c: Sink alsa_output.pci_10de_59_sound_card_0_alsa_playback _0 idle for too long, suspending ...
I: module-alsa-sink.c: Device suspended...
psyke83
May 19th, 2008, 03:22 PM
@psyke83
Thanks for the help about the plugins.
But first I have fix pulseaudio itself..
I'm afraid I don't see any problems from that output, and I'm not sure what your problem is.
I would recommend you undo all the changes from this guide (Appendix 2), then check if your PulseAudio is running normally.
Then, apply Part A, log out and in, and see if things work. Then follow the other steps as long as things still work ok.
psyke83
May 19th, 2008, 03:23 PM
I removed the package and now movie player works fine too. Is it possible that movie player and swh-plugins have some disconformity?
No, that shouldn't happen. Try to undo all the changes from this guide and see if things work ok, perhaps.
pingpongboss
May 19th, 2008, 06:16 PM
The equalizer part of your guide was awesome! Thanks :KS
Sordelka
May 19th, 2008, 09:33 PM
Woha thank you so much. It works without any problems!
OmahaZ
May 19th, 2008, 10:03 PM
Thanks indeed psyke83 c|;o)
Improved soundquality throughout - no stuttering and no tincan sound anymore.
No difficulties whatsoever with your guide.
Would it be possible for you to add a comment at the bottom near the downloadable files (flash and default.pa.txt) that one has to be a member of Ubuntuforums to get the attachments?
steveneddy
May 19th, 2008, 10:13 PM
Part C, #4 (Optional) fixed my stuttering audio.
Thank you.
This is the only fix I did because I already had the new kernel and it still stuttered.
Not sure, but I think I just squashed my last bug on my laptop since installing Hardy.
pingpongboss
May 20th, 2008, 01:56 AM
The equalizer part of your guide was awesome! Thanks :KS
ah crap, well it broke sound in GTA San Andreas under wine. So i had to revert the changes. One day i'll look into why it stopped working :mad:
psyke83
May 20th, 2008, 08:42 AM
ah crap, well it broke sound in GTA San Andreas under wine. So i had to revert the changes. One day i'll look into why it stopped working :mad:
You didn't have to revert changes so soon...
You have two options (I already mentioned these in the guide, by the way):
1. Select the "OSS" audio driver via "winecfg". When you launch Wine applications, use "padsp" (see Appendix 1).
2. Select the "ESD" audio driver via "winecfg".
The ALSA driver is not currently compatible (the problem is partly WINE, partly PulseAudio), but it's being worked on and should be resolved in the next few versions.
In the meantime, both options above should work.
Janik
May 20th, 2008, 09:38 AM
hi,
this howto hasn't really helped me out for skype.
I get sound thru 'pulse' and the stuttering of others' voices is less when I put the values from the optional step in part C of the howto.
However it doesn't really work better now than it did before the howto. Before the howto I was also able to hear others' voices. So, my issue is that I hear the voice quite good of others but my voice is completely stuttering.
CPU is 100% while calling. I tried a lot of different values for 'default-fragments' and
'default-fragment-size-msec' but none really made it better.
Can it be because of the microphone I use is thru a voip-phone?
I get this message when I killed pulse and restart it:
ALSA lib control.c:909:(snd_ctl_open_noupdate) Invalid CTL front:1
W: alsa-util.c: Cannot find fallback mixer control "PCM".
ALSA lib control.c:909:(snd_ctl_open_noupdate) Invalid CTL front:1
ALSA lib control.c:909:(snd_ctl_open_noupdate) Invalid CTL front:0
ALSA lib control.c:909:(snd_ctl_open_noupdate) Invalid CTL front:0
I am going to try with the static-oss version and padsp.
It's really anoing for me cause skype is the main program I use on this computer (the rest is just office).
Thanks for any input,
Janik
psyke83
May 20th, 2008, 12:53 PM
hi,
this howto hasn't really helped me out for skype.
I get sound thru 'pulse' and the stuttering of others' voices is less when I put the values from the optional step in part C of the howto.
However it doesn't really work better now than it did before the howto. Before the howto I was also able to hear others' voices. So, my issue is that I hear the voice quite good of others but my voice is completely stuttering.
CPU is 100% while calling. I tried a lot of different values for 'default-fragments' and
'default-fragment-size-msec' but none really made it better.
Can it be because of the microphone I use is thru a voip-phone?
I get this message when I killed pulse and restart it:
ALSA lib control.c:909:(snd_ctl_open_noupdate) Invalid CTL front:1
W: alsa-util.c: Cannot find fallback mixer control "PCM".
ALSA lib control.c:909:(snd_ctl_open_noupdate) Invalid CTL front:1
ALSA lib control.c:909:(snd_ctl_open_noupdate) Invalid CTL front:0
ALSA lib control.c:909:(snd_ctl_open_noupdate) Invalid CTL front:0
I am going to try with the static-oss version and padsp.
It's really anoing for me cause skype is the main program I use on this computer (the rest is just office).
Thanks for any input,
Janik
I'm in a bit of a hurry, sorry I can't give a more detailed answer. In Skype, keep the "Sound Out" as the "pulse" device, but set "Sound In" directly to your hardware device that is connected to your microphone. Please see previous posts in this thread, it was already discussed.
psyke83
May 20th, 2008, 09:09 PM
Hi everyone,
I've made a small update (v2.2) to the guide, replacing Debian unstable packages with Intrepid's versions instead. If you've already followed this guide, there's no need to "upgrade" packages as they are pretty much identical.
The real news is that Part B (Flash) has been fixed in Intrepid, and will probably be backported to Hardy soon. Part A seems on the way towards getting fixed officially as well. See the linked bug reports for more details.
When I have news, I'll update the HOWTO (especially if any steps need to be taken to downgrade packages).
banjobacon
May 20th, 2008, 09:51 PM
After following parts A and B, I didn't get any audio when running a few games through Wine/Steam: Half Life 2, Pulse, and Stubbs. Actually, I heard audio when the Valve splash screen appeared, but there was no audio after that.
I undid part A and I was able to get audio in these games without a problem. Wine was set up to use ALSA the whole time.
psyke83
May 20th, 2008, 09:55 PM
After following parts A and B, I didn't get any audio when running a few games through Wine/Steam: Half Life 2, Pulse, and Stubbs. Actually, I heard audio when the Valve splash screen appeared, but there was no audio after that.
I undid part A and I was able to get audio in these games without a problem. Wine was set up to use ALSA the whole time.
Please read Appendix 1, or my reply to pingpongboss on this page.
klap-in
May 22nd, 2008, 12:02 PM
I'm afraid I don't see any problems from that output, and I'm not sure what your problem is.
I would recommend you undo all the changes from this guide (Appendix 2), then check if your PulseAudio is running normally.
Then, apply Part A, log out and in, and see if things work. Then follow the other steps as long as things still work ok.
Pulseaudio works, without reinstall anything, probably the second time reboot helps...
Now I have install part D and the problems are back.
I have tried to change the output to the sofware mixer: comment slave.pcm "plughw" and uncomment #slave.pcm "plug:dmix"
This didn't help.
When I try to start the pulseaudio volume control I got the dialog: 'Connection failed: Connection refused'
Do you have a good advice what to do?
Thanks
This is using dmix:
--:~$ pkill pulseaudio
--:~$ pulseaudio
W: pid.c: Stale PID file, overwriting.
ALSA lib control.c:909:(snd_ctl_open_noupdate) Invalid CTL equalized
ALSA lib conf.c:3952:(snd_config_expand) Segmentatiefout
and using with verbose option on:
--:~$ pkill pulseaudio
--:~$ pulseaudio -vv
I: main.c: We're in the group 'pulse-rt', allowing real-time and high-priority scheduling.
I: core-util.c: Successfully gained nice level -11.
W: pid.c: Stale PID file, overwriting.
I: main.c: setrlimit(RLIMIT_NICE, (31, 31)) failed: Bewerking niet toegestaan
I: main.c: setrlimit(RLIMIT_RTPRIO, (9, 9)) failed: Bewerking niet toegestaan
I: main.c: This is PulseAudio 0.9.10
I: main.c: Page size is 4096 bytes
I: main.c: Dude, your kernel stinks! The chef's recommendation today is Linux with high-resolution timers enabled!
I: module.c: Loaded "module-suspend-on-idle" (index: #0; argument: "").
I: module-alsa-sink.c: Successfully opened device equalized.
I: module-alsa-sink.c: Successfully enabled mmap() mode.
ALSA lib control.c:909:(snd_ctl_open_noupdate) Invalid CTL equalized
I: alsa-util.c: Unable to attach to mixer equalized: Bestand of map bestaat niet
I: alsa-util.c: Unable to attach to mixer hw:(null): Onjuist apparaat
I: sink.c: Created sink 0 "alsa_output.equalized" with sample spec "s16le 2ch 44100Hz"
I: source.c: Created source 0 "alsa_output.equalized.monitor" with sample spec "s16le 2ch 44100Hz"
I: module-alsa-sink.c: Using 5 fragments of size 3760 bytes.
D: module-alsa-sink.c: Thread starting up
D: rtpoll.c: Acquired POSIX realtime signal SIGRTMIN+29
I: module-alsa-sink.c: Starting playback.
D: module-suspend-on-idle.c: Source alsa_output.equalized.monitor becomes idle.
D: module-suspend-on-idle.c: Sink alsa_output.equalized becomes idle.
I: module.c: Loaded "module-alsa-sink" (index: #1; argument: "device=equalized").
D: cli-command.c: Checking for existance of '/usr/lib/pulse-0.9/modules/module-hal-detect.so': success
I: module-hal-detect.c: Trying capability alsa
D: module-hal-detect.c: Not loaded device /org/freedesktop/Hal/devices/computer_alsa_timer
D: module-hal-detect.c: Not loaded device /org/freedesktop/Hal/devices/computer_alsa_sequencer
D: module-hal-detect.c: Not loaded device /org/freedesktop/Hal/devices/pci_10de_59_sound_card_0_alsa_playback_2
D: module-hal-detect.c: Not loaded device /org/freedesktop/Hal/devices/pci_10de_59_sound_card_0_alsa_capture_1
D: module-hal-detect.c: Loading module-alsa-sink with arguments 'device_id=0 sink_name=alsa_output.pci_10de_59_sound_card_0_als a_playback_0'
D: alsa-util.c: Trying front:0...
Segmentatiefout
And when I did use "plughw" verbose gives a similar output, so i guess that option doesn't matter..:
--:~$ pkill pulseaudio
--n:~$ pulseaudio -vv
I: main.c: We're in the group 'pulse-rt', allowing real-time and high-priority scheduling.
I: core-util.c: Successfully gained nice level -11.
I: main.c: setrlimit(RLIMIT_NICE, (31, 31)) failed: Bewerking niet toegestaan
I: main.c: setrlimit(RLIMIT_RTPRIO, (9, 9)) failed: Bewerking niet toegestaan
I: main.c: This is PulseAudio 0.9.10
I: main.c: Page size is 4096 bytes
I: main.c: Dude, your kernel stinks! The chef's recommendation today is Linux with high-resolution timers enabled!
I: module.c: Loaded "module-suspend-on-idle" (index: #0; argument: "").
I: module-alsa-sink.c: Successfully opened device equalized.
I: module-alsa-sink.c: Successfully enabled mmap() mode.
ALSA lib control.c:909:(snd_ctl_open_noupdate) Invalid CTL equalized
I: alsa-util.c: Unable to attach to mixer equalized: Bestand of map bestaat niet
I: alsa-util.c: Unable to attach to mixer hw:(null): Onjuist apparaat
I: sink.c: Created sink 0 "alsa_output.equalized" with sample spec "s16le 2ch 44100Hz"
I: source.c: Created source 0 "alsa_output.equalized.monitor" with sample spec "s16le 2ch 44100Hz"
I: module-alsa-sink.c: Using 4 fragments of size 4408 bytes.
D: module-alsa-sink.c: Thread starting up
D: rtpoll.c: Acquired POSIX realtime signal SIGRTMIN+29
I: module-alsa-sink.c: Starting playback.
D: module-suspend-on-idle.c: Source alsa_output.equalized.monitor becomes idle.
D: module-suspend-on-idle.c: Sink alsa_output.equalized becomes idle.
I: module.c: Loaded "module-alsa-sink" (index: #1; argument: "device=equalized").
D: cli-command.c: Checking for existance of '/usr/lib/pulse-0.9/modules/module-hal-detect.so': success
I: module-hal-detect.c: Trying capability alsa
D: module-hal-detect.c: Not loaded device /org/freedesktop/Hal/devices/computer_alsa_timer
D: module-hal-detect.c: Not loaded device /org/freedesktop/Hal/devices/computer_alsa_sequencer
D: module-hal-detect.c: Not loaded device /org/freedesktop/Hal/devices/pci_10de_59_sound_card_0_alsa_playback_2
D: module-hal-detect.c: Not loaded device /org/freedesktop/Hal/devices/pci_10de_59_sound_card_0_alsa_capture_1
D: module-hal-detect.c: Loading module-alsa-sink with arguments 'device_id=0 sink_name=alsa_output.pci_10de_59_sound_card_0_als a_playback_0'
D: alsa-util.c: Trying front:0...
Segmentatiefout
crimsun
May 22nd, 2008, 05:16 PM
Thanks for the notes. Here are additional points:
Part A step 2 should use `asoundconf set-pulseaudio'.
The fixes for hardy's alsa-plugins are in bzr (https://code.launchpad.net/~ubuntu-core-dev/alsa-plugins/hardy). It's not as straightforward as just pulling in those fixes, since you must have alsa-lib 1.0.16, too.
So - for 8.04.1 timeframe, the plan is to attempt to backport (to hardy-backports) alsa-lib, alsa-plugins, libflashsupport, and flashplugin-nonfree from intrepid. (There is a known issue with focus grabbing in the Flash 10 beta.)
For 8.10, nspluginwrapper will be enabled on i386, too.
Further questions should be copied to the ubuntu-devel-discuss mailing list, too.
klap-in
May 22nd, 2008, 08:10 PM
In addition to my previous post, I can't play for example flashmovies with sound together with Rhythmbox. So pulseaudio seems to do not its work. (but I guess that is logical, because pulseaudio do not start)
SnowPunk98
May 23rd, 2008, 12:44 AM
My sounds stutters when I get an IM in pidgin where it feels like my system resources are really low and it can't process fast enough, I assume this is fix B you are referring to.
When I am plahing a MP3 in totem I do not get any sound in Pidgin, I assume this is because Pidgin is ALAS aware?
I am using a Dell Inspiron E1705/9400, should I use your fixes to resolve my problems or will they be fixed by Ubuntu in Hardy or will I have to wait until the next release?
reidi
May 23rd, 2008, 10:39 AM
2. Enable the "hardy-proposed" repository via Synaptic and perform a dist-upgrade to get kernel 2.6.24-17-generic. Hopefully it is not necessary to describe this in detail; most people should be able to figure it out.
Repository enabled. But when I do a "sudo apt-get dist-upgrade" I am prompted to install many, many packages.
Can I upgrade just the kernel and headers?
If so, how would I do that? (syntax please).
NTolerance
May 23rd, 2008, 08:46 PM
nm
richardh9936
May 25th, 2008, 01:46 AM
This information about libasound2-1.0.16+ is also essential for people trying Enlightenment e17. apt-get install emodules-all may fail with HARDY installations because the e modules expect libasound2 to be >> 1.0.16, but HARDY only provides 1.0.15.
hihihi
May 26th, 2008, 01:12 PM
hello there,
first of all: many thanks, your how-to made the sound-skips-hips-snips disappear, finally...
I am running xubuntu hardy 8.04 64bit, i just followed part C.
the /etc.alsa.conf interfeared with anything in my sys and i had no ALSA sound anymore so i deleted it again.
sound is back and really great, THX
flacvest
May 28th, 2008, 02:28 AM
Hi, I just wanted to say THANK-YOU!!!
'Been wanting an EQ for MPD/Sonata ever since I started using it around January 08. I tried to use JACK, failed miserably and destroyed 2 installations in the process. Your guide worked the first time around for me, on Xubuntu Hardy amd64 on a Shuttle XPC SN27P2 with a dualcore and 8GB RAM.
I wanted to say thanks because I have NEVER heard such clean, well articulated music IN MY ENTIRE LIFE! Talk about a great how-to...
-flacvest
cacus
May 28th, 2008, 03:36 AM
Hi there, I'm under AMD64, Creative Audigy2 lS (CA0106), Hardy 8.04 and followed your guide for the EQ...
I try to change the EQ settings for frequencies... But nothing happens...
How do I know the plugin "equalized" is working or not?
I just did everything in the guide (the EQ part only) and play with the values in /etc/asound.conf at the end of file.
I've tried something pretty awful like:
[...]
controls [ -20 -20 -20 -20 -20 -20 -20 -20 -20 -20 -20 -20 20 20 20 ]
[...]
This was to see if the EQ was working or not, but i didn't note any change...
Anyone could give me a hand?
Greetings.
cacus
cacus
May 28th, 2008, 03:59 AM
Ok now, i've found the problem...
There was a file called "default.pa" in my "/home/user/.pulse" dir that i've created...
Just renamed it.
But, that file was the one that managed mi 4.0 surround system. Without that file i'm now listening to equalized output but only in the two front speakers.... How to make EQ works with surround40??? (or combine the two sinks)
Sorry about my english, i'm from Argentina.
Greetings
PS:I pasted the content of the "default.pa" file i was using to make the surround40.
#!/usr/bin/pulseaudio -nF
#
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, write to the Free Software Foundation,
# Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA.
.nofail
### Load something into the sample cache
#load-sample-lazy x11-bell /usr/share/sounds/gtk-events/activate.wav
load-sample-lazy pulse-hotplug /usr/share/sounds/startup3.wav
#load-sample-lazy pulse-coldplug /usr/share/sounds/startup3.wav
#load-sample-lazy pulse-access /usr/share/sounds/generic.wav
.fail
### Load audio drivers statically (it's probably better to not load
### these drivers manually, but instead use module-hal-detect --
### see below -- for doing this automatically)
#load-module module-alsa-source device=hw:1,0
#load-module module-oss device="/dev/dsp" sink_name=output source_name=input
#load-module module-oss-mmap device="/dev/dsp" sink_name=output source_name=input
#load-module module-null-sink
#load-module module-pipe-sink
load-module module-alsa-sink device=surround40:CA0106 sink_name=CA0106
load-module module-alsa-source device=hw:CA0106
### Automatically load driver modules depending on the hardware available
.ifexists module-hal-detect.so
#load-module module-hal-detect
.else
### Alternatively use the static hardware detection module (for systems that
### lack HAL support)
load-module module-detect
.endif
### Load several protocols
.ifexists module-esound-protocol-unix.so
load-module module-esound-protocol-unix
.endif
load-module module-native-protocol-unix
### Network access (may be configured with paprefs, so leave this commented
### here if you plan to use paprefs)
#load-module module-esound-protocol-tcp
#load-module module-native-protocol-tcp
#load-module module-zeroconf-publish
### Load the RTP reciever module (also configured via paprefs, see above)
#load-module module-rtp-recv
### Load the RTP sender module (also configured via paprefs, see above)
#load-module module-null-sink sink_name=rtp format=s16be channels=2 rate=44100 description="RTP Multicast Sink"
#load-module module-rtp-send source=rtp.monitor
### Automatically restore the volume of playback streams
load-module module-volume-restore
### Automatically restore the default sink/source when changed by the user during runtime
load-module module-default-device-restore
### Automatically move streams to the default sink if the sink they are
### connected to dies, similar for sources
load-module module-rescue-streams
### Automatically suspend sinks/sources that become idle for too long
load-module module-suspend-on-idle
### Load X11 bell module
#load-module module-x11-bell sample=x11-bell
### Register ourselves in the X11 session manager
# Deactivated by default, to avoid deadlock when PA is started as esd from gnome-session
# Instead we load this via /etc/xdg/autostart/ and "pactl load-module" now
# load-module module-x11-xsmp
### Load additional modules from GConf settings. This can be configured with the paprefs tool.
### Please keep in mind that the modules configured by paprefs might conflict with manually
### loaded modules.
.ifexists module-gconf.so
.nofail
load-module module-gconf
.fail
.endif
### Publish connection data in the X11 root window
.ifexists module-x11-publish.so
.nofail
load-module module-x11-publish
.fail
.endif
### Make some devices default
#set-default-source input
load-module module-combine sink_name=combined master= slaves=CA0106,
psyke83
May 28th, 2008, 09:41 AM
Ok now, i've found the problem...
There was a file called "default.pa" in my "/home/user/.pulse" dir that i've created...
Just renamed it.
But, that file was the one that managed mi 4.0 surround system. Without that file i'm now listening to equalized output but only in the two front speakers.... How to make EQ works with surround40??? (or combine the two sinks)
Sorry about my english, i'm from Argentina.
Greetings
Well, let's see if we can get it working. Firstly, the way I arrange EQ support is by pointing PulseAudio to a virtual ALSA device, not directly to the hardware. Therefore, you need to focus on the asound.conf file.
Providing you have followed the guide (Part A & D), you will see this line in /etc/asound.conf:
slave.pcm "plughw"
This is the line that tells ALSA what sound card to use. On my system, it should define the default playback device, so in fact it really points to "plughw:0,0". Perhaps it is not picking the default device for you, so check your hardware:
cat /etc/asound/devices
Here's my output: conn@inspiron:~$ cat /proc/asound/devices
0: [ 0] : control
1: : sequencer
16: [ 0- 0]: digital audio playback
20: [ 0- 4]: digital audio playback
24: [ 0- 0]: digital audio capture
25: [ 0- 1]: digital audio capture
26: [ 0- 2]: digital audio capture
27: [ 0- 3]: digital audio capture
33: : timer
In my case, "plughw:0,0" is appropriate, so see if it's different for you and edit /etc/asound.conf to reflect that.
Alternatively, your /etc/asound.conf may be configured correctly, but PulseAudio is not detecting the correct speaker layout. Try editing /etc/pulse/daemon.conf and make sure this line is present:
default-sample-channels = 4
Let me know if you get it working.
psyke83
May 28th, 2008, 09:45 AM
My sounds stutters when I get an IM in pidgin where it feels like my system resources are really low and it can't process fast enough, I assume this is fix B you are referring to.
When I am plahing a MP3 in totem I do not get any sound in Pidgin, I assume this is because Pidgin is ALAS aware?
I am using a Dell Inspiron E1705/9400, should I use your fixes to resolve my problems or will they be fixed by Ubuntu in Hardy or will I have to wait until the next release?
Your problem with Totem and Pidgin depends on how you have configured your system. If you did not follow my guide and "Sound Playback" is set to "ALSA" in System/Preferences/Sound, then programs will conflict, so it's best to set everything to "Autodetect".
If you follow my guide, then you won't have this problem anymore, even if you have everything set to "ALSA" in Sound Preferences.
cacus
May 28th, 2008, 10:25 AM
Here's my output: conn@inspiron:~$ cat /proc/asound/devices
0: [ 0] : control
1: : sequencer
16: [ 0- 0]: digital audio playback
20: [ 0- 4]: digital audio playback
24: [ 0- 0]: digital audio capture
25: [ 0- 1]: digital audio capture
26: [ 0- 2]: digital audio capture
27: [ 0- 3]: digital audio capture
33: : timer
In my case, "plughw:0,0" is appropriate, so see if it's different for you and edit /etc/asound.conf to reflect that.
Alternatively, your /etc/asound.conf may be configured correctly, but PulseAudio is not detecting the correct speaker layout. Try editing /etc/pulse/daemon.conf and make sure this line is present:
default-sample-channels = 4
Mi output:
cacus@mendieta:~$ cat /proc/asound/devices
0: [ 0] : control
1: : sequencer
8: [ 0- 0]: raw midi
16: [ 0- 0]: digital audio playback
17: [ 0- 1]: digital audio playback
18: [ 0- 2]: digital audio playback
19: [ 0- 3]: digital audio playback
24: [ 0- 0]: digital audio capture
25: [ 0- 1]: digital audio capture
26: [ 0- 2]: digital audio capture
27: [ 0- 3]: digital audio capture
32: [ 1] : control
33: : timer
36: [ 1- 0]: hardware dependent
48: [ 1- 0]: digital audio playback
49: [ 1- 1]: digital audio playback
56: [ 1- 0]: digital audio capture
57: [ 1- 1]: digital audio capture
(I have 2 sound cards, HDA NVIDIA OnBoard and the CA0106)
So, I guess it's correct for me too "0,0".
In "/etc/pulse/daemon.conf" I've already "default-sample-channels" set to 4...
Any other idea?
Maybe applying some old school duplicate route policy in asound.conf? (as I did in older versions of Ubuntu to set my surround with CA0106). What do you think?.
Thanks for the interest!.
psyke83
May 28th, 2008, 10:56 AM
Mi output:
(I have 2 sound cards, HDA NVIDIA OnBoard and the CA0106)
So, I guess it's correct for me too "0,0".
In "/etc/pulse/daemon.conf" I've already "default-sample-channels" set to 4...
Any other idea?
Maybe applying some old school duplicate route policy in asound.conf? (as I did in older versions of Ubuntu to set my surround with CA0106). What do you think?.
Thanks for the interest!.
Actually, if your onboard card is detected first, wouldn't that be "0,0", and your CA0106 would register as "1,0"? I don't have multiple cards so I can't be sure.
If you can't get it to work, please post the asound.conf that you originally used (before PulseAudio) and we'll try to adapt it.
Edit: In fact, it seems you can define the hardware device by the name, so try changing the definition in /etc/asound.conf to read:
slave.pcm "plughw:CA0106"
cacus
May 28th, 2008, 12:47 PM
Actually, if your onboard card is detected first, wouldn't that be "0,0", and your CA0106 would register as "1,0"? I don't have multiple cards so I can't be sure.
If you can't get it to work, please post the asound.conf that you originally used (before PulseAudio) and we'll try to adapt it.
Edit: In fact, it seems you can define the hardware device by the name, so try changing the definition in /etc/asound.conf to read:
slave.pcm "plughw:CA0106"
Man, by setting slave.pcm to "plughw:CA0106" i've just messed up pulseaudio...
Completely removed the server :S...
The last config i was talking about for surround40 was in my default.pa file in /home/user/.pulse... and is the one that I posted in one of my previous posts.
In Fiesty I remember to tweak the .asoundrc for surround40 using duplicate route policy or the presets in alsa surround40, 41 or 51...
Anyway, with that config I lost my dmix possibilities, so i just could play one stream at a time. That's a bug with the CA0601 and ALSA, I've read a lot of information in ALSA docs and it was just possible one thing or the other... dmix (multiple applications streaming) or surround, but not both at the same time.
So, my bet was in pulseaudio and it's promises... and now, I'm with the problem of the equalizer... It's surround40 or equalized playback but just front speaker... :S
I know, you could tell me... "man, you have 2 sound cards, use them with pulseaudio and you will have your ******* surround", yes, I thought about it, but it's pretty annoying, every time I change to windows, to switch the audio plugs!!!!
Hope you understand... I want to have surround40 and equalized outputs just like in my winshit to probe it's just as possible!
cacus
May 28th, 2008, 01:02 PM
I found this very funny...
look:
load-module module-alsa-sink device=equalized
#load-module module-alsa-sink device=surround40:CA0106 sink_name=CA0106
That's the line of my default.pa...
Note that I have commented the seccond line, that line was the one that make the surround40...
Is there a way to combine those two into one?
I've tried with both activated but it just did't work. Just gave me no sound system and an error while loading gnome. That's why I commented the second.
At the end of the file, I found some interesting thing...
#load-module module-combine sink_name=combined master= slaves=CA0106,
This code was in the previous default.pa (surround40) too.
This goes at the very end of the file.
Look at "sink_name=combined", master is clear and slave is CA0106... Curious uh?. What the h*** is that comma doing there?, It says slave"s", so is there a possibility to put the equalized sink to get combined or it's just for modules?
load-module module-combine sink_name=combined master= slaves=CA0106,equalized???
When I get back to home i'll tell you what happens :P.
psyke83
May 28th, 2008, 01:11 PM
Man, by setting slave.pcm to "plughw:CA0106" i've just messed up pulseaudio...
Completely removed the server :S...
The last config i was talking about for surround40 was in my default.pa file in /home/user/.pulse... and is the one that I posted in one of my previous posts.
In Fiesty I remember to tweak the .asoundrc for surround40 using duplicate route policy or the presets in alsa surround40, 41 or 51...
Anyway, with that config I lost my dmix possibilities, so i just could play one stream at a time. That's a bug with the CA0601 and ALSA, I've read a lot of information in ALSA docs and it was just possible one thing or the other... dmix (multiple applications streaming) or surround, but not both at the same time.
So, my bet was in pulseaudio and it's promises... and now, I'm with the problem of the equalizer... It's surround40 or equalized playback but just front speaker... :S
I know, you could tell me... "man, you have 2 sound cards, use them with pulseaudio and you will have your ******* surround", yes, I thought about it, but it's pretty annoying, every time I change to windows, to switch the audio plugs!!!!
Hope you understand... I want to have surround40 and equalized outputs just like in my winshit to probe it's just as possible!
Ok, you don't need to worry about your previous problems regarding dmix, as long as you've followed this guide. Let me try to explain.
Forget about PulseAudio for a minute. If you configure /etc/asound.conf to use surround40, then you can only play one stream at a time, correct? I assume that is because surround40 does not allow dmix, which means it would depend on hardware mixing support on your card, which you seem not to have.
Ok, so how does this affect PulseAudio? Well, you have to understand that the PulseAudio server itself can be considered as a layer on top of ALSA, and it is in fact an ALSA client itself (sorry for the oversimplification). If you configure ALSA to use surround40, and configure PulseAudio to point correctly to that surround40 configuration, then ALSA will still not have dmix capability. But that doesn't really matter!
The fact is that the PulseAudio server itself mixes streams, so as long as it has access to the sound card. Hardy's current configuration is suboptimal, as many applications will not interface with PulseAudio, instead trying to use ALSA directly. And of course, if PulseAudio is grabbing the soundcard, it will fail to work. My guide (particularly Part A) solves that problem by coaxing all ALSA applications to direct their audio stream to PulseAudio.
Can you post the surround40 enabled asound.conf so I can show you what needs to be changed?
psyke83
May 28th, 2008, 01:43 PM
I found this very funny...
look:
load-module module-alsa-sink device=equalized
#load-module module-alsa-sink device=surround40:CA0106 sink_name=CA0106
That's the line of my default.pa...
Note that I have commented the seccond line, that line was the one that make the surround40...
Is there a way to combine those two into one?
I've tried with both activated but it just did't work. Just gave me no sound system and an error while loading gnome. That's why I commented the second.
At the end of the file, I found some interesting thing...
#load-module module-combine sink_name=combined master= slaves=CA0106,
This code was in the previous default.pa (surround40) too.
This goes at the very end of the file.
Look at "sink_name=combined", master is clear and slave is CA0106... Curious uh?. What the h*** is that comma doing there?, It says slave"s", so is there a possibility to put the equalized sink to get combined or it's just for modules?
load-module module-combine sink_name=combined master= slaves=CA0106,equalized???
When I get back to home i'll tell you what happens :P.
Ok, make sure you've moved away any settings in ~/.pulse/ and use the supplied default.pa from the guide. Then, edit /etc/asound.conf and change the slave.pcm definition to *one* of these (I'm not sure, but the most likely ones come first):
slave.pcm "plug:surround40:CA0106"
slave.pcm "plug:surround40"
slave.pcm "plughw:surround40:CA0106"
slave.pcm "plughw:surround40"
I think the first or second should work, though.
hyperair
May 28th, 2008, 02:54 PM
I'd suggest leaving out the "plug:" portion. Just this would be sufficient:
slave.pcm "surround40"
psyke83
May 28th, 2008, 03:08 PM
I'd suggest leaving out the "plug:" portion. Just this would be sufficient:
slave.pcm "surround40"
Sorry, that's incorrect. We need to use "plug" because it is interfacing to ALSA's LADSPA plugin.
Edit: no, perhaps you're right, if the surround40 definition is treated as a virtual card, like dmix. He may need to specify the right device, however, since he has two cards.
cacus
May 28th, 2008, 04:57 PM
Ok, make sure you've moved away any settings in ~/.pulse/ and use the supplied default.pa from the guide. Then, edit /etc/asound.conf and change the slave.pcm definition to *one* of these (I'm not sure, but the most likely ones come first):
slave.pcm "plug:surround40:CA0106"
slave.pcm "plug:surround40"
slave.pcm "plughw:surround40:CA0106"
slave.pcm "plughw:surround40"
I think the first or second should work, though.
None worked, I ran out of pulseaudio just like the last try.
this is the config I found for having surround in CA0106 in .asoundrc.
pcm.!dmix {
type plug
slave {
pcm surround51
channels 6
}
}
pcm.!default {
type plug
slave.pcm "dmix"
slave.channels 6
route_policy duplicate
}
Could it be combined with the equalized setting?
psyke83
May 28th, 2008, 05:04 PM
None worked, I ran out of pulseaudio just like the last try.
this is the config I found for having surround in CA0106 in .asoundrc.
pcm.!dmix {
type plug
slave {
pcm surround51
channels 6
}
}
pcm.!default {
type plug
slave.pcm "dmix"
slave.channels 6
route_policy duplicate
}
Could it be combined with the equalized setting?
You don't want to use dmix, it's unnecessary and introduces extra latency. Backup ALL your customizations (asound.conf or .asoundrc, any changes to /etc/pulse/* files), and follow my guide.
So, after making backups:rm ~/.asound.conf
sudo rm /etc/asound.conf
sudo dpkg -P --force-depends pulseaudio
sudo apt-get install pulseaudio
That will restore your PulseAudio config to default. Follow the guide again (Part A & D), and then edit /etc/asound.conf and *only* change the slave.pcm line to one of the suggested settings I gave previously (I see you're using surround51, so replace all instances of surround40 with that).
By the way, the reason it didn't work for you is that PulseAudio expects to see an "equalized" device definition in /etc/asound.conf or ~/.asoundrc, and your ~/.asoundrc was conflicting with that.
If PulseAudio still won't work, paste the verbose output here, i.e.
pkill pulseaudio; pulseaudio -vv
cacus
May 28th, 2008, 07:32 PM
It's rocking now!!!!
:D
Listen, I've lost almost all my afternoon but worth it.
Didn't read your suggestions before making my tweaks but I think this is no more necessary.
Here's what I did:
First, in /etc/asound.conf:
[...]
pcm.equalizer {
type ladspa
slave.pcm "plug:surround40"
path "/usr/lib/ladspa"
[...]
Just to check, in /etc/pulse/daemon.conf:
[...]
default-sample-channels = 4
[...]
In /etc/pulse/default.pa:
[...]
load-module module-alsa-sink device=equalized
[...]
That's gonna work for any Audigy2 LS (or any other CA0106) I guess... Just change surround40 with the option you need taking care about the sample channels in the daemon.conf. (for surround41, 5 channels; surround51, 6 channels; surround71, 8 channels).
I really don't know why I didn't find it before, because I've already tried that config, maybe I forgot to completely reboot the system and just ctrl+alt+backspace (which I don't know why don't work for this kind of stuff) and mess up myself trying pathetic config combinations.
Sorry about the bother, and really thanks a lot. I messed it just for being a stupid anti-reboot silly person.
Greetings from Argentina.
cacus
psyke83
May 28th, 2008, 07:46 PM
It's rocking now!!!!
:D
I'm glad you got it working ;). By the way, you don't need to reboot after tweaking PulseAudio; all you need to do is kill the process and restart it, i.e.:
pkill pulseaudio; pulseaudio
timothius
May 29th, 2008, 05:10 AM
Hi, I did fix number one and now I get this on bootup:
May 29 00:19:56 hplappy kernel: [ 47.799470] ALSA /build/buildd/linux-ubuntu-modules-2.6.24-2.6.24/debian/build/build-generic/sound/alsa-driver/pci/ac97/ac97_codec.c:2061: AC'97 1 does not respond - RESET
May 29 00:19:56 hplappy kernel: [ 47.833344] ALSA /build/buildd/linux-ubuntu-modules-2.6.24-2.6.24/debian/build/build-generic/sound/alsa-driver/pci/ac97/ac97_codec.c:2070: AC'97 1 access is not valid [0xffffffff], removing mixer.
May 29 00:19:56 hplappy kernel: [ 47.855456] ALSA /build/buildd/linux-ubuntu-modules-2.6.24-2.6.24/debian/build/build-generic/sound/alsa-driver/pci/ali5451/ali5451.c:1927: ali mixer 1 creating error..
I can't get rid of these messages whatever I do. Any ideas? Thanks.
psyke83
May 29th, 2008, 09:01 AM
Hi, I did fix number one and now I get this on bootup:
May 29 00:19:56 hplappy kernel: [ 47.799470] ALSA /build/buildd/linux-ubuntu-modules-2.6.24-2.6.24/debian/build/build-generic/sound/alsa-driver/pci/ac97/ac97_codec.c:2061: AC'97 1 does not respond - RESET
May 29 00:19:56 hplappy kernel: [ 47.833344] ALSA /build/buildd/linux-ubuntu-modules-2.6.24-2.6.24/debian/build/build-generic/sound/alsa-driver/pci/ac97/ac97_codec.c:2070: AC'97 1 access is not valid [0xffffffff], removing mixer.
May 29 00:19:56 hplappy kernel: [ 47.855456] ALSA /build/buildd/linux-ubuntu-modules-2.6.24-2.6.24/debian/build/build-generic/sound/alsa-driver/pci/ali5451/ali5451.c:1927: ali mixer 1 creating error..
I can't get rid of these messages whatever I do. Any ideas? Thanks.
If you google the error, it appears to be kernel related. Did you do a kernel upgrade? If that's the case, boot to the old kernel and see if it's fixed. Otherwise see Appendix 2... but it's not PulseAudio related.
djhig
May 29th, 2008, 10:51 AM
Thanks, i was getting really sick of the firefox crashes with libflashsupport this did the business :)
timothius
May 29th, 2008, 11:22 AM
If you google the error, it appears to be kernel related. Did you do a kernel upgrade? If that's the case, boot to the old kernel and see if it's fixed. Otherwise see Appendix 2... but it's not PulseAudio related.
Thats the thing, I followed the removal instructions to the letter and I still get:
[ 49.901133] ALSA /build/buildd/linux-ubuntu-modules-2.6.24-2.6.24/debian/build/build-generic/sound/alsa-driver/pci/ac97/ac97_codec.c:2061: AC'97 1 does not respond - RESET
[ 49.936109] ALSA /build/buildd/linux-ubuntu-modules-2.6.24-2.6.24/debian/build/build-generic/sound/alsa-driver/pci/ac97/ac97_codec.c:2070: AC'97 1 access is not valid [0xffffffff], removing mixer.
[ 49.958047] ALSA /build/buildd/linux-ubuntu-modules-2.6.24-2.6.24/debian/build/build-generic/sound/alsa-driver/pci/ali5451/ali5451.c:1927: ali mixer 1 creating error.
I'm using the default kernel that installs when you install from the Hardy CD.
It seems that some configuration file change or something has been left even after install. I have no idea how to fix this :(
Thanks for the help.
psyke83
May 29th, 2008, 11:39 AM
It seems that some configuration file change or something has been left even after install. I have no idea how to fix this :(
Thanks for the help.
If you follow the removal instructions of Appendix 2, then all configuration files and packages will be restored to Hardy defaults. Again as I said, this is a kernel issue and not related to PulseAudio or its configuration.
Was sound working for you before you tried this guide? Does booting from the LiveCD present this issue as well? I cannot troubleshoot a kernel issue for your hardware since it's different to mine, and I don't believe this guide caused the issue. The removal instruction will restore your system to its original state.
For a start to your troubleshooting, see these bug reports and links:
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/65529
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/94333
http://groups.google.com/group/linux.debian.user/browse_thread/thread/45e7d1ef18639869
timothius
May 29th, 2008, 11:45 AM
If you follow the removal instructions of Appendix 2, then all configuration files and packages will be restored to Hardy defaults. Again as I said, this is a kernel issue and not related to PulseAudio or its configuration.
Was sound working for you before you tried this guide? Does booting from the LiveCD present this issue as well? I cannot troubleshoot a kernel issue for your hardware since it's different to mine, and I don't believe this guide caused the issue. The removal instruction will restore your system to its original state.
For a start to your troubleshooting, see these bug reports and links:
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/65529
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/94333
http://groups.google.com/group/linux.debian.user/browse_thread/thread/45e7d1ef18639869
Ah, I might have had the message before I followed the guide - I only checked after I followed the guide, so assumed that it was the cause. I'll try to boot from the live cd to see.
My audio works the same currently as it always has - the sound crackles and randomly speeds up and down. I was following the guide as it was linked from a bug report.
psyke83
May 29th, 2008, 11:48 AM
My audio works the same currently as it always has - the sound crackles and randomly speeds up and down. I was following the guide as it was linked from a bug report.
Sound crackling certainly can occur because of PulseAudio, but speeding up and down does not. This indicates a problem with your audio chipset and not PulseAudio, so the fix is probably needed either in ALSA or with a BIOS update. The links I posted have lots of useful information.
timothius
May 29th, 2008, 12:25 PM
Sound crackling certainly can occur because of PulseAudio, but speeding up and down does not. This indicates a problem with your audio chipset and not PulseAudio, so the fix is probably needed either in ALSA or with a BIOS update. The links I posted have lots of useful information.
Yup you were right :) I booted from the livecd and checked dmesg - those errors were present.
I'll look into configuring ALSA (although i've tried in vain for days) and check my bios version.
Pablo Somebody
May 30th, 2008, 04:57 PM
I had PulseAudio working fine under gutsy, and it works under Heron, except for one issue: it doesn't start on boot. If I manually run 'pulseaudio --daemonize' it works fine.
'/etc/init.d/pulseaudio start' doesn't do anything because 'PULSEAUDIO_SYSTEM_START' in /etc/default/pulseaudio is set to zero. I could change it to 1 so it runs, but all the warnings suggest that's it's not a recommended way to run it. When & where is Heron meant to start the PulseAudio daemon?
hyperair
May 30th, 2008, 07:47 PM
Open Sound Preferences (System->Preferences->Sound). Then go to the Sound tab. Enable software mixing. It says ESD there, but it'll start Pulseaudio when booting.
psyopper
May 31st, 2008, 12:19 AM
Wow...
This seems like a LOT of work for something that should have been done pre-release, especially with all the fan-fare associated with PulseAudio going into Hardy. Makes me a little afraid of doing it and hoping they actually get PulseAudio done correctly in Intrepid.
All I want is an EQ for Linux...
Pablo Somebody
May 31st, 2008, 05:24 AM
Open Sound Preferences (System->Preferences->Sound). Then go to the Sound tab. Enable software mixing. It says ESD there, but it'll start Pulseaudio when booting.
Thanks, I tried that but it hasn't worked; neither PulseAudio or ESD is running. I'm running kubuntu, so it's the slightly System Settings->Sound&Multimedia->SoundSystem dialog that I am lookng at. Now I'm thinking about it, when I had PulseAudio successfully running on Gusty, I'm pretty sure PulseAudio was an option from the dropdown box and that's what I had selected. Now it isn't shown on the list.
olavjunior
May 31st, 2008, 05:53 AM
Tanks! Now I can hear flashsound at the same time as exaile :)
But after installing the updated debs and making asound.conf, awn volume control stopped woring. Any idea how I can fix this?
File "/usr/lib/awn/applets/volume-control/volume-control.py", line 67, in __init2
self.drawMainDlog()
File "/usr/lib/awn/applets/volume-control/volume-control.py", line 138, in drawMainDlog
volume.set_value(self.backend.getVolume())
File "/usr/lib/awn/applets/volume-control/volume-control.py", line 227, in getVolume
return alsaaudio.Mixer(self.channel).getvolume()[0]
alsaaudio.ALSAAudioError: Unable to find mixer control 'PCM',0
EOLVED: It could be fixed trough gconf editor. Changed PCM to Master in apps-a-w-n-applets-volume. Great :)
psyke83
June 3rd, 2008, 11:48 PM
I had PulseAudio working fine under gutsy, and it works under Heron, except for one issue: it doesn't start on boot. If I manually run 'pulseaudio --daemonize' it works fine.
'/etc/init.d/pulseaudio start' doesn't do anything because 'PULSEAUDIO_SYSTEM_START' in /etc/default/pulseaudio is set to zero. I could change it to 1 so it runs, but all the warnings suggest that's it's not a recommended way to run it. When & where is Heron meant to start the PulseAudio daemon?
I'm sorry, but I don't use Kubuntu, you may have better luck on the http://kubuntuforums.net (Kubuntu forums). If you installed PulseAudio from Gutsy, there's a good chance you're using a non-standard configuration and it's impossible to tell what you've changed/tweaked etc., so it's hard to diagnose the problem.
psyke83
June 3rd, 2008, 11:55 PM
Hi, I made a small update to the guide (v2.3). Previously, GDM was blocked from using the sound card as it was explicitly trying to connect to a PulseAudio server before it was available (as it is run per-user). If you already followed this guide previously, it's not necessary to go through the guide again, just do the following:
$ cp /etc/asound.conf ~/.asoundrc
$ sudo rm /etc/asound.conf
GDM should now work correctly, but you will need to copy your .asoundrc configuration to each user's ~/ (Home) folder if you have multiple users.
psyke83
June 4th, 2008, 12:07 AM
Can I make a small request? If anyone using a laptop experiences distorted sound from the built-in speakers, can you please give feedback from Step C (the equalizer)?
Please let me know:
a) your laptop brand and model
b) your audio codec information:$ cat /proc/asound/card?/codec97#0/ac97#0-0
c) your impression of the change in audio quality - better or worse?
d) optionally, if you have tried different LADSPA settings that you believe to be better, share them!
I'd really appreciate any feedback!
Thanks.
juanmanuelagueda
June 4th, 2008, 05:52 AM
First of all great work! Thanks!!!!
I have applied part A B and C of the howto, and now I don´t have problems playing music with rythmbox, exaile and I´m
able to play youtube videos at the same time without poblem. But while playing videos with vlc, from time to time,
the audio stutters. If I play the same videos with totem the stuttering is less noticeable but its still there.
I´ve tried switching sound to alsa and fiddling with pulseaudio config (priority, fragments) but without any
improvement.
Am I missing something?
The specs of my computer:
Pentium 4 3.2Ghz (hyperthreading) 1GB ram
Ubuntu hardy heron 8.04 Kerner 2.6.24.18
EDIT: sound card
VIA Technologies, Inc. VIA High Definition Audio Controller (rev 10)
Any help will be appreciated! Thanks a lot :D
------------------
Added sound card
eryksun
June 4th, 2008, 09:44 AM
Thanks for this latest update. I was starting to miss the drum sound in GDM. :)
On an unrelated note, I've found that some sites fail to recognize the Flash 10 beta, though they work fine with Flash 9. I don't need audio in these picky sites, so I reinstalled the repository Flash 9 package and put the beta 10.0 plugin in /opt. galternatives lets me toggle the plugin by modifying "xulrunner-addons-flash".
Ebuntor
June 5th, 2008, 05:11 PM
If I play a .flac file in VLC I still get some skipping and/or popping sound although luckily it's gone when i play mp3's or other files.
I've been messing around with the default-fragments and default-fragment-size-msec settings but no matter what I try it just won't go away when playing .flac's.
psyke83
June 5th, 2008, 05:28 PM
First of all great work! Thanks!!!!
I have applied part A B and C of the howto, and now I don´t have problems playing music with rythmbox, exaile and I´m
able to play youtube videos at the same time without poblem. But while playing videos with vlc, from time to time,
the audio stutters. If I play the same videos with totem the stuttering is less noticeable but its still there.
I´ve tried switching sound to alsa and fiddling with pulseaudio config (priority, fragments) but without any
improvement.
Am I missing something?
The specs of my computer:
Pentium 4 3.2Ghz (hyperthreading) 1GB ram
Ubuntu hardy heron 8.04 Kerner 2.6.24.18
EDIT: sound card
VIA Technologies, Inc. VIA High Definition Audio Controller (rev 10)
Any help will be appreciated! Thanks a lot :D
------------------
Added sound card
VLC does not interact well with PulseAudio sometimes, unfortunately. Changing the fragment values does help reduce the problem, but not eliminate, unfortunately. There's no solution as of yet.
fontenot_1031
June 5th, 2008, 06:51 PM
currently I have all of my sounds running through OSS. The shuttering audio has been fixed but I still can't run two applications at once that both use sound.
I was using the stable flash from adobe.com since upgrading to the beta closing a firefox tab that was a flash movie (or a youtube video) closes firefox even if other tabs are open. The beta also did not resolve the sound issue (youtube videos won't play any sound even if rhythmbox is paused).
psyke83
June 5th, 2008, 08:09 PM
currently I have all of my sounds running through OSS. The shuttering audio has been fixed but I still can't run two applications at once that both use sound.
I was using the stable flash from adobe.com since upgrading to the beta closing a firefox tab that was a flash movie (or a youtube video) closes firefox even if other tabs are open. The beta also did not resolve the sound issue (youtube videos won't play any sound even if rhythmbox is paused).
You're using a suboptimal configuration. Forget about my guide and PulseAudio for a second, and take note:
1. ALSA provides OSS compatibility kernel drivers, but software mixing does not work correctly if you run an OSS application directly.
2. To allow OSS applications to share sounds with other applications, you need to use the "aoss" wrapper, available in the package "alsa-oss". This wrapper tricks the application into redirecting its sound to ALSA.
Now, let's add PulseAudio to the equation:
1. PulseAudio by default uses ALSA to interface with the hardware (i.e. hw:0,0). Although I believe OSS support is present, I haven't tested it, and it's not recommended to configure PulseAudio like this.
2. PulseAudio is an audio abstraction layer, it runs on top of ALSA or OSS and it is NOT a replacement for either of them.
3. PulseAudio provides its own OSS emulation support, using the "padsp" wrapper (it's the PulseAudio version of "aoss").
You need to reconfigure your system, therefore. Go to System/Preferences/Sound, and set every every possible option to "Autodetect". If you've manually edited configuration files, or installed OSS v4, then you'll have to figure out how to cleanly remove it and reconfigure your system to use ALSA yourself, I'm afraid.
Edit: just to clarify - even though I explained about "aoss" and "padsp", you should not use either solution. You should configure GStreamer applications to "Autodetect" (as mentioned above), and generally use ALSA or PulseAudio-compatible applications. If you have applications that only support OSS output (e.g. old games), use the "padsp" wrapper (which will work if PulseAudio is working correctly on your system).
michaelzap
June 6th, 2008, 12:51 AM
Just so you know, the character " ; " is the comment code, meaning that it causes those lines to get completely ignored... Therefore you're using the default PulseAudio values.
OMG! I was crying because your fixes didn't seem to be working, and my audio was so stuttery that stuttery didn't even describe it. You might want to call special attention to those semicolons, because removing them made all the difference!
juanmanuelagueda
June 6th, 2008, 04:22 AM
VLC does not interact well with PulseAudio sometimes, unfortunately. Changing the fragment values does help reduce the problem, but not eliminate, unfortunately. There's no solution as of yet.
What a pity! I´ll give totem a try!
Anyway, I´ll check vlc forums. Maybe there´s a workaround.
Thanks psyke83!
psyke83
June 6th, 2008, 11:18 AM
OMG! I was crying because your fixes didn't seem to be working, and my audio was so stuttery that stuttery didn't even describe it. You might want to call special attention to those semicolons, because removing them made all the difference!
Thanks for pointing that out, I've added a note to the guide.
neymac
June 6th, 2008, 04:58 PM
I used the flac test file with totem-gstreamer and all speakers worked.
But with mplayer there was no sound when I select pulseaudio as audio output (mplayer -ao pulse Multichannel_test_flac_nonstandard_8.flac).
Is there any way to allow mplayer to play pulse?
There is a "pulse" option when I select preferences in mplayer, but if I select it => no sound.
By the way, at the terminal it looks like the file was playing (no error message), but no sound.
psyke83
June 6th, 2008, 05:01 PM
I used the flac test file with totem-gstreamer and all speakers worked.
But with mplayer there was no sound when I select pulseaudio as audio output (mplayer -ao pulse Multichannel_test_flac_nonstandard_8.flac).
Is there any way to allow mplayer to play pulse?
There is a "pulse" option when I select preferences in mplayer, but if I select it => no sound.
By the way, at the terminal it looks like the file was playing (no error message), but no sound.
Use the PulseAudio Manager to see if audio is being directed to PulseAudio successfully. If it is using Pulse, an application will be listed in the client list along with a volume control.
neymac
June 6th, 2008, 05:16 PM
This is what I have in pulseaudio manager client window:
http://pix.nofrag.com/c/4/c/a8a67eddd0bc3cbbc2d70ba46b43c.png (http://pix.nofrag.com/c/4/c/a8a67eddd0bc3cbbc2d70ba46b43c.html)
When I run mplayer -ao pulse .....flac, MPlayer appears at the window above, but no sound.
As I have two sound devices, I think the sound is going to the one that is not connected to the speakers.
I'll try figure out how change the default sink device.
I choosed the "other" sink device and it worked (pulse sound in mplayer).
michaelzap
June 6th, 2008, 09:54 PM
Sigh. OK so after these fixes my audio files play without horrible skipping, but now my volume level goes haywire constantly (for example in the course of one song the volume is constantly going up and down throughout). Any idea what the sam hill is going on with this?
Up until the updates earlier this week I had no audio problems whatsoever...
psyke83
June 6th, 2008, 10:49 PM
Sigh. OK so after these fixes my audio files play without horrible skipping, but now my volume level goes haywire constantly (for example in the course of one song the volume is constantly going up and down throughout). Any idea what the sam hill is going on with this?
Up until the updates earlier this week I had no audio problems whatsoever...
You're not really giving much information to go on, e.g. what application(s) present this issue?
Use PulseAudio Volume Control (pavucontrol) to see if the application is really using PulseAudio, and if it is, see if the volume sliders visibly change when you hear the volume change.
Were you referring to software updates or updates to this guide? If you're desperate, undo the changes made by this guide (Appendix 2) and see if the problem goes away.
michaelzap
June 6th, 2008, 11:14 PM
You're not really giving much information to go on, e.g. what application(s) present this issue?
Sorry. I guess I was hoping that this is a common enough experience that a cursory description would be sufficient. I guess not.
Use PulseAudio Volume Control (pavucontrol) to see if the application is really using PulseAudio, and if it is, see if the volume sliders visibly change when you hear the volume change.
I'm playing music in Amarok now, and it does appear in the PA Volume Control applet. The sliders do not change when the volume goes up and down (they remain at 100%). Amarok's volume indicator doesn't change either.
I just tried playing the same music using Rythmbox instead, and it displayed a slight variation of this volume level freak-out behavior. When I first started playing the file, it was so incredibly loud that I expect the neighbors now hate me. I had to reduce the volume to about 6% in order to be roughly equivalent to Amarok's 80% setting. Then it got very quiet again, but more than that the difference between percentages became very slight (meaning that 5% and 95% were almost the same). As I was playing with that, the volume suddenly shot up into the stratosphere again and set off car alarms all over the neighborhood (OK not really). The PA Volume Control continued to show 100% for Rhythmbox throughout this as well.
Were you referring to software updates or updates to this guide? If you're desperate, undo the changes made by this guide (Appendix 2) and see if the problem goes away.
I wasn't referring to the changes I made based on your guide. I was referring to software updates pushed out via the update manager this past week. I had no audio problems at all until sometime this week, and other than the kernel update (which I assume changes everything to some extent) the only audio-related update that I noticed was for Rhythmbox (which I don't use and could remove).
I only tried out your guide after things went screwy, and it stopped the stuttering issue but now I have this new volume level problem (which may have existed prior to making the changes in your guide, since audio was unlistenable before then).
If I boot into Windows my sound is still working as before, so I know that the problem is Ubuntu-related and not my speakers or hardware.
THANKS in advance for any advice you may have.
psyke83
June 7th, 2008, 09:28 AM
I only tried out your guide after things went screwy, and it stopped the stuttering issue but now I have this new volume level problem (which may have existed prior to making the changes in your guide, since audio was unlistenable before then).
If I boot into Windows my sound is still working as before, so I know that the problem is Ubuntu-related and not my speakers or hardware.
THANKS in advance for any advice you may have.
It seems pretty obvious you're suffering from a kernel problem. The first step I would suggest is to boot from Hardy's shipping kernel (2.6.24-16-generic) and see if the issue is present. If you didn't keep the old kernel, you can try the Live CD, although that's not a good way to isolate non-kernel updates that may have caused this issue.
If that doesn't help, try to isolate the source of the problem - is it a problem with PulseAudio or ALSA in general? Kill the running PulseAudio server, and then launch Amarok* or another application that exhibits this bug, and see if it helps.
This will kill the running server: $ pkill pulseaudio
*You may need to temporarily move/delete your ~/.asoundrc file, otherwise audio will fail to play while no PulseAudio server is running.
michaelzap
June 7th, 2008, 04:31 PM
It seems pretty obvious you're suffering from a kernel problem.
Seems like it. I rebooted with the 2.6.24-17-generic kernel and volume is once again under control. I was resisting believing that the kernel was the problem because I didn't notice the audio issues right away after updating it, but I think I must just not have played music for a couple days or something.
So does this mean that my audio driver has a volume control issue with the latest kernel? Anyone else experiencing this? How do I figure out exactly what driver and hardware I have in order to search for a solution and report a problem?
michaelzap
June 7th, 2008, 05:48 PM
Seems like it. I rebooted with the 2.6.24-17-generic kernel and volume is once again under control.
Oops. Sorry. I lied about the volume working properly using the 17 kernel. It took a while before it started to freak out, but after playing music for 20 minutes or so it also started varying wildly. And I've also tried the 16 kernel now and I have the same problem using it.
If I kill the pulseaudio server, rename my ~/.asoundrc file, and change all sound output settings to Alsa, sound plays and still has the volume level problem.
plun
June 8th, 2008, 06:01 AM
Excellent guide... thanks..! :)
Took the time and fixed this.
Running Intrepids repo (some changes) and using Exaile (bzr)
as player including Exailes equalizer. Audigy2 as soundcard
Now I can "blow my ears" again :lolflag:
markbuntu
June 12th, 2008, 06:04 PM
Well, that sorta worked for me. I followed the instructions and some things worked and some didn't. Flash works better and doesn't bother my other sound players like it used to, thank you very much.
But, mplayer did not have any sound, neither did vlc. I got sound in vlc but never in mplayer. The Multimedia Systems Selector would hang when I tried to do anything with it as would Sound. My alsa default sound card selector wouldn't even start.
After extensive fooling around with pulseaudio settings etc I ended up with no sound output at all so I removed asound.conf to trash and pulseaudio from bootup with bum and renabled the alsa utils in System/Administration/Services.
A kind of drastic step I know, but I got tired of going in circles.
But now everything works, everything.
I have never had any luck with pulseaudio and my sound hardware and that saga continues.
AC97 on board and realtek HDMI on ATI Radeon HD3650 video card.
Kernel 2.6.24-19 generic
psyke83
June 12th, 2008, 06:20 PM
After extensive fooling around with pulseaudio settings etc I ended up with no sound output at all so I removed asound.conf to trash and pulseaudio from bootup with bum and renabled the alsa utils in System/Administration/Services.
A kind of drastic step I know, but I got tired of going in circles.
Sorry you didn't get things working... I just hope you realize that there were uninstall instructions in my guide. If you try to use PulseAudio in the future and have issues with applications, the easiest thing to do is:
1. Install "padevchooser" (it will pull in other useful applications)
2. Open either the PulseAudio Manager or PulseAudio Volume Control, and look at the Client or Playback client list.
If an application that is currently playing sound is listed there, then it is using PulseAudio successfully. If an application is playing sound but not listed, then it's using ALSA directly, probably because you didn't follow this guide properly, or it's an OSS application and you forgot to use the "padsp" wrapper.
In the latter case, when an application is using ALSA directly, then PulseAudio will not be able to access the sound card and thus audio mixing will appear broken.
mocha
June 13th, 2008, 02:30 AM
Does anyone know how to boost the output of the pulseaudio PCM playback? I have a Intel HDA controller, AD1988 chip actually. The stereo mix playback level has always been low in Linux under Alsa as well. Is there any files I could dig into to boost the volume? For example, even with all the mixer playback sliders at max, the bars on the pulseaudio playback meter are still between 50% and 75%. They should be clipping with those settings. Line-In boost is fine, it's just the internal mix (aka stereo mix or analog mix) or whatever you want to call it.
citral
June 13th, 2008, 01:10 PM
Life saver guide this! Thanks a bunch. These steps should've been in Hardy by default.:KS
monstermudder78
June 13th, 2008, 01:18 PM
Thanks! I agree 100% with this guy^^^
jukingeo
June 13th, 2008, 07:51 PM
I followed the procedure and unfortunately I am dead in the water (soundwise).
Prior to following the guide I mainly had trouble with streaming audio on the internet and Gens was working, but distorted.
Now after installation I have nothing, nada, iksnay.
psyke83
June 13th, 2008, 07:53 PM
I followed the procedure and unfortunately I am dead in the water (soundwise).
Prior to following the guide I mainly had trouble with streaming audio on the internet and Gens was working, but distorted.
Now after installation I have nothing, nada, iksnay.
Follow Appendix 2, then.
markbuntu
June 13th, 2008, 10:42 PM
Sorry you didn't get things working... I just hope you realize that there were uninstall instructions in my guide. If you try to use PulseAudio in the future and have issues with applications, the easiest thing to do is:
1. Install "padevchooser" (it will pull in other useful applications)
2. Open either the PulseAudio Manager or PulseAudio Volume Control, and look at the Client or Playback client list.
If an application that is currently playing sound is listed there, then it is using PulseAudio successfully. If an application is playing sound but not listed, then it's using ALSA directly, probably because you didn't follow this guide properly, or it's an OSS application and you forgot to use the "padsp" wrapper.
In the latter case, when an application is using ALSA directly, then PulseAudio will not be able to access the sound card and thus audio mixing will appear broken.
I followed your guide EXACTLY, every step of the way. All I know is that following it broke a lot of my stuff in the same manner as the last time I tried to get pulseaudio to work using a different guide. Luckily, I know how to recover to alsa in a quick and easy manner which I figured out the last time.
Besides, I really don't care what I use as long as it all "just works" and it didn't "just work" for me.
Maybe you should explain this padevchooser thing in the how to. Is it similar asoundconf-gtk?
Anyway, thanks for taking the time to do all this. And thanks for the new flash and libasound2. They seem to be a great improvement. I will probably give pulseaudio another go round in a few months because I would really like to see it working on my machine.
Cheers, and no hard feelings OK.
sammydee
June 14th, 2008, 07:02 AM
Anybody struggling with surround sound in pulseaudio, or having problems with it, you should try this thread:
Howto: Surround sound in pulseaudio (http://ubuntuforums.org/showthread.php?t=795525)
If you have problems, post it there and we'll help you out :-)
psyke83
June 14th, 2008, 12:24 PM
Hi everyone,
I have made a major update to the guide, adding new instructions (as updated packages were uploaded to hardy-proposed) and giving some new troubleshooting information.
Users that followed the guide prior to v2.5 simply need to "downgrade" some Intrepid package versions to the hardy-proposed versions, to keep their system consistent:
$ sudo apt-get install libasound2/hardy-proposed libasound2-plugins/hardy-proposed libasound2-dev/hardy-proposed
jukingeo
June 14th, 2008, 12:30 PM
Hi everyone,
I have made a major update to the guide, adding new instructions (as updated packages were uploaded to hardy-proposed) and giving some new troubleshooting information.
Users that followed the guide prior to v2.5 simply need to "downgrade" some Intrepid package versions to the hardy-proposed versions, to keep their system consistent:
$ sudo apt-get install libasound2/hardy-proposed libasound2-plugins/hardy-proposed libasound2-dev/hardy-proposed
Would this fix the "no sound" problem I am now having? I also now have Ubuntu Studio. Since I wanted it anyway I figured I would load it on now instead of getting everything fixed and then putting more things out of whack by loading it on afterwards.
psyke83
June 14th, 2008, 12:34 PM
Would this fix the "no sound" problem I am now having? I also now have Ubuntu Studio. Since I wanted it anyway I figured I would load it on now instead of getting everything fixed and then putting more things out of whack by loading it on afterwards.
NO. If your system does not play any sounds, this guide will not help. You probably have a kernel or ALSA issue.
jukingeo
June 14th, 2008, 12:44 PM
NO. If your system does not play any sounds, this guide will not help. You probably have a kernel or ALSA issue.
Ok, but if you backpedal a bit to a few posts ago, I followed you original guide to fixing the streaming audio on the internet and now I have NO sound because of that.
Prior to following your guide I HAD sound on most of my applications. Some applications had audio, but distortion as well. The internet audio/video was so choppy it was unusable. So that is why I followed your original procedure, but now I have no audio at all.
If it was a Kernel problem, last night I upgraded to Ubuntu Studio and that has the latest Kernel, but it is the RT kernel. I was hoping that would correct at least some issues, but alas, it hasn't.
I just need to know what to do to get my audio fully functional again.
I pretty much installed all the programs that I am going to work with (and I can run them down for you). So I would like to get them all going.
As a quick recap I am running a few console emulators (Stella, Gens, NES, ZSNES, N64) and I am also running DosBox. I do have a few native Linux games loaded on as well such as SuperTux and Neverball.
Then I need the streaming audio/video to work on the internet.
Finally, pretty much all the audio/video applications that come with Ubuntu Studio I would like to work, but mainly I need Ardour, RoseGarden, Audacity, Cinelerra, Open Movie Editor, Jack rack, and Kino to work.
Am I asking too much of Ubuntu for that? I certainly hope not!
Geo
psyke83
June 14th, 2008, 12:55 PM
Ok, but if you backpedal a bit to a few posts ago, I followed you original guide to fixing the streaming audio on the internet and now I have NO sound because of that.
Ah my apologies, I had forgotten your previous post. In that case, what I recommend is that you follow Appendix C (to revert changes), but it's not necessary to restore any backup files. Make sure you a) delete ~/.asoundrc* and /etc/asound.conf, and b) have the "ubuntu-desktop" or "ubuntustudio-desktop" metapackages installed (just in case some packages were accidentally removed).
Then perform the following test:
1. Ensure all the playback streams are set to "Autodetect" in System / Preferences / Sound.
1. Close all media players, etc.
2. Open a terminal, and kill the pulseaudio process:
$ pkill pulseaudio
3. Open a media player and try to play some audio.
If that works, then your sound is functioning when using ALSA directly. I would then recommend that you try following the guide again, to hopefully fix PulseAudio for you.
Can you also provide any relevant information? For example, did you notice packages getting uninstalled that seemed suspicious? Are you on i386 or amd64?
timzak
June 14th, 2008, 01:36 PM
psyke83,
Shouldn't you warn users that enabling the hardy-proposed, then doing a dist-upgrade will basically update all of your applications to not-ready-for-primetime versions? It will also take forever to download and update all these apps. It even upgrades the kernel...is the .19 kernel even considered stable? I'm typing this as all this is happening and praying that nothing breaks after I reboot the computer.
psyke83
June 14th, 2008, 01:38 PM
psyke83,
Shouldn't you warn users that enabling the hardy-proposed, then doing a dist-upgrade will basically update all of your applications to not-ready-for-primetime versions? It will also take forever to download and update all these apps. It even upgrades the kernel...is the .19 kernel even considered stable? I'm typing this as all this is happening and praying that nothing breaks after I reboot the computer.
Hmm, I guess so, although some packages must be upgraded for PulseAudio to work correctly.
Edit: I've updated the guide, thanks for the suggestion.
timzak
June 14th, 2008, 02:42 PM
Hmm, I guess so, although some packages must be upgraded for PulseAudio to work correctly.
Edit: I've updated the guide, thanks for the suggestion.
Thanks, everything seems to be working okay after following your howto. Youtube videos don't crash the system anymore. I noticed that Firefox got updated too. Not sure which version is in hardy-proposed, but probably RC2?
Thanks for your help!
billybag
June 15th, 2008, 11:07 AM
sorry if someone already mentrioned this. i am in a hurry i have to get to work.
My PulseAudio is waaay too quiet. Way more quiet then ALSA. I have my laptop hooked up to my stereo and i need to have my stereo AND laptop at both max volumes and it isnt enough... How can this be fixed?
psyke83
June 15th, 2008, 11:10 AM
sorry if someone already mentrioned this. i am in a hurry i have to get to work.
My PulseAudio is waaay too quiet. Way more quiet then ALSA. I have my laptop hooked up to my stereo and i need to have my stereo AND laptop at both max volumes and it isnt enough... How can this be fixed?
First, open PulseAudio Volume Control (available from Device Chooser) and make sure the volume for PulseAudio playback streams is at 100%.
Secondly, make sure it's really a problem with Pulse and not ALSA. Temporarily move/delete your /etc/asound.conf and ~/.asoundrc files, kill the pulseaudio server and try to play sound.
So:
1. aplay /usr/share/sounds/startup.wav
2. sudo rm /etc/asound.conf ~/.asoundrc
3. pkill pulseaudio
4. aplay /usr/share/sounds/startup.wav
BlueSkyNIS
June 15th, 2008, 02:35 PM
Hello psyke,
Thanks very much for this post! :)
Please, correct miss type in following:
$ analyzeplugin /usr/lib/ladspa/mbeq_1197.so
should be:
$ analyseplugin /usr/lib/ladspa/mbeq_1197.so
Cheers :popcorn:
psyke83
June 15th, 2008, 03:11 PM
Please, correct miss type in following:
Thanks, it's fixed now!
bowie101
June 16th, 2008, 01:49 PM
Hello. I followed your guide, as far as I can tell, to the letter.
Alienware area 51 laptop, Heron, i386, etc etc.
Well, orginally, I installed Flash 9, then had problems, then installed flash 10, then back to 9, and now, hopefully with following your guide, back to 10.
FF RC2.
It worked for just a bit (I think). When all cutting and pasting from your guide was done, (Part A: Required Fixes,
Part B: Adobe Flash & PulseAudio Fix, & Part D: Equalizer Support), FF worked, for the remaining 2 minutes that I used it. I went to YouTube, and it worked fine. Then I open Opera and Konqueror. (I'm in gnome, but have K installed as well, and therefore Konqueror. BTW, I also have XFCE installed and after installing ubuntu, installed the metapackage for ubuntu-studio on top. IS this relevant? you decide.) anyway...open Opera and Konqueror and the same youtube link in both browsers. Video works, no sound. Sound only works now in FF.
So I restart the machine.
Now FF is crashing, again. Not as much as before, but still, crashing immediately after launch, etc. So apparently, no change.
Suggestions? Sorry, I just found this thread today, and after scaning the first 3rd of the threads, I thought I'd just ask. Maybe the solution is already in here, in which case, just direct me to it, and I apologize.
btw, I followed part D just b/c i am using a laptop, and as a precaution. didn't experience this problem before.
thanks, b
psyke83
June 16th, 2008, 02:30 PM
Suggestions? Sorry, I just found this thread today, and after scaning the first 3rd of the threads, I thought I'd just ask. Maybe the solution is already in here, in which case, just direct me to it, and I apologize.
btw, I followed part D just b/c i am using a laptop, and as a precaution. didn't experience this problem before.
From your post it seems that you tested Firefox immediately after applying the changes here. Did you read the warning about PulseAudio changes not taking effect until a reboot or logging out and back in?
If Firefox is crashing immediately upon startup, it would seem that there's something wrong with your system unrelated to PulseAudio. The cause of crashes for some users with the "libflashsupport" package installed (that shouldn't be installed on a user's system by default anymore) only causes Firefox to crash when closing and opening pages with flash content (e.g. when you visit Youtube, it works fine the first time, but when you click on another video link, then it can crash).
So, my advice to you is:
1. Remove the EQ changes (Part D), so we can make sure that's not the problem (besides, you shouldn't be using those settings if your audio quality is already fine). This is the easiest way to do it:
$ sudo dpkg --force-depends -P pulseaudio
$ sudo apt-get install pulseaudio
Log out and back in for changes to take effect.
2. Close *all* applications that play audio, and follow Appendix B, testing just one application at a time. Be sure to test Firefox, Opera and Konqueror separately. Just keep in mind that these applications only show an entry in the PulseAudio Volume Control when they are playing audio!
Let me know the results, and if you get the "A" result, try playing audio from more than one application at once (ensure they all show correctly in the Volume Control window).
jukingeo
June 16th, 2008, 06:46 PM
Ah my apologies, I had forgotten your previous post. In that case, what I recommend is that you follow Appendix C (to revert changes), but it's not necessary to restore any backup files. Make sure you a) delete ~/.asoundrc* and /etc/asound.conf, and b) have the "ubuntu-desktop" or "ubuntustudio-desktop" metapackages installed (just in case some packages were accidentally removed).
Then perform the following test:
1. Ensure all the playback streams are set to "Autodetect" in System / Preferences / Sound.
1. Close all media players, etc.
2. Open a terminal, and kill the pulseaudio process:
$ pkill pulseaudio
3. Open a media player and try to play some audio.
If that works, then your sound is functioning when using ALSA directly. I would then recommend that you try following the guide again, to hopefully fix PulseAudio for you.
Can you also provide any relevant information? For example, did you notice packages getting uninstalled that seemed suspicious? Are you on i386 or amd64?
I tried to do Appendix C of your guide, but the last 4 or 5 instructions stated that it there is no such file or directory, etc. Here is what happened in my terminal:
geo@geo-desktop:~$ sudo dpkg -P --force-depends pulseaudio
dpkg - warning: ignoring request to remove pulseaudio which isn't installed.
geo@geo-desktop:~$ sudo apt-get install flashplugin-nonfree/hardy libsdl1.2debian-alsa pulseaudio
Reading package lists... Done
Building dependency tree
Reading state information... Done
Selected version 9.0.124.0ubuntu2 (Ubuntu:8.04/hardy) for flashplugin-nonfree
You might want to run `apt-get -f install' to correct these:
The following packages have unmet dependencies:
libsdl1.2debian-all: Conflicts: libsdl1.2debian-alsa but 1.2.13-1ubuntu1.1 is to be installed
libsdl1.2debian-alsa: Conflicts: libsdl1.2-all
Conflicts: libsdl1.2debian-all but 1.2.13-1ubuntu1.1 is to be installed
E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution).
geo@geo-desktop:~$ sudo rm ~/.asoundrc* /etc/asound.conf /etc/libao.conf
rm: cannot remove `/home/geo/.asoundrc*': No such file or directory
rm: cannot remove `/etc/asound.conf': No such file or directory
rm: cannot remove `/etc/libao.conf': No such file or directory
geo@geo-desktop:~$ sudo cp ~/pulse-backup/asound.conf /etc/
cp: cannot stat `/home/geo/pulse-backup/asound.conf': No such file or directory
geo@geo-desktop:~$ sudo cp ~/pulse-backup/libao.conf /etc/
cp: cannot stat `/home/geo/pulse-backup/libao.conf': No such file or directory
geo@geo-desktop:~$ cp ~/pulse-backup/.asoundrc* ~/
cp: cannot stat `/home/geo/pulse-backup/.asoundrc*': No such file or directory
geo@geo-desktop:~$
I also did the kill pulseaudio in the terminal as you said, however, there is no sound. The video streams on the internet are back to normal and they play without any choppiness, but no audio.
I know you mentioned ALSA and using that...however, I was told that I needed OSS because I do not have a Sound Blaster Live card. I have a Sound Blaster X-Fi in which ALSA is KNOWN not to work.
In addition, I needed the pulse audio to get my games to work. However, the pulse audio is what caused the problem with streaming audio and that is why I came here and followed your guide.
I am hoping there is a way to fix this problem.
As of now I have installed just about everything I need to get both games and Ubuntu Studio going. And for the most part I got everything to work...except the sound. The sound is proving very much to be a nightmare and I am wondering if I should pull the X-Fi card out and put something in that that is more Linux compliant. BUT, I really would like to avoid that if I have to because as of now the X-Fi card is working beautifully with Windows and I am not yet willing to make the full conversion yet to Ubuntu...especially if I can't get the sound to work.
Is there a major issue with Pulse Audio in that it can't work with streaming audio?
I was very close to having everything working with sound, but now I am back to square one.
psyke83
June 16th, 2008, 07:00 PM
I was very close to having everything working with sound, but now I am back to square one.
I'm sorry to say this, but you're looking in the wrong thread for support. PulseAudio is not a replacement for ALSA or OSS, it works as a layer on top of them. I don't know how to install OSS v4 (which I assume is what you were told was necessary for your sound card) on Ubuntu without messing everything up, so you should look elsewhere.
By the way, you seem to have broken packages. Run:
$ sudo apt-get install -f
If it seems suspicious and wants to uninstall lots of packages, paste the output here before accepting; otherwise let it fix any missing packages.
Edit: here's a guide to install OSS v4, but it's for Ubuntu 6.10: http://4front-tech.com/forum/viewtopic.php?t=1438
I can't assist with OSS v4, so you should use that forum for support. I also don't know if PulseAudio will work correctly with it, so I don't recommend you follow my guide.
jukingeo
June 16th, 2008, 07:19 PM
I'm sorry to say this, but you're looking in the wrong thread for support. PulseAudio is not a replacement for ALSA or OSS, it works as a layer on top of them. I don't know how to install OSS v4 (which I assume is what you were told was necessary for your sound card) on Ubuntu without messing everything up, so you should look elsewhere.
By the way, you seem to have broken packages. Run:
$ sudo apt-get install -f
If it seems suspicious and wants to uninstall lots of packages, paste the output here before accepting; otherwise let it fix any missing packages.
I looked on my system, and indeed OSS was blasted.
The first guide to get Pulse Audio working with my games worked fine. It was the second guide that you posted to correct the problem with the streaming audio (internet, YouTube) is what has caused the problem.
So what happens now?
psyke83
June 16th, 2008, 07:22 PM
I looked on my system, and indeed OSS was blasted.
So what happens now?
I don't know how you configured your system, as Ubuntu does not use OSS by default. I have edited my reply giving a link to the OSS v4 forum guide, so check it out. Just make sure you run the command to fix broken packages!
bowie101
June 16th, 2008, 08:40 PM
From your post it seems that you tested Firefox immediately after applying the changes here. Did you read the warning about PulseAudio changes not taking effect until a reboot or logging out and back in?
If Firefox is crashing immediately upon startup, it would seem that there's something wrong with your system unrelated to PulseAudio. The cause of crashes for some users with the "libflashsupport" package installed (that shouldn't be installed on a user's system by default anymore) only causes Firefox to crash when closing and opening pages with flash content (e.g. when you visit Youtube, it works fine the first time, but when you click on another video link, then it can crash).
So, my advice to you is:
1. Remove the EQ changes (Part D), so we can make sure that's not the problem (besides, you shouldn't be using those settings if your audio quality is already fine). This is the easiest way to do it:
$ sudo dpkg --force-depends -P pulseaudio
$ sudo apt-get install pulseaudio
Log out and back in for changes to take effect.
2. Close *all* applications that play audio, and follow Appendix B, testing just one application at a time. Be sure to test Firefox, Opera and Konqueror separately. Just keep in mind that these applications only show an entry in the PulseAudio Volume Control when they are playing audio!
Let me know the results, and if you get the "A" result, try playing audio from more than one application at once (ensure they all show correctly in the Volume Control window).
Sorry for my rushing. Too much rushing these days. just so much to do, and with these crashes, i've been living with it for about a 3 weeks now. I am confident it is a Pulse audio thing.
Sorry for not being specific enough. I launch it, it asks me to go to a new page or restore my old pages. I pretty much always pick restore old pages, one or more of which will inevidably have flash. Especially Gmail and Google Docs, Google stuff in general. (not the search). If I choose new page, well it will go to my home page which is presently a Google Desktop page which will have flash.
So again, I'm confident it's pulseaudio.
Based on this info, you want me to still try the same steps you outlined for me before?
psyke83
June 16th, 2008, 09:10 PM
Sorry for my rushing. Too much rushing these days. just so much to do, and with these crashes, i've been living with it for about a 3 weeks now. I am confident it is a Pulse audio thing.
Sorry for not being specific enough. I launch it, it asks me to go to a new page or restore my old pages. I pretty much always pick restore old pages, one or more of which will inevidably have flash. Especially Gmail and Google Docs, Google stuff in general. (not the search). If I choose new page, well it will go to my home page which is presently a Google Desktop page which will have flash.
So again, I'm confident it's pulseaudio.
Based on this info, you want me to still try the same steps you outlined for me before?
Follow Part A & B, then (after logging out/in, or rebooting!) try the troubleshooting steps Appendix B and report back.
(By the way, the crashes you're experiencing with Firefox are unusual. It shouldn't crash when restoring tabs with flash content, only when closing them.)
XneoX
June 16th, 2008, 10:09 PM
Hey guys.. was just wondering, if the stuttering fix would also work for the linux kernel 2.6.24-19-generic. I had enabled the Hardy proposed reps too. I hope it would not cause any problem. I usually notice the audio stuttering when i am using firefox and if i start scrolling the page. Seems like a buffering problem..
psyke83
June 16th, 2008, 10:19 PM
Hey guys.. was just wondering, if the stuttering fix would also work for the linux kernel 2.6.24-19-generic. I had enabled the Hardy proposed reps too. I hope it would not cause any problem. I usually notice the audio stuttering when i am using firefox and if i start scrolling the page. Seems like a buffering problem..
The stuttering problem is complicated - I provide links to the relevant bug reports in the guide. There was a scheduler problem with Hardy's default kernel (2.6.24-16-generic) that caused skipping in PulseAudio, and it's been fixed since 2.6.24-17-generic. Unfortunately that's not the only cause of skipping, as PulseAudio's default buffering is to blame. Following Part C will most likely help reduce stuttering even more.
bowie101
June 17th, 2008, 12:01 AM
the apt-get install command in part A that you suggest..., well, I figured why install what I already have installed, right?
So after drinking 2 glasses of wine, I thought why not just purge the files first , right? so I run "sudo apt-get purge" instead of install, and then copy and paste the rest of the command, (actually, copy and paste the whole thing, and then just replace install with purge.)
REALLY bad idea. Sort of like a " cd / " and " sudo rm * -fr "
I watch as everything that I believe is in the proposed repository get eaten up off my computer. my terminal, my everything.
I finally quit it. tried to fix my now broken system.
couldn't do it in 30 min. so I am cutting bait , got all my config files (from the web) onto my pen drive, and will just reinstall from the CD again. Once I'm up and running again, I'll let you know..and I'm switching to ice tea and vanilla ice cream. Why is it always at midnight that these things happen? I hate computers..
jukingeo
June 17th, 2008, 08:06 AM
I don't know how you configured your system, as Ubuntu does not use OSS by default. I have edited my reply giving a link to the OSS v4 forum guide, so check it out. Just make sure you run the command to fix broken packages!
I had to use OSS because the ALSA drivers for the SB X-Fi are very buggy and it is a huge headache to get the card to work with ALSA. OSS does work first shot out. However, I needed to use Pulse Audio to get many of my applications working. But a side effect of doing such rendered my streaming audio inoperable and I couldn't even watch videos on YouTube anymore. Then you came with your fix and after I did that, my video was back to normal, but my sound was blasted out.
As of now I had to uninstall Pulse Audio and OSS, and for some reason, now my machine isn't retaking OSS. So I had to go back to the OSS thread for help.
I would make a BIG fat note in your document that states that it doesn't work with OSS, otherwise those that use OSS will also have their sound knocked out.
bowie101
June 17th, 2008, 11:30 AM
Well you should have seen it. IT wasn't pretty. Couldn't find a good CD to burn the image, and when I did, for some reason my various burning CD software on both a Vista and a W2k machine wouldn't let me burn at a speed any slower than 4x. Which means that I didn't have a qualified disk image on CD that could make it through the install.
So then I found a Breezy Kubuntu CD. Never used it before. But I figured , why not? no other choice right? So I install Breezy Badger , command line only. No windows. Then I upgrade that to Dapper. Then I upgrade that to Edgy. No dice. Edgy repositories not communicating for some reason. So I upgrade right to Feisty. I did it , it worked, but sometime thereafter , there was a kernel panic, and then I paniced, and went to sleep. Then I wake up and notice that I have some old HArdy Heron alternate and regular install disks right next to my bed. The ones I actually used before. Damn!
So I've installed Hardy Heron, command line, and am right now in the middle of installing the gnome-desktop and the ubuntustudio stuff too. I will want XFCE, and yes, not some kubuntu applications, so probably to be safe, the K desktop too (although I won't use it too much, just some K applications).
So as I'm doing that, maybe now is a good time to tell me what to do with my fresh install, so as to avoid the pulseaudio stuff sure to come up. Is there a "best-practice" for a fresh install?
- Severely sleep deprived, but listening to bowie as I type.
eryksun
June 17th, 2008, 11:32 AM
For anyone tweaking their .asoundrc settings (e.g. tweaking the equalizer), you can reload the ALSA system with the following command:
sudo alsa reload
You have to restart currently playing audio for the new settings to take effect (e.g. pause/stop, then play), but it beats having to reload your entire session.
Also, for what it's worth, here's my current EQ config (it depends on original audio quality, speaker fidelity, room acoustics, and your own ears/brain):
# Frequency Bands (kHz)
# 0.050, 0.100, 0.156, 0.220, 0.311, 0.440, 0.622, 0.880,
# 1.250, 1.750, 2.500, 3.500, 5.000, 10.00, 20.00
# controls [0 0 0 0 0 0 0 0 0 0 0 0 0 0 0]
#
controls [0 -2 -4 -6 -6 -6 -6 -9 -9 -6 -6 -6 -6 -6 -6]
I keep all the values non-positive to avoid clipping distortion. If your system is too quiet you might trade off some distortion for loudness -- just add a constant positive bias across the spectrum. I think as much as +30 is possible, though not recommended. Probably +5 would be enough.
psyke83
June 17th, 2008, 11:39 AM
- Severely sleep deprived, but listening to bowie as I type.
My suggestion is that you get some sleep ;). With all the rigmarole you're going through to install Hardy, I don't have a lot of faith your system will be working completely. I don't recommended you follow my guide unless you install from a working installation, simply because I don't want to be working around bugs in your system that have nothing to do with PulseAudio or my instructions. Also, keep in mind the warning that this is not a guide to fix a system with *no* audio, it's to fix audio mixing between some applications due to a PulseAudio misconfiguration.
Also, please don't go substituting commands in my guide with what you think is correct. Using "purge" is not the same as "install", it's the opposite! How did you expect that to have the right effect? I can't see every command you type into your shell, so I can't know what vital packages you may uninstall from using such dangerous commands.
What I suggest you do is a) get some sleep ;) and b) wait until you can get a proper Hardy CD image, so you can perform a clean install. Also note that CD images can be burned onto DVDs if you use good burning software (if you're using Windows, Nero won't allow it, but you can find alternatives).
psyke83
June 17th, 2008, 11:40 AM
For anyone tweaking their .asoundrc settings (e.g. tweaking the equalizer), you can reload the ALSA system with the following command:
sudo alsa reload
You have to restart currently playing audio for the new settings to take effect (e.g. pause/stop, then play), but it beats having to reload your entire session.
Also, for what it's worth, here's my current EQ config (it depends on original audio quality, speaker fidelity, room acoustics, and your own ears/brain):
# Frequency Bands (kHz)
# 0.050, 0.100, 0.156, 0.220, 0.311, 0.440, 0.622, 0.880,
# 1.250, 1.750, 2.500, 3.500, 5.000, 10.00, 20.00
# controls [0 0 0 0 0 0 0 0 0 0 0 0 0 0 0]
#
controls [0 -2 -4 -6 -6 -6 -6 -9 -9 -6 -6 -6 -6 -6 -6]
I keep all the values non-positive to avoid clipping distortion. If your system is too quiet you might trade off some distortion for loudness -- just add a constant positive bias across the spectrum. I think as much as +30 is possible, though not recommended. Probably +5 would be enough.
Thanks for the info! Also "/etc/init.d/alsa-utils restart" and/or restarting the pulseaudio process will have a similar effect. Can I ask what is your hardware/speaker setup?
bowie101
June 17th, 2008, 11:48 AM
we are suffering from slight miscommunication problems. I got enough sleep (few hours), shower, sleep deprived, but i don't feel it, and I got a good disk, so here I now go.. (really my mind is fresh)(I promise!)
The purge was intentional. you asked me originally to do step A and B etc. But since I already did, repeating those steps again was going to have absolutely no effect. So the thought was to purge and then install again. Except the purge, purged a little too much!
psyke83
June 17th, 2008, 11:57 AM
we are suffering from slight miscommunication problems. I got enough sleep (few hours), shower, sleep deprived, but i don't feel it, and I got a good disk, so here I now go.. (really my mind is fresh)(I promise!)
The purge was intentional. you asked me originally to do step A and B etc. But since I already did, repeating those steps again was going to have absolutely no effect. So the thought was to purge and then install again. Except the purge, purged a little too much!
You need to understand the risks involved when purging a package. It will also remove associated packages that list it as a dependency - very, very bad. I gave you instructions several times and you didn't reply to my requests. I asked you to follow configuration steps and report the troubleshooting results of Appendix B. I then asked you to test applications while pulseaudio is not running. You didn't try that either.
When you have Hardy installed (properly), I suggest you go back and read my previous posts completely, and don't "interpret" any of the instructions... you've already seen what the difference between "purge" and "install" can do to a system.
bowie101
June 17th, 2008, 12:14 PM
i don't move on to steps 2 or 3 or any Appendix in your guide until I get past 1. Which I did not. I assumed they were numbered/lettered for a reason. 1 step follows the other, not independent of one another.
But alas, I deserve the tongue lashing. That's fine. Will try again.
BTW, another thing not to do is to try a distribution upgrade command from the command line when you have installed the latest release (in this case, Hardy) Oy Vey!
eryksun
June 17th, 2008, 12:17 PM
Thanks for the info! Also "/etc/init.d/alsa-utils restart" and/or restarting the pulseaudio process will have a similar effect. Can I ask what is your hardware/speaker setup?
I have a pair of cheap Acer desktop speakers. Their high-frequency response is pretty good, but the lower end of the spectrum needs a boost. Plus I always have to dampen the mid-range around 1 kHz to keep music from sounding muddled -- just a personal preference that probably stems from mild hearing damage (I grew up working in the family carpet cleaning business around 100+ dB vacuums).
psyke83
June 17th, 2008, 12:20 PM
I have a pair of cheap Acer desktop speakers. Their high-frequency response is pretty good, but the lower end of the spectrum needs a boost. Plus I always have to dampen the mid-range around 1 kHz to keep music from sounding muddled -- just a personal preference that probably stems from mild hearing damage (I grew up working in the family carpet cleaning business around 100+ dB vacuums).
Thanks. Unfortunately your presets don't translate well for my poor laptop speakers, but they may be useful to others! The range of 500Hz or so seems to give the most trouble here.
psyke83
June 17th, 2008, 12:33 PM
i don't move on to steps 2 or 3 or any Appendix in your guide until I get past 1. Which I did not. I assumed they were numbered/lettered for a reason. 1 step follows the other, not independent of one another.
But alas, I deserve the tongue lashing. That's fine. Will try again.
BTW, another thing not to do is to try a distribution upgrade command from the command line when you have installed the latest release (in this case, Hardy) Oy Vey!
Here's my final, definitive instructions for you :).
1. Reinstall Hardy from scratch (find a way to burn the CD, don't dist-upgrade if you can avoid it).
2. Do not do any steps of this guide yet!
3. Do the troubleshooting of Appendix B, testing the following applications separately: Totem, and Firefox when playing a video with sound on Youtube.
4. You will notice that Totem works, but Firefox does not.
5. Follow Part A & B (not C or D!), then log out and back in.
6. Follow the troubleshooting of Appendix B again, using Totem and Flash again.
7. Flash should work with PulseAudio (and as a side-effect, many other applications will work also).
That's all I can advise for now - except that you shouldn't modify any commands I've written in the guide.
bowie101
June 17th, 2008, 01:09 PM
muchas gracias
eryksun
June 17th, 2008, 01:13 PM
Thanks. Unfortunately your presets don't translate well for my poor laptop speakers, but they may be useful to others! The range of 500Hz or so seems to give the most trouble here.
Is this your current config?
controls [ -5 -5 -5 -5 -5 -10 -20 -15 -10 -10 -10 -10 -10 -3 -2 ]
This is heavily damping 400-1200 Hz, with a minimum around 600 Hz. It's surprising that laptop speakers wouldn't have a reasonably flat response curve between 150 and 15 kHz. I'd expect some roll-off at the extremes. But it looks like your speaker coils have an extremely sharp physical resonance at around 600 Hz. Thank heavens for equalizers. :)
IMO, you could make your system a little louder, without risking digital distortion, if you added +2 across the spectrum:
controls [ -3 -3 -3 -3 -3 -8 -18 -13 -8 -8 -8 -8 -8 -1 0 ]
psyke83
June 17th, 2008, 11:24 PM
This is heavily damping 400-1200 Hz, with a minimum around 600 Hz. It's surprising that laptop speakers wouldn't have a reasonably flat response curve between 150 and 15 kHz. I'd expect some roll-off at the extremes. But it looks like your speaker coils have an extremely sharp physical resonance at around 600 Hz. Thank heavens for equalizers. :)
IMO, you could make your system a little louder, without risking digital distortion, if you added +2 across the spectrum:
controls [ -3 -3 -3 -3 -3 -8 -18 -13 -8 -8 -8 -8 -8 -1 0 ]
Oddly enough, I'm using the settings that someone else posted on the Archlinux wiki (http://wiki.archlinux.org/index.php/ALSA#System-Wide_Equalizer), unmodified, as I found them to work best for my laptop. I had already realized that the main source of distortion came from the range of about 500-600Hz (using VLC's equalizer and Audacious with the caps/C* Eq LADSPA plugin, testing in realtime).
You can see my efforts from last year here (http://ubuntuforums.org/showthread.php?t=476146), although the current settings are better. I suppose some further tweaking would make things better, but I'm pretty happy with the results at the moment.
I've applied your settings (although it's too late to test right now, heh). Thanks!
eryksun
June 18th, 2008, 03:07 AM
A bug in my system is causing the audio to cut out when the total mixer volume between the application setting and the master volume is less than 100%. For example, if Rhythmbox is set to 60% volume, the audio will cut out if I decrease the master volume below 40%. Is this a PulseAudio bug that others have experienced, or is it something to do with my particular driver (Intel HDA for an ALC662 chip)?
eryksun
June 18th, 2008, 05:06 AM
I found an easy way to get more than 100% master or per application volume. The PulseAudio manager lets you adjust the volume of all the audio sinks on the 'Devices' tab. The percentages reported there are for the normalized peak audio level, so 50% is 20*Log10(0.5) = -6.02dB. Open up the PulseAudio Volume Control at the same time and adjust to a perceived increase in volume. For example, 141% is a 3dB boost, corresponding to 110% volume.
Bear in mind that going over 100% will distort the sound. On my system the volume meter peaks at a setting of exactly 100% volume level, and if I go even 1% higher I get lots of crackling noise. But I've read some people saying they can't get anywhere near maxing out the volume meter level, which to me seems like a problem with their source audio. If the 16-bit value is normalized to the full [-32768, 32767] range, the meter should be peaking, but I digress.
billybag
June 18th, 2008, 02:18 PM
Does anyone have any info or a fix for this volume problem i am having. I am using Linux Mint 5 with Gnome and my max volume is very low.
I have to have the volume level in Pidgin's preferences on LOUDEST and i still can barely hear that.
When i play music i have to hook it up to my stereo to be able to hear it at a relatively pleasing volume and even that isnt loud enough and my stereo is maxed out as well.
Is anyone, at least, having this problem as well?
psyke83
June 18th, 2008, 02:25 PM
Does anyone have any info or a fix for this volume problem i am having. I am using Linux Mint 5 with Gnome and my max volume is very low.
I have to have the volume level in Pidgin's preferences on LOUDEST and i still can barely hear that.
When i play music i have to hook it up to my stereo to be able to hear it at a relatively pleasing volume and even that isnt loud enough and my stereo is maxed out as well.
Is anyone, at least, having this problem as well?
1. Open Pidgin, play a sound
2. Close Pidgin
3. Kill PulseAudio: $ pkill pulseaudio
4. Open Pidgin, play a sound
If there is no difference between step 1 and 4, then it has nothing to do with PulseAudio.
billybag
June 18th, 2008, 02:31 PM
Yeah their was. It was actually louder. Not as luud as it used to be with gutsym but deffinitely noticebly louder
YaroMan86
June 18th, 2008, 02:44 PM
In section D, I typed in the following:
analyseplugin /usr/lib/ladspa/mbeq_1197.so
And got the following result:
Failed to load plugin "/usr/lib/ladspa/mbeq_1197.so": /usr/lib/ladspa/mbeq_1197.so: cannot open shared object file: No such file or directory
I'm assuming I'm either missing a package or I need to compile something. What shall I do?
psyke83
June 18th, 2008, 02:44 PM
Yeah their was. It was actually louder. Not as luud as it used to be with gutsym but deffinitely noticebly louder
I have two suggestions:
1. Go to the PulseAudio Volume Control (run the PulseAudio Device Chooser applet, then click the icon), and make sure all the Output Devices are set to 100% volume. The playback volume for Pidgin should also be at 100%, but it's hard to check unless you're quick (as the entry only appears in the Playback tab while Pidgin is actually playing sound, and Pidgin's samples are very short).
2. If you followed Part D (the equalizer), that will have caused sounds to become quieter. You can undo this step by editing /etc/pulse/default.pa and commenting the line you changed in the guide, i.e.:
change this:
load-module module-alsa-sink device=equalized
to this:
#load-module module-alsa-sink device=equalized
That will disable the equalizer and as a result increase the volume somewhat. Changed take effect after logging out and back in.
psyke83
June 18th, 2008, 02:49 PM
In section D, I typed in the following:
analyseplugin /usr/lib/ladspa/mbeq_1197.so
And got the following result:
Failed to load plugin "/usr/lib/ladspa/mbeq_1197.so": /usr/lib/ladspa/mbeq_1197.so: cannot open shared object file: No such file or directory
I'm assuming I'm either missing a package or I need to compile something. What shall I do?
You need the packages "swh-plugins" and "ladspa-sdk" (they get installed in Part A of this guide, which you're supposed to follow).
Are you using the 64bit version of Ubuntu? If so, the LADSPA plugins may be stored in a different location. You can check by running either "locate mbeq_1197.so" or "dpkg -S mbeq_1197.so" (but you need to have the package "swh-plugins" installed first).
billybag
June 18th, 2008, 02:52 PM
Thanks. Step 2 worked. I remember the last ubuntu still being a lot louder though. But im not going to complain, i at least got pulseaudio to be louder than it was. thanks again
psyke83
June 18th, 2008, 02:54 PM
A bug in my system is causing the audio to cut out when the total mixer volume between the application setting and the master volume is less than 100%. For example, if Rhythmbox is set to 60% volume, the audio will cut out if I decrease the master volume below 40%. Is this a PulseAudio bug that others have experienced, or is it something to do with my particular driver (Intel HDA for an ALC662 chip)?
Did you find a solution to this problem? I don't have this issue here, so the best thing I can suggest is for you to kill the PulseAudio server and see if this bug occurs - then you'll know if it's a PulseAudio or ALSA bug.
ShirishAg75
June 18th, 2008, 04:17 PM
Hi pyske83,
Love the work you are doing. There are few issues which need some sorting out. I'm on Intrepid and used your guide and it works sort of. Apologies for the long post below :-
shirish@Mugglewille:~/Documents$ mplayer Cute_Zee_Aunty_First_nite.rmvb
MPlayer 1.0rc2-4.2.3 (C) 2000-2007 MPlayer Team
CPU: Intel(R) Pentium(R) 4 CPU 1.80GHz (Family: 15, Model: 1, Stepping: 2)
CPUflags: MMX: 1 MMX2: 1 3DNow: 0 3DNow2: 0 SSE: 1 SSE2: 1
Compiled with runtime CPU detection.
mplayer: could not connect to socket
mplayer: No such file or directory
Failed to open LIRC support. You will not be able to use your remote control.
Playing Cute_Zee_Aunty_First_nite.rmvb.
REAL file format detected.
Stream description: Video Stream
Stream mimetype: video/x-pn-realvideo
[real] Video stream found, -vid 0
Stream description: Audio Stream
Stream mimetype: audio/x-pn-realaudio
[real] Audio stream found, -aid 1
Stream mimetype: logical-fileinfo
VIDEO: [RV40] 352x288 24bpp 25.000 fps 0.0 kbps ( 0.0 kbyte/s)
Clip info:
author: Easy Real Converter
copyright: http://www.magicutils.com
comment:
xscreensaver_disable: Could not find XScreenSaver window.
GNOME screensaver disabled
================================================== ========================
Opening video decoder: [realvid] RealVideo decoder
Selected video codec: [rv3040] vfm: realvid (Linux RealPlayer 10 RV30/40 decoder)
================================================== ========================
================================================== ========================
Forced audio codec: mad
Opening audio decoder: [ffmpeg] FFmpeg/libavcodec audio decoders
AUDIO: 44100 Hz, 2 ch, s16le, 96.5 kbit/6.84% (ratio: 12058->176400)
Selected audio codec: [ffcook] afm: ffmpeg (FFmpeg COOK audio decoder)
================================================== ========================
AO: [pulse] Failed to connect to server: Connection refused
*** PULSEAUDIO: Unable to connect: Connection refused
[AO_ALSA] Playback open error: Connection refused
AO: [oss] 44100Hz 2ch s16le (2 bytes per sample)
Starting playback...
VDec: vo config request - 352 x 288 (preferred colorspace: Planar I420)
VDec: using Planar I420 as output csp (no 0)
Movie-Aspect is 1.22:1 - prescaling to correct movie aspect.
VO: [xv] 352x288 => 352x288 Planar I420
GNOME screensaver enabled.001 ct: -0.029 62/ 62 43% 10% 1.3% 5 0
Exiting... (Quit)
Now another one
shirish@Mugglewille:~$ exaile
location: /usr/lib/xulrunner-1.9/libxpcom.so
before 3
Exaile 0.2.14devel
Plugins 'Tray Buttons' version '0.7.3' loaded successfully
Failed to load plugin
Traceback (most recent call last):
File "/usr/local/lib/exaile/xl/plugins/manager.py", line 71, in initialize_plugin
plugin = __import__(re.sub('\.py[co]?$', '', file))
File "/home/shirish/.exaile/plugins/updates.py", line 2, in <module>
import gtk, plugins, gobject, time, urllib
ImportError: No module named plugins
Plugins 'Shoutcast Radio' version '0.4.7' loaded successfully
Plugins 'Mini Mode' version '0.4.9' loaded successfully
Plugins 'Python Console' version '0.1.2' loaded successfully
Created db for thread Thread-1
{'Thread-1': <sqlite3.Connection object at 0x8bcbea8>}
Closed db for thread Thread-1
Activated gnome mmkeys for gnome 2.22.x
Using multimedia keys from: gnome
loading tracks...
Starting scan timer at 25.0
done loading tracks...
loading songs
Clearing tracks cache
Importing /home/shirish/.exaile/saved/playlist0000.m3u
Last playlist loaded
Loading page 0
*** PULSEAUDIO: Unable to connect: Connection refused
Traceback (most recent call last):
File "/usr/local/lib/exaile/xl/gui/main.py", line 1241, in as_play_track
int(track.duration), track.track)
File "/usr/local/lib/exaile/lib/scrobbler.py", line 149, in now_playing
raise AuthError("Please 'login()' first. (No session available)")
lib.scrobbler.AuthError: Please 'login()' first. (No session available)
/usr/local/lib/exaile/xl/gui/playlist.py:354: GtkWarning: gtk_tree_path_append_index: assertion `index >= 0' failed
iter = self.model.get_iter(path)
/usr/local/lib/exaile/xl/gui/playlist.py:354: GtkWarning: gtk_tree_model_get_iter: assertion `path->depth > 0' failed
iter = self.model.get_iter(path)
ReplayGain support initialized.
Not using Equalizer disabled by the user
Adding an application
shirish@Mugglewille:~$ sudo aptitude install wammu
[sudo] password for shirish:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
The following NEW packages will be installed:
freepats{a} libgammu-common{a} libgammu3{a} python-bluez{a} python-gammu{a} timidity{a} wammu
0 packages upgraded, 7 newly installed, 0 to remove and 5 not upgraded.
Need to get 30.8MB of archives. After unpacking 39.9MB will be used.
Do you want to continue? [Y/n/?] Y
Writing extended state information... Done
Get:1 http://in.archive.ubuntu.com intrepid/universe freepats 20060219-1 [29.0MB]
Get:2 http://in.archive.ubuntu.com intrepid/universe libgammu-common 1.20.0-1 [145kB]
Get:3 http://in.archive.ubuntu.com intrepid/universe libgammu3 1.20.0-1 [448kB]
Get:4 http://in.archive.ubuntu.com intrepid/main python-bluez 0.14-1ubuntu1 [84.3kB]
Get:5 http://in.archive.ubuntu.com intrepid/universe python-gammu 0.26-1 [146kB]
Get:6 http://in.archive.ubuntu.com intrepid/universe timidity 2.13.2-19ubuntu1 [545kB]
Get:7 http://in.archive.ubuntu.com intrepid/universe wammu 0.27-1 [434kB]
Fetched 30.8MB in 26min34s (19.3kB/s)
Selecting previously deselected package freepats.
(Reading database ... 317841 files and directories currently installed.)
Unpacking freepats (from .../freepats_20060219-1_all.deb) ...
Selecting previously deselected package libgammu-common.
Unpacking libgammu-common (from .../libgammu-common_1.20.0-1_all.deb) ...
Selecting previously deselected package libgammu3.
Unpacking libgammu3 (from .../libgammu3_1.20.0-1_i386.deb) ...
Selecting previously deselected package python-bluez.
Unpacking python-bluez (from .../python-bluez_0.14-1ubuntu1_i386.deb) ...
Selecting previously deselected package python-gammu.
Unpacking python-gammu (from .../python-gammu_0.26-1_i386.deb) ...
Selecting previously deselected package timidity.
Unpacking timidity (from .../timidity_2.13.2-19ubuntu1_i386.deb) ...
Selecting previously deselected package wammu.
Unpacking wammu (from .../archives/wammu_0.27-1_all.deb) ...
Processing triggers for man-db ...
Setting up freepats (20060219-1) ...
Setting up libgammu-common (1.20.0-1) ...
Setting up libgammu3 (1.20.0-1) ...
Setting up python-bluez (0.14-1ubuntu1) ...
Setting up python-gammu (0.26-1) ...
Setting up timidity (2.13.2-19ubuntu1) ...
* Starting TiMidity++ ALSA midi emulation... *** PULSEAUDIO: Unable to connect: Connection refused
[fail]
invoke-rc.d: initscript timidity, action "start" failed.
dpkg: error processing timidity (--configure):
subprocess post-installation script returned error exit status 1
Setting up wammu (0.27-1) ...
Processing triggers for libc6 ...
ldconfig deferred processing now taking place
Errors were encountered while processing:
timidity
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:
Setting up timidity (2.13.2-19ubuntu1) ...
* Starting TiMidity++ ALSA midi emulation... *** PULSEAUDIO: Unable to connect: Connection refused
[fail]
invoke-rc.d: initscript timidity, action "start" failed.
dpkg: error processing timidity (--configure):
subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
timidity
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
Writing extended state information... Done
I know it simply could be that we are in the pre-alpha stage thats the reason I'm getting this bug or maybe because I'm using the 2.6.26-1 kernel or something else unrelated as well.
As far as mplayer and exaile they both work. Exaile gives a little delay but works.
Timidity is still an issue though
Some things more :-
shirish@Mugglewille:~$ padevchooser
** (padevchooser:17220): WARNING **: pa_browser_new() failed.
I have filed a bug for the same at launchpad.
Just in case you want to know here's my lspci output :-
shirish@Mugglewille:~$ lspci | grep audio
00:1f.5 Multimedia audio controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 02)
The same one as yours, hence used the same values for fragments and things.
Any tips or ideas or anything which you could share would be nice to know.
psyke83
June 18th, 2008, 04:41 PM
Any tips or ideas or anything which you could share would be nice to know.
Some notes for Intrepid:
1. In Part A, this is the list of packages to install:$ sudo apt-get install libasound2/hardy-proposed libasound2-plugins/hardy-proposed libasound2-dev/hardy-proposed padevchooser swh-plugins libao-pulse libsdl1.2debian-pulseaudio ladspa-sdk
That won't work for Intrepid because it's explicitly asking for packages in the "hardy-proposed" repository. Use this instead: $ sudo apt-get install libasound2 libasound2-plugins libasound2-dev padevchooser swh-plugins libao-pulse libsdl1.2debian-pulseaudio ladspa-sdk
2. For Part B, it's not necessary to manually install the "flashplugin-nonfree" package (it's from the Intrepid repository anyway), but it *is* required to remove the "libflashsupport" package.
Now getting back to your specific problem - it seems the pulseaudio server isn't running on your system.
Try booting with the old 2.6.24 kernel and see if sound works. If it still doesn't work, kill the PulseAudio server and relaunch it with verbose output:
$ pkill pulseaudio
$ pulseaudio -vv
Please paste its output here.
kalyanakrishna
June 18th, 2008, 05:53 PM
Awesome!! You are a life saver, to many, I am sure. I came here looking for skype help. I had given up on configuring the Pulse Audio to work fine. I am surprised it was not configured to work properly during the upgrade. You have my heartfelt thanks.
YaroMan86
June 18th, 2008, 06:14 PM
Okay, one last question... how do I invoke the equalizer? I see no manu option for it. (There's the device chooser, but that's not what I want."
eryksun
June 18th, 2008, 06:29 PM
Did you find a solution to this problem? I don't have this issue here, so the best thing I can suggest is for you to kill the PulseAudio server and see if this bug occurs - then you'll know if it's a PulseAudio or ALSA bug.
No I didn't find a solution. I'll search around for more info tomorrow. Killing PulseAudio wouldn't narrow anything down. The volume cuts out if the master volume (pavucontrol -> Output Devices) and the per application volume (pavucontrol -> Playback) sum to less than 100%. The volume control within programs is not affected. The ALSA master volume is also unaffected, but that's not what I want since the volume applet in AWN uses the PulseAudio master, not ALSA.
psyke83
June 18th, 2008, 06:47 PM
Okay, one last question... how do I invoke the equalizer? I see no manu option for it. (There's the device chooser, but that's not what I want."
There's no way to change it via a GUI. The equalizer will be active if you followed Part D (editing /etc/pulse/default.pa).
This post explains how to disable the equalizer: http://ubuntuforums.org/showpost.php?p=5213207&postcount=230
If you're not sure it's working (and you've logged out and back in), try this:
1. mplayer song.mp3 -ao pulse
2. mplayer song.mp3 -ao oss
The first will have equalized sound, and the second won't (as it bypasses the PulseAudio server). It works only if no other applications are playing audio, however.
YaroMan86
June 18th, 2008, 10:13 PM
There's no way to change it via a GUI. The equalizer will be active if you followed Part D (editing /etc/pulse/default.pa).
This post explains how to disable the equalizer: http://ubuntuforums.org/showpost.php?p=5213207&postcount=230
If you're not sure it's working (and you've logged out and back in), try this:
1. mplayer song.mp3 -ao pulse
2. mplayer song.mp3 -ao oss
The first will have equalized sound, and the second won't (as it bypasses the PulseAudio server). It works only if no other applications are playing audio, however.
I noticed a difference, I was just hoping for a way to adjust it easily. I'm not on a laptop, I'm on a desktop with cheap speakers that are receiving pollution from the rest of the system's signals. It sounds fine now, but I'd love to tweak this if need be. Do I have to adjust those numerical values in that .pa configuration file?
ShirishAg75
June 18th, 2008, 10:25 PM
Some notes for Intrepid:
1. In Part A, this is the list of packages to install:$ sudo apt-get install libasound2/hardy-proposed libasound2-plugins/hardy-proposed libasound2-dev/hardy-proposed padevchooser swh-plugins libao-pulse libsdl1.2debian-pulseaudio ladspa-sdkThat won't work for Intrepid because it's explicitly asking for packages in the "hardy-proposed" repository. Use this instead: $ sudo apt-get install libasound2 libasound2-plugins libasound2-dev padevchooser swh-plugins libao-pulse libsdl1.2debian-pulseaudio ladspa-sdk2. For Part B, it's not necessary to manually install the "flashplugin-nonfree" package (it's from the Intrepid repository anyway), but it *is* required to remove the "libflashsupport" package.
Hi Pyske83 thanx for getting back to me. I actually did this in Intrepid
$ sudo apt-get install libasound2 libasound2-plugins libasound2-dev padevchooser swh-plugins libao-pulse libsdl1.2debian-pulseaudio ladspa-sdk
Now getting back to your specific problem - it seems the pulseaudio server isn't running on your system.
Try booting with the old 2.6.24 kernel and see if sound works. If it still doesn't work, kill the PulseAudio server and relaunch it with verbose output:
$ pkill pulseaudio
$ pulseaudio -vv
Please paste its output here.
I am able to hear the drums whenever I'm logging in so somehow the sound system works. I ran your commands and this is the output on kernel 2.6.26-1
shirish@Mugglewille:~$ pulseaudio -vv
I: main.c: We're in the group 'pulse-rt', allowing real-time and high-priority scheduling.
I: core-util.c: Successfully gained nice level -11.
W: main.c: setrlimit(RLIMIT_NICE, (31, 31)) failed: Operation not permitted
W: main.c: setrlimit(RLIMIT_RTPRIO, (9, 9)) failed: Operation not permitted
I: main.c: This is PulseAudio 0.9.10
I: main.c: Page size is 4096 bytes
I: main.c: Fresh high-resolution timers available! Bon appetit!
E: module.c: Failed to open module "module-alsa-sink=equalized": module-alsa-sink=equalized.so: cannot open shared object file: No such file or directory
E: main.c: Module load failed.
E: main.c: Failed to initialize daemon.
I: main.c: Daemon terminated.
Some additional notes :- I didn't do Part B because I don't want nonflashplugin-free . I am looking and waiting for swfdec or gnash whenever they're ready and I'm ready to wait for them as well as your notes how to work with either of them.
Looking forward to your comments on the same.
psyke83
June 18th, 2008, 10:30 PM
I noticed a difference, I was just hoping for a way to adjust it easily. I'm not on a laptop, I'm on a desktop with cheap speakers that are receiving pollution from the rest of the system's signals. It sounds fine now, but I'd love to tweak this if need be. Do I have to adjust those numerical values in that .pa configuration file?
No, not in "default.pa". You need to edit the "controls" values in your .asoundrc. I explain this in the guide, Part D.
YaroMan86
June 18th, 2008, 10:34 PM
My bad. I wasn't sure which one.
ShirishAg75
June 18th, 2008, 10:39 PM
/me bangs his head against the desk.
I was able to fix the pulseaudio error it was showing but ran into a segfault
shirish@Mugglewille:~$ pulseaudio -vv
I: main.c: We're in the group 'pulse-rt', allowing real-time and high-priority scheduling.
I: core-util.c: Successfully gained nice level -11.
W: main.c: setrlimit(RLIMIT_NICE, (31, 31)) failed: Operation not permitted
W: main.c: setrlimit(RLIMIT_RTPRIO, (9, 9)) failed: Operation not permitted
I: main.c: This is PulseAudio 0.9.10
I: main.c: Page size is 4096 bytes
I: main.c: Fresh high-resolution timers available! Bon appetit!
I: module-alsa-sink.c: Successfully opened device equalized.
I: module-alsa-sink.c: Successfully enabled mmap() mode.
ALSA lib control.c:909:(snd_ctl_open_noupdate) Invalid CTL equalized
I: alsa-util.c: Unable to attach to mixer equalized: No such file or directory
I: alsa-util.c: Unable to attach to mixer hw:(null): No such device
I: sink.c: Created sink 0 "alsa_output.equalized" with sample spec "s16le 2ch 44100Hz"
I: source.c: Created source 0 "alsa_output.equalized.monitor" with sample spec "s16le 2ch 44100Hz"
I: module-alsa-sink.c: Using 8 fragments of size 880 bytes.
D: module-alsa-sink.c: Thread starting up
D: rtpoll.c: Acquired POSIX realtime signal SIGRTMIN+29
I: module-alsa-sink.c: Starting playback.
I: module.c: Loaded "module-alsa-sink" (index: #0; argument: "device=equalized").
D: cli-command.c: Checking for existance of '/usr/lib/pulse-0.9/modules/module-hal-detect.so': success
I: module-hal-detect.c: Trying capability alsa
D: module-hal-detect.c: Not loaded device /org/freedesktop/Hal/devices/computer_alsa_timer
D: module-hal-detect.c: Not loaded device /org/freedesktop/Hal/devices/computer_alsa_sequencer
D: module-hal-detect.c: Loading module-alsa-source with arguments 'device_id=2 source_name=alsa_input.pci_1131_7130_alsa_capture_ 0'
D: alsa-util.c: Trying front:2...
Segmentation fault
The issue was I didn't write correct the stuff at /etc/pulse/default.pa
The line instead of
load-module module-alsa-sink device=equalized
was
load-module module-alsa-sink=equalized
The segfault is worrying though.
psyke83
June 18th, 2008, 10:39 PM
I am able to hear the drums whenever I'm logging in so somehow the sound system works. I ran your commands and this is the output on kernel 2.6.26-1
shirish@Mugglewille:~$ pulseaudio -vv
I: main.c: We're in the group 'pulse-rt', allowing real-time and high-priority scheduling.
I: core-util.c: Successfully gained nice level -11.
W: main.c: setrlimit(RLIMIT_NICE, (31, 31)) failed: Operation not permitted
W: main.c: setrlimit(RLIMIT_RTPRIO, (9, 9)) failed: Operation not permitted
I: main.c: This is PulseAudio 0.9.10
I: main.c: Page size is 4096 bytes
I: main.c: Fresh high-resolution timers available! Bon appetit!
E: module.c: Failed to open module "module-alsa-sink=equalized": module-alsa-sink=equalized.so: cannot open shared object file: No such file or directory
E: main.c: Module load failed.
E: main.c: Failed to initialize daemon.
I: main.c: Daemon terminated.
You made a typo in Part D. It seems you changed the line in /etc/pulse/default.pa to:load-module module-alsa-sink=equalized
When it should be:
load-module module-alsa-sink device=equalized
Edit: I just saw your reply ;). You figured it out.
psyke83
June 18th, 2008, 10:42 PM
The segfault is worrying though.
Try disabling the equalizer and checking the verbose output. See this post for how to disable it: http://ubuntuforums.org/showpost.php?p=5213207&postcount=230
eryksun
June 19th, 2008, 07:38 AM
If your per application settings get messed up and it's hard to modify in pavucontrol (e.g. Pidgin has short audio samples), one way to solve the problem is to either edit or delete the following file:
~/.pulse/volume-restore.table
If you delete the file, all your application volume settings will be reset at the next login. If you edit it, just search for the program name and adjust the value. It's a 16-bit unsigned number [1, 65536].
ShirishAg75
June 19th, 2008, 02:37 PM
Try disabling the equalizer and checking the verbose output. See this post for how to disable it: http://ubuntuforums.org/showpost.php?p=5213207&postcount=230
When I disabled the equalizer I got no sound . This is on 2.6.26-1-generic kernel. Didn't try the 2.6.24-17 kernel. Didn't even the drum sound and none of the players played any of the songs.
With the equalizer while it does take some time or pauses a bit between 2 songs it works.
Dunno if any more info. is required or any tests need to be done. Lemme know if you need anything else done as well.
psyke83
June 19th, 2008, 04:05 PM
When I disabled the equalizer I got no sound . This is on 2.6.26-1-generic kernel. Didn't try the 2.6.24-17 kernel. Didn't even the drum sound and none of the players played any of the songs.
With the equalizer while it does take some time or pauses a bit between 2 songs it works.
Dunno if any more info. is required or any tests need to be done. Lemme know if you need anything else done as well.
The drum sound (in GDM) does not play through PulseAudio - so you have a kernel/ALSA problem. Boot to the Hardy kernel like I suggested (and you should always keep previous kernels until you verify the new one works completely).
ShirishAg75
June 19th, 2008, 11:06 PM
psyke83,
Thank you for your responses. Would be waiting for fixes in the 2.6.26 -tree. I do have the previous kernels installed :)
vBulletin® v3.8.1, Copyright ©2000-2009, Jelsoft Enterprises Ltd.