On Wed, 10 Oct 2001 14:31:22 -0400, Artemis3 <[EMAIL PROTECTED]> wrote:
>Hi Brent! > >On Tue, 09 Oct 2001, Brent Geery wrote: > >> For some unknown reason, there seems to be hostile resistance to >> adding a simple balance adjusting feature to LAME. I'm not sure I >> understand the hostility. It wouldn't add an load to the programmers >> load, as the functions are already there in the --scale function. > > I don't understand what you mean with "resistance". You are >forgetting the real purpose of lame is not to process audio; it >was a generous gift that some processing is already done with >it, but the real solution is to use the proper tools. Maybe you picked poor words, but LAME's ONLY job is processing audio! In any case, no matter how you define the word, LAME already implements the scale feature (like it or not.) All I am asking is for it to act on a single channel. If you start a crusade to remove the scale function, then your comments carry more weight. As is stands, this argument makes little sense. And while we are at it, why not remove the low-/high-pass filtering? This is also "processing" the wav. I can name lots of other features that should be removed, under your definition of what LAME should do. > In any case, like in any open project, you are not supposed >to *ask* but to _give_. That means, do the patch, submit it, >and hope for the best. Can't program? That's sad; you can't >force anyone to do it for you, specially the few lame >developers that are already *very* busy focusing on the >priority things. Who is "forcing" anyone to do anything? I have posted a feature request; and so far, am only getting fanboy flack. I have received private emails from *programmers* (not fanboys) expressing their interest in implementing the feature. From their input, I'm told it will take under a dozen lines of code to implement. However, they want to wait for the alpha to go beta. > This message goes also to the person requesting better >documentation; maybe its time to find the answers for himself, >make a patch to update the documentation and submit the >changes. Yeah, that's just what we want: the blind leading the blind. Part of programming is documenting your code. Ever try reading another's code, and figure out what it does!? :) -- BRENT - The Usenet typo king. :) Fast Times At Ridgemont High Info http://www.FastTimesAtRidgemontHigh.org Voted #87 - American Film Institute's Top 100 Funniest American Films _______________________________________________ mp3encoder mailing list [EMAIL PROTECTED] http://minnie.tuhs.org/mailman/listinfo/mp3encoder
