Gary Scavone wrote: > I'm making use of a card's id (via the snd_ctl_card_info_get_id() > function) to access a device. Recently, I noticed some inconsistent > behavior. On a machine with an OmniIO box, if no "id" is set in the > /etc/modules.conf file, a default id of "66" is returned.
The default card id is composed of the letters and numbers of the last word of the card's name (as seen in /proc/asound/cards). > So, when I attempt to use the snd_ctl_open() function, my ascii > identifier looks like "hw:66" and the function call fails. If I > provide an "id" in /etc/modules.conf (ex. id=omniIO), then my ascii > identifier looks like "hw:omniIO" and the call to snd_ctl_open() > works. The first parameter to hw specifies the card; if it looks like a number, it will be interpreted as the card number. > On my home laptop with a Maestro2e chipset, I don't have this problem > (though I need to look more carefully at this when I go home because I > don't use the value returned from snd_ctl_card_info_get_id() if the > string length is zero and that might be happening on my laptop). The id is intended to provide a more readable identification than the card number (for humans). If you want to access a device from your program, I'd suggest to use the card number instead because it's guaranteed to never fail. HTH Clemens ------------------------------------------------------- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. _______________________________________________ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
