Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: Lame alternatives (Read 18238 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Lame alternatives

I've tried now different PCs one being the HP nx8220 laptop I'm typing this on and LAME 3.97 seems to crash repeatedly with VBR 192. I'm ripping CAMEL's I can see your house from here with EAC. It stops in the first track Wait.

Overclocking is not really possible with this laptop. 

What are the alternatives to LAME?

Lame alternatives

Reply #1 –
Quote from: th00ht on
LAME 3.97 seems to crash repeatedly with VBR 192. What are the alternatives to LAME?


More than 180,000 conversions with LAME 3.97, and I can't recall a single crash. I'd say your problem lies elsewhere.

Lame alternatives

Reply #2 –
Quote from: csiron on
Quote from: th00ht on

LAME 3.97 seems to crash repeatedly with VBR 192. What are the alternatives to LAME?


More than 180,000 conversions with LAME 3.97, and I can't recall a single crash. I'd say your problem lies elsewhere.


where? 

tried this with a the mentioned HP nx8220 laptop and a Shuttle Reflection XPC. Common factor being EAC and Windows XPSP2.

But thanks for the message (please do look at others reporting frequent crashes with 3.97)

Lame alternatives

Reply #3 –
Laptops are known to overheat easy when subjected to high processor loads, I know I've had a couple that could not do extended encodes.

Lame alternatives

Reply #4 –
Quote from: th00ht on
What are the alternatives to LAME?

LAME 3.98b6 would be a good replacement for 3.97.

I'm quite sure that LAME does not crash. One common problem is, you're trying to feed in some ID3 genre, which is not a valid ID3v1 genre. In this case, 3.98 will help you, or you can add "--ignore-tag-errors" to your command line.

Lame alternatives

Reply #5 –
Quote from: robert on
Quote from: th00ht on

What are the alternatives to LAME?

LAME 3.98b6 would be a good replacement for 3.97.

I'm quite sure that LAME does not crash. One common problem is, you're trying to feed in some ID3 genre, which is not a valid ID3v1 genre. In this case, 3.98 will help you, or you can add "--ignore-tag-errors" to your command line.



Thanks robert.
So this would mean to add these as additional parameters to EAC?

Quote from: th00ht on
Quote from: robert on

Quote from: th00ht on

What are the alternatives to LAME?

LAME 3.98b6 would be a good replacement for 3.97.

I'm quite sure that LAME does not crash. One common problem is, you're trying to feed in some ID3 genre, which is not a valid ID3v1 genre. In this case, 3.98 will help you, or you can add "--ignore-tag-errors" to your command line.



Thanks robert.
So this would mean to add these as additional parameters to EAC?



So not really. LAME crashed again. I would love to have someone tell me where to get diagnostic information that could possible help someone to fix this.

this is on my screen right now:

LAME version 4.0 (alpha 14, May 25 2006 12:48:18) (http://www.mp3dev.org/)

warning: alpha versions should be used for testing only

Using MDCT filter
  Lowpass  filter, transition band: 17461 Hz - 17548 Hz
Encoding F:\@Shared\Shared Music\Camel\I Can See Your House From Here\0tmp1!542.
wav
      to F:\@Shared\Shared Music\Camel\I Can See Your House From Here\0tmp1!542.
mp3
Encoding as 44.1 kHz VBR(q=4) j-stereo MPEG-1 Layer III (ca. 10x) qval=2
    Frame          |  CPU time/estim | REAL time/estim | play/CPU |    ETA
  6969/11623  (60%)|    0:07/    0:12|    0:07/    0:12|  24.254x|    0:05
192 [5667] %%%%%%%%%%%%%%%%%%%%%%********************************************
224 [ 934] %%%%%%%****
256 [ 316] %%**
320 [  51] %
---------------------------------------------02:01-----------------------------
  kbps        LR    MS  %    long switch short %
  200.1      37.2  62.8        96.7  2.2  1.1

Lame alternatives

Reply #6 –
Quote from: th00ht on
this is on my screen right now:

LAME version 4.0 (alpha 14, May 25 2006 12:48:18) (http://www.mp3dev.org/)

warning: alpha versions should be used for testing only

Turns out you are not using LAME 3.97.

Also, could you be more specific about how it crashes? Do you get any error messages?

Lame alternatives

Reply #7 –
Try using the current version of lame, not some ancient alpha that wasn't made for encoding.

Lame alternatives

Reply #8 –
You are using some unofficial LAME 4 alpha build, not LAME 3.97 as you were telling above. You should replace it with some LAME 3 version.

Lame alternatives

Reply #9 –
Splitting ripping and converting might give some hints:

1) Have you tried to rip to wav (EAC menu Action>Copy>Uncompressed)? Does that work OK?

2) Have you tried to just convert an existing wav file to mp3 for example through system commandline (DOS Window) or with some frontend? What happens?

Lame alternatives

Reply #10 –
Quote from: Alexxander on
Splitting ripping and converting might give some hints:

1) Have you tried to rip to wav (EAC menu Action>Copy>Uncompressed)? Does that work OK?

