FYI,
The ymfpci based soundcards don't seem to have an entry at:
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/alsa/alsa-driver/doc/SOUNDCARDS?rev=HEAD&content-type=text/plain
Can someone update this?
Adam
---
>I got around my previous problems (readn) in an output/capture
>application with an envy24
>(ice1712) by bypassing the plugin and going straight to hw:0,0. Had to
>change my code a bit
>but it's now **almost** working.
i humbly suggest that you:
(1) read the source code for JACK's ALSA driver
John Covici wrote:
> Using the rc2 aplay, it doesn't honor -c 1 at all, just plays on card
> 0. I even changed the aliases around so what was card1 is now 0, but
> aplay still only plays on card 0.
>
aplay -D hw:0,0 --> card 0 device 0
aplay -D hw:1,0 --> card 1 device 0 etc...
-d is for dura
I have a small perl script which I am working on. The idea is to autodetect
a card/s and create a modules.conf based on that either at configure or as
a seperate process.
Can anyone who is more fluent in perl give me a hint as to how I can
compare the output of list_pci to list_modules and retur
Try that again. after saving this time :)
I have a small perl script which I am working on. The idea is to autodetect
a card/s and create a modules.conf based on that either at configure or as
a seperate process.
Can anyone who is more fluent in perl give me a hint as to how I can
compare the ou
>I have a small perl script which I am working on. The idea is to autodetect
>a card/s and create a modules.conf based on that either at configure or as
>a seperate process.
IIRC, this has already been written, but its not up-to-date. its in
the alsa-conf CVS module.
--p
--
Paul Davis wrote:
>
> >I got around my previous problems (readn) in an output/capture
> >application with an envy24
> >(ice1712) by bypassing the plugin and going straight to hw:0,0. Had to
> >change my code a bit
> >but it's now **almost** working.
>
> i humbly suggest that you:
>
> (1) read