Lame 3.98a9 error encoding

Topic: Lame 3.98a9 error encoding (Read 7200 times) previous topic - next topic

0 Members and 1 Guest are viewing this topic.

Lame 3.98a9 error encoding

2006-12-20 19:10:11

I was tring to convert wav's to mp3's with frontah using Lame 3.98a9 and the setting -V 2 --vbr-old and I got this error

"Assertion failed: thr >= 0, file psymodel.c, line 670"

Edit: tried with -V 2 --vbr-new and got the same results

Lame 3.98a9 error encoding

Reply #1 – 2006-12-20 19:22:40

Quote from: Fishman0919 on 2006-12-20 19:10:11

I was tring to convert wav's to mp3's with frontah using Lame 3.98a9 and the setting -V 2 --vbr-old and I got this error

"Assertion failed: thr >= 0, file psymodel.c, line 670"

Edit: tried with -V 2 --vbr-new and got the same results

There's a link with a working version in another topic about this issue.

Edit: Muahahahahahaha! I was first!

Lame 3.98a9 error encoding

Reply #2 – 2006-12-20 19:26:06

http://www.hydrogenaudio.org/forums/index....&hl=3.98a9#

Edit: Damn. Beat while I was searching.

Lame 3.98a9 error encoding

Reply #3 – 2006-12-20 19:34:51

Thx, sorry I'm at work and didn't have much time to search

Lame 3.98a9 error encoding

Reply #4 – 2006-12-20 20:28:49

Rarewares has updated 3.98a9 compiles which may fix this.

Lame 3.98a9 error encoding

Reply #5 – 2006-12-20 20:36:46

Quote from: dv1989 on 2006-12-20 20:28:49

Rarewares has updated 3.98a9 compiles which may fix this.

Nope, they don't! I could probably 'fix' it by commenting out the offending 'assert', but I'm sure that would not really be the right thing to do. Hopefully, Robert will fix it in the CVS momentarily.

Lame 3.98a9 error encoding

Reply #6 – 2006-12-20 20:50:11

Ah, sorry, John! I simply assumed that because I thought that they were re-uploaded after a day.

Lame 3.98a9 error encoding

Reply #7 – 2006-12-20 21:05:29

Well, I just tried commenting out the offending 'asserts' and although it completes encoding, '-V 2 --vbr-new' produces what is almost CBR at 319kbps!! So, clearly something has been broken.

Lame 3.98a9 error encoding

Reply #8 – 2006-12-20 21:06:59

Haha, this is a pickle! Well, let's hope that the good LAME developers figure something out soon.

Lame 3.98a9 error encoding

Reply #9 – 2006-12-20 21:23:58

Well, I don't have newer sources than what's in CVS already. John33 are you sure you have latest sources? Did you make a clean rebuild?

Lame 3.98a9 error encoding

Reply #10 – 2006-12-20 23:00:17

Quote from: robert on 2006-12-20 21:23:58

Well, I don't have newer sources than what's in CVS already. John33 are you sure you have latest sources? Did you make a clean rebuild?

Yep. Just double checked everything and building via the VC6 IDE and the VC8 IDE, both using ICL9.1 yields the same error message.

Lame 3.98a9 error encoding

Reply #11 – 2006-12-20 23:21:10

Hmmm, a straight VC8 compile encodes cleanly, but the ICL version fails. I'll look at this more closely tomorrow.

Lame 3.98a9 error encoding

Reply #12 – 2006-12-21 02:19:31

Still the same error with latest CVS code, compiled by MinGW, no extra optimization.

Lame 3.98a9 error encoding

Reply #13 – 2006-12-21 02:30:13

10 minutes ago I checked in a bug fix, so you may try again later.

Lame 3.98a9 error encoding

Reply #14 – 2006-12-21 02:47:04

Alright.

Now it's OK.

BTW, how can I optimize compilation of lame with MinGW as compiler? Should I change Makefile options or do something else, like get a copy of nasm?

Lame 3.98a9 error encoding

Reply #15 – 2006-12-21 10:05:55

Quote from: robert on 2006-12-21 02:30:13

10 minutes ago I checked in a bug fix, so you may try again later.

Thanks a lot Robert, all seems OK now.

The only problem I have now is that Rarewares is down, so I can't upload!!

If anyone is desperate, you can download alpha10 from: http://homepage.ntlworld.com/jfe1205/LAME/ until I can get back to Rarewares.

Lame 3.98a9 error encoding

Reply #16 – 2006-12-21 10:10:21

Quote from: robert on 2006-12-21 02:30:13

10 minutes ago I checked in a bug fix, so you may try again later.

As that will be alpha10 on Rarewares and as I tested the dll based alpha9 version from the link you provided:

Should I expect another behavior so that it's worth testing again? Or is it just a technical bug fix for the assertion error?

Lame 3.98a9 error encoding

Reply #17 – 2006-12-21 12:25:58

It's more of a technical fix, you don't need to test the same samples again.

Lame 3.98a9 error encoding

Reply #18 – 2006-12-21 13:10:06

Rarewares is back up and the files are now in their usual place.