2) Have you tried to just convert an existing wav file to mp3 for example through system commandline (DOS Window) or with some frontend? What happens?



Yes that works, thanks for aksing alexxander. FLAC also works fine. Only the LAME encoder seems to cause trouble

Lame alternatives

Reply #11 –
Quote from: th00ht on
I've tried now different PCs one being the HP nx8220 laptop I'm typing this on and LAME 3.97 seems to crash repeatedly with VBR 192. I'm ripping CAMEL's I can see your house from here with EAC. It stops in the first track Wait.

Overclocking is not really possible with this laptop. 

What are the alternatives to LAME?


For mp3? Well there are lots in theory I guess but none worth using  I use the nero aac codec as my replacement but that's prolly not an option for you...

like others in this thread, I've *NEVER* experienced a crash with LAME that was a direct result of it. There may be some other instability in your machine.

Lame alternatives

Reply #12 –
Quote from: robert on
You are using some unofficial LAME 4 alpha build, not LAME 3.97 as you were telling above. You should replace it with some LAME 3 version.



Please let me know what is "official". Where would I locate an official LAME build?

Quote from: frozenspeed on
Quote from: th00ht on

I've tried now different PCs one being the HP nx8220 laptop I'm typing this on and LAME 3.97 seems to crash repeatedly with VBR 192. I'm ripping CAMEL's I can see your house from here with EAC. It stops in the first track Wait.

Overclocking is not really possible with this laptop. 

What are the alternatives to LAME?


For mp3? Well there are lots in theory I guess but none worth using  I use the nero aac codec as my replacement but that's prolly not an option for you...

like others in this thread, I've *NEVER* experienced a crash with LAME that was a direct result of it. There may be some other instability in your machine.


Thanks for pointing that out, frozenspeed. My machine is just as stable as any Windows XP SP2 machine ;-) and I have no problems using other programs

Lame alternatives

Reply #16 –
Quote from: th00ht on
Quote from: Alexxander on
Splitting ripping and converting might give some hints:
1) Have you tried to rip to wav (EAC menu Action>Copy>Uncompressed)? Does that work OK?
2) Have you tried to just convert an existing wav file to mp3 for example through system commandline (DOS Window) or with some frontend? What happens?
Yes that works, thanks for aksing alexxander. FLAC also works fine. Only the LAME encoder seems to cause trouble

Just to eliminate any doubt because I'm not sure reading your answer:

Have you tried option 2) (converting through commandline or frontend)?

And: Are you now using v3.97 or 3.98b6 as suggested?

Lame alternatives

