rnergy
Mar 10 2003, 22:33
Why lame crash everytime? When I use Musepack for multiple encoding he never crash, when I use ogg vorbis encoder for multiple files he never crash too...but...when I encode multiple files with lame 3.90.2, 3.92 or 3.93.1 he ALWAYS crash. I know this is maybe a bad memory hardware but... why other encoder never crash (Mpc or ogg) ?
(sorry for bad english)
Thx
Gabriel
Mar 11 2003, 09:29
Because your processor is overclocked or overheating.
Yes, I know, you probably ran some burn-in tests and they were fine. But trust me, Lame is really able to demonstrate that a computer is not stable.
budgie
Mar 11 2003, 09:37
I have an overclocked comp, too, and made already batch encoding with 132 files at once (--alt-preset extreme -Z --lowpass 21) and had no problem... just yesterday I encoded 60 files (insane with lowpass 21) and no problem again...
Dibrom
Mar 11 2003, 09:50
QUOTE (budgie @ Mar 11 2003 - 01:37 AM)
I have an overclocked comp, too, and made already batch encoding with 132 files at once (--alt-preset extreme -Z --lowpass 21) and had no problem... just yesterday I encoded 60 files (insane with lowpass 21) and no problem again...
This doesn't mean that this guy's computer is stable though.
I suggest doing some searches about LAME and overclocking on the forums here. If LAME is crashing, it's due to instabilities with your processor for some reason or another, and it's usually do to overheating or overclocking like Gabriel said.
Gabriel
Mar 11 2003, 13:15
It might also be because of a previous generation of C3 processor from Via.
NumLOCK
Mar 11 2003, 14:18
Might also be a RAM module gone bad. It happens.
rnergy
Mar 11 2003, 18:25
I have Athlon xp 1800+ & 768 mo . Why the lame compile crash on unstable system and all other encoder don't crash? I love lame compile but I encode 8 file at a time it's not funny for over 200 files to encode!!!
I think now I will go for fhg encoder. He don't crash on my system.
At the same time...can I have the maximum bandwidth for fhg (this is maybe lowpass for other encoder) ? (15 500 hz more or less)
Thx in advance & thx very much for your quick answers !!!
(sorry for my bad english...I learn...I learn...thx)
Gabriel
Mar 12 2003, 13:15
Well, if the system is not stable, I prefer the encoder to crash.
It could be way worse if it would not crash. You could be encoding (without any crash), and the encoder could produces some errors in its computations, reducing the produced audio quality without you noticing it.
This would be really bad.
I definitively prefer pure crash than hazardous and random results.
rnergy
Mar 12 2003, 13:44
Thx...you know what? I make a test with the lame 3.94a11 and he never crash. I encode over 400 files and he never crash. Do you have explication? My system unstable with lame 3.90.2, 3.92 and 3.93.1 but my system stable with lame 3.94a11. I really don't know what it happen?
Thx everyone....
NeoRenegade
Mar 12 2003, 17:41
Um, seriously, somebody, please, if anybody knows, give him the problematic processor switches, for chrissakes.
William
Mar 12 2003, 19:13
@rnergy
1) What is your system spec?
2) What is the compiler used in different LAME versions?
3) How much do you overclock if you really did it?
Btw, I think one point must be made clear:
Once you overclock the system, nothing is guaranteed. You use it at your own risk.
rnergy
Mar 12 2003, 20:16
QUOTE
1) What is your system spec?
I have AMD athlon 1800+ with 768 ram, 2 x 40 go HD
QUOTE
2) What is the compiler used in different LAME versions?
I use alt-preset cbr 128 for all version
QUOTE
3) How much do you overclock if you really did it?
I never overclock my system and the case is open.
I don't know why different compile crash. The solution is maybe underclock my system !!!
thx for all answers and I think i will get a new solution...thanks !!!
NeoRenegade
Mar 14 2003, 18:27
2) The compiler (listed on the encoding screen), NOT the commandline!
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please
click here.