So I’m not sure what it was in the end, but the solution was to manually upgrade alsa to 1.24(at the time of this writing).   I used the instructions found here to do the install: http://monespaceperso.org/blog-en/2010/05/02/upgrade-alsa-1-0-23-on-ubuntu-lucid-lynx-10-04/

But for convenience sake I’ll post the instructions below:

Installation :

To do this, we must begin by determining our version of alsa as follows :

cat /proc/asound/version
Advanced Linux Sound Architecture Driver Version 1.0.21.

To avoid problems during the upgrade of Alsa-utils, we need to stop it with the following command :

sudo /sbin/alsa-utils stop

We must then install the necessary tools to compile along with the kernel headers :

sudo apt-get -y install build-essential ncurses-dev gettext xmlto libasound2-dev
sudo apt-get -y install linux-headers-`uname -r` libncursesw5-dev

Then, we go in our personal folder and download alsa-driver, alsa-lib and alsa-utils :

cd ~
rm -rf ~/alsa* ~/.pulse*
wget ftp://ftp.alsa-project.org/pub/driver/alsa-driver-1.0.24.tar.bz2
wget ftp://ftp.alsa-project.org/pub/lib/alsa-lib-1.0.24.1.tar.bz2
wget ftp://ftp.alsa-project.org/pub/utils/alsa-utils-1.0.24.2.tar.bz2

After that, we create a new folder for the compilation and installation of the 3 files. Then, we move the 3 tar files that we just downloaded in this folder :

sudo rm -rf /usr/src/alsa
sudo mkdir -p /usr/src/alsa
cd /usr/src/alsa
sudo cp ~/alsa* .

Unpack the 3 tar files :

sudo tar xjf alsa-driver*
sudo tar xjf alsa-lib*
sudo tar xjf alsa-utils*

We compile and install alsa-driver :

cd alsa-driver*
sudo ./configure
sudo make
sudo make install

We compile and install alsa-lib :

cd ../alsa-lib*
sudo ./configure
sudo make
sudo make install

We compile and install alsa-utils :

cd ../alsa-utils*
sudo ./configure
sudo make
sudo make install

Then, we remove the 3 tar files in our personal folder that are not anymore necessary :

rm -f ~/alsa-driver*
rm -f ~/alsa-lib*
rm -f ~/alsa-utils*

Then, just restart your computer and your alsa version should be 1.0.23!

You can verify that you have now indeed have this version of alsa :

cat /proc/asound/version
Advanced Linux Sound Architecture Driver Version 1.0.24.
Compiled on May 2 2010 for kernel 2.6.32-21-generic (SMP).

Just to be sure everything is well configured, execute this command :

sudo alsaconf

and reboot again!

 

Again a big thanks to Stéphane Gaudreault for his tips on that even though it was for an older version of Ubuntu and for a different version of Alsa.. still did the trick!

After about a year of no jacksense on my Acer-aspire 5253 with Ubuntu 10.10 I finally fixed it when I upgraded to 11.10 and added this to my alsa-base.conf: options snd-hda-intel model=,asus (and yes that , is supposed to be infront of asus).

Now while that was a major victory in it’s own right it was overshadowed by the absolute nightmare that was Ubuntu 11.10.  Let’s put it this way, 11.10 was so incredibly offensive that after nearly 3 years with Ubuntu, the OS that I completely ditched Windows for, the OS with which my true love and appreciation for linux as a whole blossomed out of, I threw it in the can and moved onto Debian.

So here I am with Debian Squeeze 64 and lo and behold the bloody jacksense reverts back to it’s old non-workign state.  UGH!  So tonight was the night, I had some major issues to fix with my sound card and this was the big one.. Putting that line in my alsa-base.conf didn’t work and neither did about 100 other solutions and then I started thinking.  What the hell could be different about this Debian release and Ubuntu 11? I mean they are so close in almost every way, what could be different enough to cause this and likewise what could be different from 10.10 where jacksense didn’t work to 11.10 where it did work.  What changes with a distro upgrade like that?  Well if they upgraded the distro, what if they upgraded alsa?  So I checked the Debian version of alsa and sure enough it was 1.012 or something old like that and the latest version of alsa is 1.024.  I had a hopeful ah HA moment and begun to upgrade alsa(after uninstalling it first).  Got 1.024 installed, made sure that line: (options snd-hda-intel model=,asus was in the alsa-base.conf), rebooted and VIOLA! it works.. Works like a bloody charm!

