[MP3 ENCODER] CVS VBR Problems

I just updated to the latest version in CVS and I was just testing various options and I cant seem to encode VBR streams at all. I keep getting access violations. I ran the debugger and it pointed back to: 0040F586 fld qword ptr [ecx*8+455A80h] Also this is the crash output: LAME

Re: [MP3 ENCODER] CVS VBR Problems

Hello Joshua, Sunday, May 21, 2000, 11:53:49 AM, you wrote: JB I just updated to the latest version in CVS and I was just testing various JB options and I can’t seem to encode VBR streams at all. I keep getting access JB violations. I ran the debugger and it pointed back to: i have got the

[MP3 ENCODER] cast problem in takehiro.c

Hello, all. In file takehiro.c, I got following errors. I think unsinged should be changed to int, or all must be casted. Error : cannot convert 'unsigned int *' to 'int *' takehiro.c line 247 return count_bit_noESC(ix, end, 1, s); Error : cannot convert 'unsigned int *' to 'int *'

Re: [MP3 ENCODER] type mismatch error in quantize-pvt.c line 1088

Osamu Shigematsu schrieb am Son, 21 Mai 2000: Hello, all. I'm now trying to make LAME 3.83 on Macintosh with CodeWarrior. My compiler says, that Error : type mismatch 'int *' and 'int' quantize-pvt.c line 1088 if (scalefac-s[sfb]0) /* scfsi! */ So I fix if

[MP3 ENCODER] 3.84a1 vbr bitrate tweaks = ok.

Hello Robert, I was just going to note that now with the new 3.83 I'm getting albums averaging 220kbit/s (-V1 -mj -h -b128), and I saw you fixed some in the CVS already: quantize-pvt.c 1.106 11 hours robert minor tweaks quantize.c 1.101 11 hours robert minor tweaks I downloaded 3.84a1_b

Re: [MP3 ENCODER] CVS VBR Problems

Hello, Joshua. I'm a japanese lame-user. Please excuse my bad English. - Original Message - From: "Joshua Bahnsen" [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Sunday, May 21, 2000 4:53 PM Subject: [MP3 ENCODER] CVS VBR Problems I just updated to the latest version in CVS and I was

Re[2]: [MP3 ENCODER] CVS VBR Problems

Hello Robert, Sunday, May 21, 2000, 2:42:26 PM, you wrote: RH Would you be so nice and compile lame with Debugging enabled in VC5? RH I don't have that compiler, I only have the Intel demo and did not find RH any problems here. to clear up misinformation from my last message, i test

Re: [MP3 ENCODER] type mismatch error in quantize-pvt.c line 1088

Hello, Robert. on 00.5.21 8:41 PM, Robert Hegemann at [EMAIL PROTECTED] wrote: Hi, the correct fix looks like this: if (scalefac-l[sfb]0) Oh, thank you. I will replace that code. -- Osamu Shigematsu mailto:[EMAIL PROTECTED] -- MP3 ENCODER mailing list ( http://geek.rcc.se/mp3encoder/

Re: [MP3 ENCODER] CVS VBR Problems

Thanx, I committed some to fix this bug. "z" == zkt [EMAIL PROTECTED] writes: I just updated to the latest version in CVS and I was just testing various options and I can't seem to encode VBR streams at all. I keep getting access violations. I ran the debugger and it

[MP3 ENCODER] new scalefac_scale algorithm

Hi, all I added a new scalefac_scale algorithm to CVS version of LAME, which enables with -Y option. "scalefac_scale" makes the scalefactor's dynamic range large. With this option, LAME will try more scalefactor combination than without it to find the best. Test this option and check the

[MP3 ENCODER] Re: new scalefac_scale algorithm

I wrote; I added a new scalefac_scale algorithm to CVS version of LAME, which enables with -Y option. Sorry, -Y option is used for Mark's new VBR routine so I changed "new scalefactor_scale algorithm" from -Y to -Z option. --- Takehiro TOMINAGA // may the source be with you! -- MP3

Re: [MP3 ENCODER] totbit/write_timing overflow

"M" == Mark Taylor [EMAIL PROTECTED] writes: M I just committed a crude fix for the totbit/write_timing M overflow problem (last 10 lines of bitstream.c in CVS) but M Takehiro may have a better idea. Uum... OK, I'll make it. --- Takehiro TOMINAGA // may the source be with you! --

[MP3 ENCODER] Where did the VBR speed go?

Hello, To be clear, I don't mind, but am just curious: Lame 370 gave me 1.7 speed on my Cel400@450 (dkutsanov) Lame 383 gives me 1.0 speed on my Cel400@450 (dkutsanov) [Lame 384 -Z gave me 1.7 speed on my Cel400@450 (dkutsanov)] What was implemented in lame 3.8 so that the speed dropped so

[MP3 ENCODER] Re: Where did the VBR speed go?

RV To be clear, I don't mind, but am just curious: RV Lame 370 gave me 1.7 speed on my Cel400@450 (dkutsanov) RV Lame 383 gives me 1.0 speed on my Cel400@450 (dkutsanov) RV [Lame 384 -Z gave me 1.7 speed on my Cel400@450 (dkutsanov)] sorry should have been -Z : 0.7 speed :) -- Best regards,

Re: [MP3 ENCODER] Re: Where did the VBR speed go?

Roel VdB schrieb am Son, 21 Mai 2000: RV To be clear, I don't mind, but am just curious: RV Lame 370 gave me 1.7 speed on my Cel400@450 (dkutsanov) RV Lame 383 gives me 1.0 speed on my Cel400@450 (dkutsanov) RV [Lame 384 -Z gave me 1.7 speed on my Cel400@450 (dkutsanov)] sorry should have

Re: [MP3 ENCODER] Re: new scalefac_scale algorithm -Z - tested

Hello Takehiro, Sunday, May 21, 2000, 6:41:25 PM, you wrote: TT I wrote; I added a new scalefac_scale algorithm to CVS version of LAME, which enables with -Y option. TT Sorry, -Y option is used for Mark's new VBR routine TT so I changed "new scalefactor_scale algorithm" from -Y to -Z