Jaroslav Kysela wrote: > > > put into device id of snd_pcm_open()? Can't find it documented > > You can put there any unique string / abbreviation of the given PCM > device.
Here's my 'aplay -l' output, what should I put into snd_pcm_open() to open card2/device0 or card1/device1? It just complains about everything I try. card 0: card0 [C-Media PCI CMI8738], device 0: CMI8738 [C-Media PCI DAC/ADC] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: card0 [C-Media PCI CMI8738], device 1: CMI8738 [C-Media PCI 2nd DAC] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: card0 [C-Media PCI CMI8738], device 2: CMI8738 [C-Media PCI IEC958] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: card1 [Ensoniq AudioPCI], device 0: ES1371/1 [ES1371 DAC2/ADC] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: card1 [Ensoniq AudioPCI], device 1: ES1371/2 [ES1371 DAC1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: card2 [M Audio Delta 1010], device 0: ICE1712 multi [ICE1712 multi] Subdevices: 1/1 Subdevice #0: subdevice #0 > It doesn't work well, if you're compiling RPM with different than > running kernel. How does the current behaviour of fixing the version to one used at .src.rpm build time make it better? There is still problem on telling users how to build and install the drivers when they just know how to click mouse in GNOME... - Jussi Laako -- PGP key fingerprint: 161D 6FED 6A92 39E2 EB5B 39DD A4DE 63EB C216 1E4B Available at PGP keyservers _______________________________________________ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
