A bug in curve calculation with huge target sizes?

[TripleA]

I have encountered a problem that seems to me like some sort of overflow problem:

I'm trying to make a 4 CD encode of a ~90 minute movie. Before anyone asks, no, it's not too much as it's 76.5% of 1st pass size. Anyway, I told XviD my target size of 2807254KB (~2.7GB) and ~5 hours later I had a 230856KB (~225MB) file. I retried this with several builds (Nic's March 23rd and 27th, uManiac's March 24th and 25th instant builds) and using regular and alternate curve routines.

I'm hoping someone can help...

RasEm Brsiq
P.S. I have DebugView logs of my last couple of attempts (using Nic's 27th), if anyone needs them, for some reason.
P.P.S. Speaking of which, wouldn't it be useful to include some sort of build identification in the debug output? Probably not in this case, but generally, I mean...

[The People's Elbow]

Which resolution you're encoding at??? 1024x768??? What movie is that hard to compress? I know really "bitches" that take much space, but your size seems a bit wrong, just too HUGE! Did you try another first pass? Maybe there something went wrong!
...by the way: 76,5% of 1st-pass is a waste of space, if you ask me - 60% should achieve almost the same quality and if you're not aware of using the DSFs capabilities I guess that even 45% will do very well!
That's just my opinion and I'm talking as a 1CD-Rip encoder...

PS: Your final filesize looks like you forgot to enter it properly, maybe one of the 7 numbers got lost :rolleyes:

- Elbow

[TripleA]

Sadly, there isn't much wrong with my math, OR with my number entry... I'm copying-and-pasting the whole thing :-)

The movie is "Bring it On". And I *am* encoding at a high resolution: 720x528. And it might be overkill for the particular movie. But that doesn't change the technical facts...

BTW, most of my encodes are 1 CDs as well, but this particular movie looks like s*** at that size, even at lower resolutions... Trust me, this is my 3rd encode of this movie. And my 90th movie, so I'm not a total newbie...

And here's a line from the DebugView log, take a look:

00000001 0.14911951 [1304] 2nd-pass: quant:31 H.263 intra stats1:4128 scaled:1 actual:4113 overflow:-4112 movie

I'm not sure, but I don't think anything should scale a frame to 1...

[Foxer]

Fixed.

It was the weirdest thing..
Not only did VC not use 64bit precision in the desired size kB to bytes calc but also in the movie & credits scales calcs..

[TripleA]

Thanks Foxer, it works now.

There were some slight problems where VDub crashed at the very end of the encoding session, but I believe those to have been caused by AVI limitations (what are those, anyway? I'd appreciate a link) rather than anything XviD-related. And I worked around that by using a segmented AVI.

All in all, I've learned quite a few new things with this encode. So XviD is *very* educational ;-)