Reply #17 –
I was using 3.97 and used lame-3.98b6_2008021306 (LAME 32bits version 3.98 (beta 6, Feb 13 2008) (http://www.mp3dev.org/)) with similar result.
I've ripped to .wav file and started lame as : "C:\Program Files\lame\lame.exe" "01. Wait.wav".

It crashes with this:

F:\@Shared\Shared Music\Camel\I Can See Your House From Here>"C:\Program Files\l
LAME 3.98 (beta 6, Feb 13 2008) 32bits (http://www.mp3dev.org/)
CPU features: MMX (ASM used), SSE (ASM used), SSE2
Using polyphase lowpass filter, transition band: 16538 Hz - 17071 Hz
Encoding 01. Wait.wav to 01. Wait.wav.mp3
Encoding as 44.1 kHz 128 kbps j-stereo MPEG-1 Layer III (11x) qval=3
    Frame          |  CPU time/estim | REAL time/estim | play/CPU |    ETA
  3900/11623  (34%)|    0:09/    0:26|    0:09/    0:26|  11.281x|    0:17
-------------------------03:21-------------------------------------------------
  kbps        LR    MS  %    long switch short %
  128.0      51.0  49.0        97.8  1.3  0.8

or with this:

F:\@Shared\Shared Music\Camel\I Can See Your House From Here>"C:\Program Files\lame\lame.exe" "01. Wait.wav"
LAME 3.98 (beta 6, Feb 13 2008) 32bits (http://www.mp3dev.org/)
CPU features: MMX (ASM used), SSE (ASM used), SSE2
Using polyphase lowpass filter, transition band: 16538 Hz - 17071 Hz
Encoding 01. Wait.wav to 01. Wait.wav.mp3
Encoding as 44.1 kHz 128 kbps j-stereo MPEG-1 Layer III (11x) qval=3
    Frame          |  CPU time/estim | REAL time/estim | play/CPU |    ETA
  8300/11623  (71%)|    0:19/    0:27|    0:20/    0:28|  11.132x|    0:08
-----------------------------------------------------01:26---------------------
  kbps        LR    MS  %    long switch short %
  128.0      39.0  61.0        98.1  1.2  0.7                              Assertion failed: p > 0, file libmp3lame/psymodel.c, line 1242

abnormal program termination

F:\@Shared\Shared Music\Camel\I Can See Your House From Here>

or this:

F:\@Shared\Shared Music\Camel\I Can See Your House From Here>"C:\Program Files\lame\lame.exe" "01. Wait.wav"
LAME 3.98 (beta 6, Feb 13 2008) 32bits (http://www.mp3dev.org/)
CPU features: MMX (ASM used), SSE (ASM used), SSE2
Using polyphase lowpass filter, transition band: 16538 Hz - 17071 Hz
Encoding 01. Wait.wav to 01. Wait.wav.mp3
Encoding as 44.1 kHz 128 kbps j-stereo MPEG-1 Layer III (11x) qval=3
    Frame          |  CPU time/estim | REAL time/estim | play/CPU |    ETA
  9500/11623  (82%)|    0:22/    0:27|    0:22/    0:26|  11.063x|    0:04
-------------------------------------------------------------00:55-------------
  kbps        LR    MS  %    long switch short %
  128.0      37.3  62.7        98.2  1.1  0.7

Moderadion: Extra quotations removed

Lame alternatives

Reply #18 –
You could try LAME 3.90.3 at --alt-preset standard (which is about 192 VBR) and see if that works or use a command line fhg mp3 encoder which has a offical download link someware on the net for the fhg surround sound which can do VBR (but does not use 320kbps frames) and supports SMB. ATM am thinking EAC could is likely to be causing the crashes after the drive is not in use while encoding or something is making the ripped WAV files courrpt. Make sure you did not change the Waveform settings, which should be disabled when EAC is configured to external encoder.
"I never thought I'd see this much candy in one mission!"

Lame alternatives

Reply #19 –
Have you tried the 12 March compile of 3.98beta6?

Lame alternatives

Reply #20 –
Quote from: Highlander on
Quote from: th00ht on

Quote from: robert on

You are using some unofficial LAME 4 alpha build, not LAME 3.97 as you were telling above. You should replace it with some LAME 3 version.

Please let me know what is "official". Where would I locate an official LAME build?

I think here is a good place.



..which, by incident is the version I'm using.

Quote from: /mnt on
You could try LAME 3.90.3 at --alt-preset standard (which is about 192 VBR) and see if that works or use a command line fhg mp3 encoder which has a offical download link someware on the net for the fhg surround sound which can do VBR (but does not use 320kbps frames) and supports SMB. ATM am thinking EAC could is likely to be causing the crashes after the drive is not in use while encoding or something is making the ripped WAV files courrpt. Make sure you did not change the Waveform settings, which should be disabled when EAC is configured to external encoder.



ehrm, thanks /mnt .

I was using 3.97.  "official" does not seem to mean very much, more like a "it works for me". I would not understand how to change the Waveform settings so probably I have not changed these (right?)

Lame alternatives

Reply #21 –
OK, first, I'm still seeing various versions in your reports so I'm not clear: Are you using 3.97. Use 3.97, and don't work with alphas, betas or outdated versions. Stick with the current version, so we can diagnose the problem in a straightforward way. From the sounds of things, an alpha, beta or anything else isn't for you anyway.

Second, but closely related, let's steer away from advice that is not 3.97-specific. Rolling him back or ahead is only making matters worse and just confusing people -- especially me!

Lame alternatives

Reply #22 –
I would also recommend going with -V 2 --vbr-new instead of 192kbps VBR.  192kbps VBR sounds like it is one of those mp3 presets built into EAC.  Instead you should either select User Defined Encoder or use the Lame mp3 option but set the bitrate to 128kbps and use the command line of -V 2 --vbr-new.  -V 2 should come out to around 190kbps VBR but it depends on the complexity of the music.  You should always use the presets when encoding VBR mp3s.  Those presets (the various -V values) were designed to give you a constant quality level, not a constant bitrate level (as does the 192kbps VBR setting in EAC does).

Lame alternatives

Reply #23 –
You should stick to John33's binary, I'd never experience any crash or problems with his work.

http://www.rarewares.org
Hong Kong - International Joke Center (after 1997-06-30)

Lame alternatives

Reply #24 –
I encode within foobar and also have random crashes. But only on my old AMD machine that has big temperature problems. I never had any issues on my cool Core2Duo machine. So I am sure it must have to do something with the temperature, especially when you are on a laptop.

Alex