Skip to contentSkip to conversation

aplay won't play on any second sound card

DISCUSSION John Covici 3 participants 5 messages Jul 11, 2002 – Jul 12, 2002

lore
Share & tools
lore
#0 lore raw

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.

Signature · 8 lines
         John Covici
         [email protected]


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
PC Mods, Computing goodies, cases & more
http://thinkgeek.com/sf
#1 lore raw
Quoted 4 lines · John Covici

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 duration of play.

Signature · 12 lines
Patrick Shirkey - Boost Hardware Ltd.
For the discerning hardware connoisseur
Http://www.boosthardware.com
Http://www.boosthardware.com/LAU/guide/
========================================



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Gadgets, caffeine, t-shirts, fun stuff.
http://thinkgeek.com/sf
#2 lore raw

autodetection at install

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 return the correct card name and module?

The script has two subs. They just parse the /proc/pci and the INSTALL file to get the current output. It has to be run from the alsa-driver dir.

Signature · 5 lines
Patrick Shirkey - Boost Hardware Ltd.
For the discerning hardware connoisseur
Http://www.boosthardware.com
Http://www.boosthardware.com/LAU/guide/
========================================

sub list_pci {

	open (FILE, "/proc/pci") 
	or die "Cannot open /proc/pci. \n Do you have permission to access this file?";
   
    for $linepci (<FILE>) {
	
	if ($linepci =~ /Multimedia audio controller/g) {
   	print $linepci;
	}
    }

# close FILE;

}

sub list_modules {

	open (FILE, "INSTALL") 
	or die "Cannot open INSTALL. \n Do you have permission to access this file?";
   
    	for $linemodule (<FILE>) {

	if ($linemodule =~ /\.o$/) {
#		print  $linemodule;
		    	while (<>) {
				foreach $word ( split ) { 
	    				# do something with $word here
	   				print "$linemodule\n" ;
					} 
    				}  

# print $linemodule;

		}
    	}

# close FILE;
}

# Output to shell

list_modules();

print "\n The modules for the following card/s can be found in the above.\n If your card is not listed below it means it is a PNP (very old)\n or USB card and this script cannot find it.\n\n The modules for ALSA USB support are: \n\n \tsnd-usb-audio\n \tsnd-usb-midi\n\n";

print " These are the cards found on your system:\n\n"; list_pci();
print "\n";

#4 lore raw

autodetection at install

In reply to Patrick Shirkey

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 output of list_pci to list_modules and return the correct card name and module?

The script has two subs. They just parse the /proc/pci and the INSTALL file to get the current output. It has to be run from the alsa-driver dir.

Signature · 5 lines
Patrick Shirkey - Boost Hardware Ltd.
For the discerning hardware connoisseur
Http://www.boosthardware.com
Http://www.boosthardware.com/LAU/guide/
========================================

sub list_pci {

	open (FILE, "/proc/pci") 
	or die "Cannot open /proc/pci. \n Do you have permission to access this file?";
   
    for $linepci (<FILE>) {
	
	if ($linepci =~ /Multimedia audio controller/g) {
   	print $linepci;
	}
    }

# close FILE;

}

sub list_modules {

	open (FILE, "INSTALL") 
	or die "Cannot open INSTALL. \n Do you have permission to access this file?";
   
    	for $linemodule (<FILE>) {

		if ($linemodule =~ /\.o$/) {
			print  $linemodule;
		}
    	}

# close FILE;
}

# Output to shell

list_modules();

print "\n The modules for the following card/s can be found in the above.\n If your card is not listed below it means it is a PNP (very old)\n or USB card and this script cannot find it.\n\n The modules for ALSA USB support are: \n\n \tsnd-usb-audio\n \tsnd-usb-midi\n\n";

print " These are the cards found on your system:\n\n"; list_pci();
print "\n";

#3 lore raw

Re: autodetection at install

In reply to Patrick Shirkey
Quoted 3 lines

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

-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Gadgets, caffeine, t-shirts, fun stuff.
http://thinkgeek.com/sf