I got my upgrading instructions from here: http://monespaceperso.org/blog-en/2010/05/02/upgrade-alsa-1-0-23-on-ubuntu-lucid-lynx-10-04/ but I’ll paste them below for convenience(It should be noted that I couldn’t get alsa-utils to install but it didn’t seem to make a difference):

Installation :

To do this, we must begin by determining our version of alsa as follows :

cat /proc/asound/version
Advanced Linux Sound Architecture Driver Version 1.0.21.

To avoid problems during the upgrade of Alsa-utils, we need to stop it with the following command :

sudo /sbin/alsa-utils stop

sudo apt-get -y install build-essential ncurses-dev gettext xmlto libasound2-dev
sudo apt-get -y install linux-headers-`uname -r` libncursesw5-dev

Then, we go in our personal folder and download alsa-driver, alsa-lib and alsa-utils :

cd ~
rm -rf ~/alsa* ~/.pulse*
wget ftp://ftp.alsa-project.org/pub/driver/alsa-driver-1.0.23.tar.bz2
wget ftp://ftp.alsa-project.org/pub/lib/alsa-lib-1.0.23.tar.bz2
wget ftp://ftp.alsa-project.org/pub/utils/alsa-utils-1.0.23.tar.bz2

After that, we create a new folder for the compilation and installation of the 3 files. Then, we move the 3 tar files that we just downloaded in this folder :

sudo rm -rf /usr/src/alsa
sudo mkdir -p /usr/src/alsa
cd /usr/src/alsa
sudo cp ~/alsa* .

Unpack the 3 tar files :

sudo tar xjf alsa-driver*
sudo tar xjf alsa-lib*
sudo tar xjf alsa-utils*

We compile and install alsa-driver :

cd alsa-driver*
sudo ./configure
sudo make
sudo make install

We compile and install alsa-lib :

cd ../alsa-lib*
sudo ./configure
sudo make
sudo make install

We compile and install alsa-utils :

cd ../alsa-utils*
sudo ./configure
sudo make
sudo make install

Then, we remove the 3 tar files in our personal folder that are not anymore necessary :

rm -f ~/alsa-driver*
rm -f ~/alsa-lib*
rm -f ~/alsa-utils*

Then, just restart your computer and your alsa version should be 1.0.23!

You can verify that you have now indeed have this version of alsa :

cat /proc/asound/version
Advanced Linux Sound Architecture Driver Version 1.0.23.
Compiled on May 2 2010 for kernel 2.6.32-21-generic (SMP).

Just to be sure everything is well configured, execute this command :

sudo alsaconf

and reboot again!

Finally, after reading a forum post from someone else with similar problems I decided to have a flash video playing and then opened up my volume control and check out the playback section where it shows yuo the volume per application.  Now you need to have something playing while you do this and you will have to do this for ever browser separately but as soon as I did that I could see that, for whatever reason as it was like this from the install, chrome’s output device was set to the HDMI port on my laptop.  I just selected it and switched it to the internal audio device and viola, midstream the sound came back on.  Loaded up firefox and sure enough no sound, checked it out in the volume control and what do ya know the sound device was set to the HDMI port for firefox.  Put that back and up came the sound.

Laughably stupid but thankfully a fixed problem.  Now if only I could get the jacksense to work like it finally did in ubuntu.  ugh

So after running into this problem suddently and for no ‘apparent’ reason(although it became apparent later) I noticed the complete lack of real support docs online in regards to the ALSA underrun problem.  Hopefully I can rememdy this a little bit and help some people out.

Last week I noticed skype audio was getting really choppy, it was the equivalent of seeing the conversation through a strobe light.  Odd I thought but didn’t pay it too much heed, that was until the end of the week when the audio simply stopped all together and skype refused to close down normally.  I would have to manually kill the process in terminal after the sound cut out.  This problem was exclusive to skype, which made it even more frustrating as I could have youtube and/or music playing in exaile while skype was screwing the pooch.

It occured to me today that something indeed had been changed recently right before this problem started and that was me fiddling with pulse’s daemon.conf and enabling real-time scheduling.  I can’t remember what for but this was part of the problem.  In fact there is even a mention in pulseaudio’s man page in regards to the possibility of real-time scheduling causing problems which I’ll quote here:

