Alexander,

you may be right from your point of view that LAME 3.90 doesn't have a bug
and that it only may trigger a bug. But: I don't think that I said that LAME
has a bug and even more importantly, this playing with words is not very
helpful for a "normal" user. Therefor let's recall the plain facts:

a) When I use LAME 3.90 my internet connection gets cut frequently (in the
meantime i've tried out what you proposed in your first letter, as you then
considered that EAC + LAME might cause the trouble. I used Razorlame and
other front ends and tried to run LAME 3.90 from the command line. No
change, connection always gets cut. I think at least we can stop the "front
end discussion" by that)
b) I have frequently used LAME 3.89 since I wrote my first mail and the
results are very satisfying. I never got cut when using it, regardless of
the front end I used.
c) No other encoder ever "triggered the same bug" which you assume is
somewhere in my OS.
d) My CPU is not overclocked.

And just to answer your question from your other mail: My network card is a
"3Com EtherLink XL 10/100"

Again (and I will now use your own words):

It sems to be a fact, that LAME 3.90 triggers a bug in my system (including
the OS), which LAME 3.89 and all previous versions don't trigger and which
no other encoder I know ever triggered. So there must be a "material change"
from version 3.89 to version 3.90, which might be capable of triggering bugs
in some users' systems.

And if you agree with that, I believe it would not be a minor reason for
considering what has been changed and how to avoid that in future versions.

Can we agree about this?

Heinz


----- Original Message -----
From: "Alexander Leidinger" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, December 27, 2001 2:33 PM
Subject: Re: [MP3 ENCODER] lame 3.90 cuts my internet connection


> On 26 Dez, [EMAIL PROTECTED] wrote:
> > A very sensible answer, Bob (though not easy to follow with my dsl
> > connection).
>
> Yes, I don't know a DSL modem which is software based and actually in
> use in germany.
>
> > And the first one which accepts that the new LAME version might really
be
> > responsible for it.
>
> Sorry, that's not correct. Even if LAME may trigger this bug, LAME isn't
> responsible for this bug. It's a bug in the OS (or a bug in the
> hardware, that's also possible, but not very likely), which LAME is able
> to trigger. The only thing lame does is to calculate some numbers, and
> that as fast as the CPU is able to do (BTW, is you CPU overclocked?).
> Even if there's a bug in LAME (which isn't impossible), the OS shouldn't
> disconnect your internet connection, so we would only have a bug in LAME
> which triggers a bug in the OS (because we didn't call a
> "close_the_internet_connection" function). If we find such a bug in LAME
> I would be very surprised (and loose the last very small piece of trust
> in software from Microsoft).
>
> Nevertless, we are willing to help you find a solution to your problem.
>
> Bye,
> Alexander.
>
> --
> Failure is not an option. It comes bundled with your Microsoft product.
>
> http://www.Leidinger.net                       Alexander @ Leidinger.net
>   GPG fingerprint = C518 BC70 E67F 143F BE91  3365 79E2 9C60 B006 3FE7
>
> _______________________________________________
> mp3encoder mailing list
> [EMAIL PROTECTED]
> http://minnie.tuhs.org/mailman/listinfo/mp3encoder

_______________________________________________
mp3encoder mailing list
[EMAIL PROTECTED]
http://minnie.tuhs.org/mailman/listinfo/mp3encoder

Reply via email to