On Fri, Apr 10, 2009 at 09:32:13PM -0400, Lee Revell wrote:
> Hmm, this all should really have worked OOTB.
>
> Any way you can revert to the stock Ubuntu 8.10 alsa, disable
> pulseaudio, and retest?
I'm actually in that state now. My initial post was a bit
misleading: I downloaded and built the
On Fri, Apr 10, 2009 at 9:28 PM, Matt Garman wrote:
> Perhaps that config file format isn't correct, e.g. I just can't use
> "plughw" as drop-in replacement for "hw".
>
You should be able to.
> So if I tell aplay directly to use plughw, it works. Thus, my
> suspicion is that I need to modify my
On Fri, Apr 10, 2009 at 09:16:08PM -0400, Lee Revell wrote:
> OK. I run the exact same distro here.
>
> Normally plughw would be built into ALSA. Not sure why it looks
> for that module.
>
> Try removing /etc/asound.conf and creating this .asoundrc in your
> home directory:
>
> pcm.!default {
OK. I run the exact same distro here.
Normally plughw would be built into ALSA. Not sure why it looks for
that module.
Try removing /etc/asound.conf and creating this .asoundrc in your home
directory:
pcm.!default {
type plughw
card 0
}
ctl.!default {
type hw
card 0
}
Also post th
On Fri, Apr 10, 2009 at 08:44:37PM -0400, Lee Revell wrote:
> On Fri, Apr 10, 2009 at 2:13 PM, Matt Garman wrote:
> > $ aplay 03_harvest.wav
> > ALSA lib pcm.c:2156:(snd_pcm_open_conf) Cannot open shared library
> > /usr/lib/alsa-lib/libasound_module_pcm_plughw.so
> > aplay: main:583: audio open
On Fri, Apr 10, 2009 at 2:13 PM, Matt Garman wrote:
> $ aplay 03_harvest.wav
> ALSA lib pcm.c:2156:(snd_pcm_open_conf) Cannot open shared library
> /usr/lib/alsa-lib/libasound_module_pcm_plughw.so
> aplay: main:583: audio open error: No such file or directory
>
> Building alsa-plugins-1.0.19 and
Hello,
I have an MAudio Audiophile 2496 PCI soundcard. My goal is have
ALSA do as little as possible, and just pass the audio to the
hardware.
$ aplay -l
List of PLAYBACK Hardware Devices
card 0: M2496 [M Audio Audiophile 24/96], device 0: ICE1712 multi [ICE1712
multi]
Subdevices:
On Thu, 9 Apr 2009 18:02:56 -0600
"s. keeling" wrote:
> You'd think grep + sed would be good for the initial change, then
> you're left with tracking down every instance where that didn't work.
> At least, that's how I write code (or maintain others' cruft).
>
> Too many cooks in the kitchen, w