Alternatively,  if the risk of locking up the machine is considered too
big to enable real-time scheduling,  high-priority  scheduling  can  be
enabled  instead  (i.e.  negative  nice  level). This can be enabled by
passing –high-priority (see above) when starting  PulseAudio  and  may
also  be  enabled  with  the approriate option in daemon.conf. Negative
nice levels can only be enabled when  the  appropriate  resource  limit

RLIMIT_NICE  is  set  (see setrlimit(2) for more information), possibly
configured in /etc/security/limits.conf. A resource limit of 31 (corre‐
sponding with nice level -11) is recommended.

At this point I got a little excited as the solution seemed within reach.  I hashed out real-time schedule and implemented high-priority scheduling, restarted pulseaudio and loaded up skype.  It started fine but when I made a test call I was once again plagued by ALSA underruns.

They key here was to adjust the nice level.  I incrementally went down from -11 all the way to 3 (as in plus 3 not -3), restarted pulseaudio, loaded skype and viola!  Problem solved.  The nice level might be different for you so maybe experiment with that a little bit.

Summary:

• edit ~/.pulse/daemon.conf (or /etc/pulse/daemon.conf if you run as system)
• Hash out realtime-scheduling and realtime-priority
• Unhash high-priority and nice-level
• set nice level to 3 (not -3 or -11 for that matter)

Update:  Bah, I am still seeing these under runs.  The severity of them has gone down as skype doesn’t completely cut out now and lock up but I am getting audio cutting in and out every 2-3 seconds when making a call via skypeout.

Searching around the skype forums I found this and this actually seems to have done the trick completely:

Edit your ~/.asoundrc file

# Part I directly from ALSA Dmix Wiki

pcm.skype {
type dmix
ipc_key 1024
slave {
pcm “hw:0,0″
period_time 0
period_size 1024
buffer_size 8192
#format “S32_LE”
#periods 128
rate 44100
}
}

pcm.dsp0 {
type plug
slave.pcm “skype”
}

# This following device can fool some applications into using pulseaudio
pcm.dsp1 {
type plug
slave.pcm “pulse”
}

ctl.mixer0 {
type hw
card 0
}

pcm.pulse { type pulse }
ctl.pulse { type pulse }
pcm.!default {
type pulse
}

ctl.!default {
type pulse
}

When I finally solve the problem I nearly broke down.  The effect that hearing crystal clear music for the first time in months, especially the likes of Bear Mcreary, is an emotional experience.  For a LONG time I have been plagued with this extremely subtle but in Ubuntu where my music would have this very slight graininess to it.  It is even hard to describe what it was because it was so sublte, the best analogy I can think of would be looking through glasses that were covered in dust, or a jpeg image that has 5-10% too much compression on it.  It really isn’t enough to notice most of the time, especially with loud progressive trance.  Over time you simply get used to it, your brain adjusts but in the back of my mind I knew this was happening, especially when I would put on classical music where this graininess would be more pronounced with the delicate sounds of a violin.  I searched and searched for a solution to no avail and every time I heard the heart wrenching compositions of Bear Mcreary it is like a part of my soul just died in defeat.

I had found a few days back while going through the hellish experience that is Amarok 2 that if I was running pulse as root the audio quality would resume.  But I never really put two and two together as my settings in /etc/pulse/daemon.conf were identical to those in ~/.pulse/daemon.conf .  In fact I even deleted the latter and replaced it with the former.  What as most perplexing is that I would adjust the resampler method from something like speex-float-1 all the way to src-best-quality without any change in CPU usage or any change in quality.

But today I went one step further as I noticed that in my ~/.pulse/ directory I was missing 3 files:  “client.conf , default.pa, and system.pa” .  I am not sure why these were missing, pulse loaded fine without them but they were.  This was the only difference now between my /etc/pulse and ~/.pulse so I went and deleted everything from ~/.pulse and replaced it with what was in /etc/pulse  and VIOLA!!  I now have perfectly crystal clear sound and what a bloody relief.

So if this is you I hope this helps

First thing first, for most all applications with the exception of those running in WINE, you can to get your butt over to this thread: http://ubuntuforums.org/showthread.php?t=789578 and get PulseAudio installed.. Pulse is the key to running a proper sound server in Ubuntu(as long as you can get it running properly – something that took me weeks)

The key I found to making sure that pulse works properly in skype with multiple options for inputs is to make sure that in /system/preferences/sound you have everything on auto detect except for the Sound Capture – which is set to Pulse and that your Mixer track is set to ALSA PCM on dmix via DMA PulseAudio Mixer.

