Mailing List Archive

hw vs. plughw
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I've got the ALSA drivers to work with the alsa supplied programs
(aplay, etc.) but xawtv does not work. The reason is that the aplay,
etc. programs support ~/.asoundrc where other programs dont.

Before i had the .asoundrc file set up correctly i could only get
aplay to work if i specified "-D plughw:0,0" (or something like that)
is there a way to specify anything like that in the myth code? The
first card ALSA detects is "hw:0,0" but the only one that works is
"plughw:0,0"

Thanks,
Magnus

-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 7.0.3 for non-commercial use <http://www.pgp.com>

iQA/AwUBPdlk48u3lhUVmrCaEQLxbwCfXjCCjPZWs5kMWr7COe9hSjLzi5EAnAmj
WQCjehV9bMwubU3kpuWmzEpv
=E9wo
-----END PGP SIGNATURE-----
Re: hw vs. plughw [ In reply to ]
On Monday 18 November 2002 05:08 pm, Magnus Ullberg wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I've got the ALSA drivers to work with the alsa supplied programs
> (aplay, etc.) but xawtv does not work. The reason is that the aplay,
> etc. programs support ~/.asoundrc where other programs dont.
>
> Before i had the .asoundrc file set up correctly i could only get
> aplay to work if i specified "-D plughw:0,0" (or something like that)
> is there a way to specify anything like that in the myth code? The
> first card ALSA detects is "hw:0,0" but the only one that works is
> "plughw:0,0"

MythTV doesn't use the alsa library, as I have a long-standing dislike of
overly complicated APIs that change completely every 6 months. It requires
the use of the oss emulation stuff that alsa provides.

Isaac