On Tue, 23 Jul 2002, Gary Scavone wrote:
>
> OK, I changed my code to do as you suggested (using the ctl interface)
> and that works. Thanks for the info.
>
> However, I still feel that my original gripe (the error message
> output) is valid. In all other cases that I'm aware of, you never
> automatically spit out an error message to stderr or stdout. Why
> should it be different in this case? There is an error retrieval
> mechanism in place, namely snd_strerror().
>
> So, what is the validation for automatically printing an error for the
> function snd_pcm_open() and not, for example, for
> snd_pcm_hw_params_any()? Why can I not determine whether a device can
> handle input by attempting to open it with the appropriate stream
> without incurring this error message?
Have you realized, that we have snd_lib_error_set_handler() function? If
you create an empty callback, you'll get no error messages. I think that
the default behaviour is good for command-line tools.
Jaroslav
-----
Jaroslav Kysela <[EMAIL PROTECTED]>
Linux Kernel Sound Maintainer
ALSA Project http://www.alsa-project.org
SuSE Linux http://www.suse.com
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
