Issue apeared sometime between beta 2 and the final release. Seems to affect programs that run directly through alsa more than those that use pulse. There are also times when recording will drop causing missed words or sounds.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: alsa-base 1.0.25+dfsg-0ubuntu4
ProcVersionSignature: Ubuntu 3.13.0-24.46-lowlatency 3.13.9
Uname: Linux 3.13.0-24-lowlatency x86_64
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC1: benjamin 2174 F.... pulseaudio
/dev/snd/pcmC1D0c: benjamin 2174 F...m pulseaudio
/dev/snd/pcmC1D0p: benjamin 2174 F...m pulseaudio
/dev/snd/controlC0: benjamin 2174 F.... pulseaudio
CurrentDesktop: Unity
Date: Mon Apr 21 11:03:33 2014
InstallationDate: Installed on 2014-03-18 (34 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Speaker, Internal
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: Underruns, dropouts, or "crackling" sound
Title: [Q501LA, Realtek ALC282, Speaker, Internal] Underruns, dropouts or crackling sound
UpgradeStatus: Upgraded to trusty on 2014-03-18 (33 days ago)
dmi.bios.date: 05/10/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: Q501LA.205
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: Q501LA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrQ501LA.205:bd05/10/2013:svnASUSTeKCOMPUTERINC.:pnQ501LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnQ501LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: Q501LA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-04-19T10:10:51.473145
This bug seems to apear on a second computer I own with the same audio chipset. All work arounds have been applied on both systems with no noticeable change.