On Fri, 28 Jul 2006 18:21:19 -0700 (PDT) Bill Unruh <[EMAIL PROTECTED]> wrote:
> On Sat, 29 Jul 2006, Sergei Steshenko wrote: > > > On Fri, 28 Jul 2006 15:20:08 -0700 (PDT) > > Bill Unruh <[EMAIL PROTECTED]> wrote: > > > >> On Sat, 29 Jul 2006, Sergei Steshenko wrote: > >> > >>> On Fri, 28 Jul 2006 17:20:57 -0400 > >>> Lee Revell <[EMAIL PROTECTED]> wrote: > >>> > >>>> On Fri, 2006-07-28 at 23:38 +0300, Sergei Steshenko wrote: > >>>>> My logic is simple: > >>>>> > >>>>> * if you are saying that a feature is supported, this means you've > >>>>> tested it - otherwise you are simply irresponsible. > >>>> > >>>> You're assuming that ALSA developers have access to every sound card > >>>> that ALSA supports which is not the case. (And your tone is insulting > >>>> as always) > >>>> > >>>> Lee > >>> > >>> Lee, you taught me STFU - it took several seconds to guess what it was. > >>> English is not my native language. > >>> > >>> So, regarding the tone, you should feel as a talented student's proud > >>> teacher. > >>> > >>> You are deviating from the issues: > >>> > >>> Do you, the developers, test the card before announcing it as supported ? > >>> > >>> If yes, what the controls for each tested feature are not written down and > >>> published ? > >>> > >>> If no, should we, ALSA end users, consider you, the developers, to be > >>> responsible > >>> folks ? > >> > >> Oh, quit it. The developers do what they do well. That does NOT mean that > >> they are good doc writers. If you look at something like Microsoft, the > >> documentation writers are totally different from the developers. They have > >> different skills. To ask the developers to write the docs is using people > >> in their area of incompetence where they will waste huge amounts of time > >> accomplishng little, whereas they could have in that same time created a > >> new driver for yet another card. > >> > >> Offer to help. Developers are NOT the ones that should be writing the > >> documentation. They should talk to the doc writers but not be the ones to > >> do it. So offer to help. > >> > > > > I still don't understand, > > > > Can developers write down values of each control they used to test each > > tested feature ? > > > > If the can write 'alsamixer' and display on its window names of controls and > > their values, whay can't the write names of controls and their values in a > > text > > or HTML file. > > > > What special skills are need for except for being a little bit literate ? > > Which they are since writing i n"C" requires it anyway ? > > > > Well, you are certainly demonstrating that you would NOT make a good writer > of documentation. What in the world would be the advantage of what you > suggest, since the user can run alsamixer and write down the values > displayed as well. The problem is NOT this. The problem people have is > actually discovering whether or not the driver actually works for their > particular card, which the manufacturer might well have totally changed but > kept the same name and model number for ( this is certainly what happens in > the wireless world, and seems to some extent also in the audio world). > Also as stated, some of the developement is done for cards which the > developer has not actually seen, but has reports from others as to what it > does. > > What sense does it make for me (or any other end ALSA user) to write down 'alsamixer' values when I do not know how they should be set to make things works in the first place ? If any of the developers tested "capture-loopback" feature of M-Audio Revolution 5.1, why didn't he write down mixer values making this feature work ? Or, even simpler, why hadn't he simply save ALSA state file and then published it ? Is it so impossible for you developers to comprehend: "log your testing process, so we, end users, will be able to just use what you've logged as our settings" ? -- Visit my http://appsfromscratch.berlios.de/ open source project. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
