On Wed, 12 Apr 2006 13:38:00 +0200 Takashi Iwai <[EMAIL PROTECTED]> wrote:
> At Wed, 12 Apr 2006 14:24:52 +0300, > Sergei Steshenko wrote: > > > > On Wed, 12 Apr 2006 13:11:44 +0200 > > Ákos Maróy <[EMAIL PROTECTED]> wrote: > > > > > Takashi Iwai wrote: > > > > The default format for dsnoop is S16, and ice1712 supports only > > > > S32_LE. You have to set the format parameter in slave pcm of dsnoop, > > > > too. > > > > > > > > > thanks, now it works! > > > > > > > > > Akos > > > > > > > > > ------------------------------------------------------- > > > This SF.Net email is sponsored by xPML, a groundbreaking scripting > > > language > > > that extends applications into web and mobile media. Attend the live > > > webcast > > > and join the prime developer group breaking into this new coding > > > territory! > > > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 > > > _______________________________________________ > > > Alsa-user mailing list > > > Alsa-user@lists.sourceforge.net > > > https://lists.sourceforge.net/lists/listinfo/alsa-user > > > > > > > Guys/girls, > > > > do we always need the developers to understand that something is wrong > > with ALSA configuration ? > > > > Shouldn't ALSA SW scream loudly that the requested S16 format is not > > supported > > by the card ? > > > > Can't ALSA SW suggest on such occasions what the supported formats are ? > > > > To me the whole plugin syntax checking looks like a compiler that never > > reports user errors. > > > > Is it the way compilers should be written ? > > > > Is this non-error-reporting because of HW manufacturers don't want to make > > specs known or because of the decisions made by ALSA developers ? > > > > Should a bug report be filed ? > > You're right about that the syntax checking or error messages could be > improved. But I have no big interest to improve this _right now_. > The more important thing is to provide a reasonable default setting > that you don't have to play with the extra configuration. So, don't > count me in this action. > > (In this case, he doesn't have to set up such a dsnoop configuration > at all, as I mentioned in another mail. The default setup should > work as it is.) > > BTW, a user-friendly error message is one of the most difficult thing > in programs. Surely you've seen many examples from popluar and basic > programs like gcc or (La)TeX... > > Anyway, as always, any improvement patches are welcome :) > > > Takashi > > > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking scripting language > that extends applications into web and mobile media. Attend the live webcast > and join the prime developer group breaking into this new coding territory! > http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642 > _______________________________________________ > Alsa-user mailing list > Alsa-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/alsa-user > Quite a long time I looked into design of simple compilers - ~5000 lines Pascal one, similar size RAT C compiler. Percentage-wise most of the code was devoted to error checking rather than to "constructive" action. The same is true about serious parsers I've written. I am trying to say that a very poor decision not to implement making sense to end user syntax and semantics checking was made. Too bad IMHO. And the most likely way to resolve this is full rewrite. Again, too bad... By the way, I'm mostly comfortable with 'gcc' error messages. ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642 _______________________________________________ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