The other thing I found was that you NEED to make sure that your ~/.asoundrc file is blank.  This will become key as in the latter part of this post I will show you that you need to fill that same file with a bunch of good stuff if you want to run a USB mic in WINE appz.

So for a lot of you that probably does it for USB mics and Ubuntu.

Now for the rest of you running games and appz in WINE the story is a little different.  This is where my struggles with learning how to get audio properly working in a linux environment when from taxing to hellish.  First a word of advice to all of you wanting to use TeamSpeak and ubuntu with a USB mic or headset – USE WINE and the Windows version.  don’t even bother with the linux version as you will have days and weeks of your life sucked away.  It just doesn’t work

For some reason, at least for me WINE and pulse do NOT mix very well when it comes to the input side of things.  So when I want to use an ingame chat or Teamspeak the first thing I need to do is to shut down Pulse and rely soley on ALSA.  Now this means that a lot of the nice convenient mixer stuff that pulse does needs to be done manually. I posted all this up in the Teamspeak discussion forums and but I’ll save you the trouble of going there and copy it here as well

Now from this point onwards I am going to assume you are using ALSA , if not then you have your own google adventure to go on.

So:

go into your home directory (cd ~) and create a file called “.asoundrc” minus the quotations of course with your favorite editor ( vi ./.asoundrc ) if it doesn’t exist already.. If it does you need to make a backup of it and clear it all to start fresh
The .asoundrc file in your home directory acts as kind of a configuration file that is used to override default settings
Our goal here is to make our default capture device our USB mic and NOT our sound card, this is accomplished by inserting the following text into the .asoundrc file:

pcm.!default {
        type asym
        playback.pcm {
                type plug
                slave.pcm "hw:0,0"
        }
        capture.pcm {
                type plug
                slave.pcm "hw:1,0"
        }
}

***Something to note: “hw:0,0″ and “hw:2,0″ are MY card locations for my soundblaster and my usb mic. Yours might be different. ***

In order to find out what your desired output device is you type the following in terminal:

“aplay -l” and you should receive and output something like this:

**** List of PLAYBACK Hardware Devices ****
card 0: CA0106 [CA0106], device 0: ca0106 [CA0106]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: CA0106 [CA0106], device 1: ca0106 [CA0106]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: CA0106 [CA0106], device 2: ca0106 [CA0106]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: CA0106 [CA0106], device 3: ca0106 [CA0106]
Subdevices: 1/1
Subdevice #0: subdevice #0

Obviously My card is 0 as that is the only one that shows up, so I use “hw:0,0″ you need to make extra sure what yours is and use that.

now to find my capture device I type:
“arecord -l” and my output should be something like this:

**** List of CAPTURE Hardware Devices ****
card 0: CA0106 [CA0106], device 0: ca0106 [CA0106]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: CA0106 [CA0106], device 1: ca0106 [CA0106]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: CA0106 [CA0106], device 2: ca0106 [CA0106]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: CA0106 [CA0106], device 3: ca0106 [CA0106]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 2: default [AK5370 ], device 0: USB Audio [USB Audio]
Subdevices: 1/1
Subdevice #0: subdevice #0

Now we already know that Card 0 is my soundblaster, which I don’t want to use, so we can rule that out.. The only other option(which is conveniently labeled USB Audio) is Card 2 so that means I used “hw:2,0″ . Yours could be different so edit your .asoundrc file accodingly.

I quickly check to make sure WINE was seeing my usb mic by running the command ‘winecfg’ and going into Audio and making sure that the ALSA WAVE IN device show up as USB Audio.

I have Hardware Acceleration set to Emulation as well as Driver Emulation checked on, not sure if it matters but it is on for me and works.

So there you have it, easy peasy!  Well it is easy to do but figuring this out with next to no documentation on this specific subject was a bitch..Hope this helped

After going through the same problem again and the above solution wasn’t working all that hot for whatever reason.

pcm.!default {
type plug
slave.pcm “combined”
}

pcm.combined {
type asym
playback.pcm “playback”
capture.pcm “hw:1,0″
}

pcm.playback {
type dmix
ipc_key 1024
slave {
pcm “hw:1,0″
period_time 0
period_size 1024
buffer_size 4096
rate 44100
}
bindings {
0 0
1 1
}
}

ctl.dmixer {
type hw
card 1
}