Log in

View Full Version : Xvid 1.1b very big over-size file


Magno
27th January 2005, 14:39
I have done my first encode using Xvid 1.1 coding a 96 secs sample from a movie at 700 Kbits/secs (two-pass) getting a surprising 44 megs file (96 x 700 / 8 = 8400 Kbytes) ang GSpot reports 3080 Kbits/seg. Amazed, I decided to reencode it at 600 Kbits/seg keeping the parameters and i got a file wheighting 16 megs. I can't start a thing about that enormous oversize. Would you mind explaining what could be possibly my mistake?

Xvid 1.1 configuration:

H.263 quantizer matrix
Adaptative Quantization
2 BVOPs at 1.5 / 1.0

Chroma optimizer enabled

Motion Search Precision 6
VHQ mode 4
VHQ for BFrames too
Use chroma motion
Turbo

Maximum I-frame interval: 250

Trellis quantization OFF

Sharktooth
27th January 2005, 14:40
Have you uninstalled ANY previous versions of Xvid before installing 1.1beta1?

Magno
27th January 2005, 14:50
Yes. Actually, this was the first time I unistalled a previous version of XVid before installing the new one. :(

Koepi
27th January 2005, 15:46
If that 96sec sample is 1920x1080 and always from frame to frame flashing in different colours, this might well be that even with all-i-frames-at-quant32 the file still gets that huge ;-)

I think you should recheck that you didn't mistake kbits for kbytes a.s.o. (clicking the kbytes button makes it become kbits and vice versa).

Cheers
Koepi

Magno
27th January 2005, 15:55
The sample is a piece from LOTR The Return of the King Extra DVD 2 at 512x280, so that can't be the problem.

And the target bitrate is measured in kbps and so is the quantity I introduced: 600 Kbps.

And moreoever, i have encoded almos 4 hours of video from the rest of the DVD with Xvid 1.1 and all are oversized: 4 Gigs using a "Target bitrate" of 700 Kbps, and last week i encoded the first extra DVD usign Xvid 1.0.3 (4 hours too) at 512x280 and "Target Bitrate = 800 Kbps" obteining a final file of 2,5 Gigs... That's a 65% of oversized, even with a lower target bitrate.

Do you want the first pass log for debugging?

Didée
27th January 2005, 16:16
Perhaps:

- the (only) zone accidentially is set to use a fixed quantizer, probably "2"

- the reference to the *.pass file is incorrect. If the *.pass isn't found when starting the 2nd pass, XviD will encode everything @ quant 2 (iirc)

What is the encoding status window showing during the 2nd pass? What quantizers are used?

Magno
27th January 2005, 18:41
- the only zone is set to use a weight factor of 1
- the *.pass is properly referenced

I think this is a polstergeist problem :D

As for the encoding status windows, although the option is checked, it doesn't appear, so i don't know the quantizers...
BTW, "I-frame boost" is set to 10% and all other optins in that property page are set to defaults.

Magno
28th January 2005, 02:32
It seems to be a problem with the front-end I use to encode, which changed the bitrate settings without my permission with Xvid 1.1 but it was working propely with 1.0.3.

So finally, it's nothing to do about the codec. Sorry about the inconvenience. :D

b0b0b0b
28th January 2005, 07:31
which front end? Thanks

Didée
28th January 2005, 09:01
Originally posted by Magno
As for the encoding status windows, although the option is checked, it doesn't appear, so i don't know the quantizers...
That's a sure sign that something is screwed up. (German: "Da ist der Wurm drin...")

Magno
28th January 2005, 15:39
The front end was "ARCalculator", a pretty good spanish program for use with Xvid, which optimizes AVS scripts splitting the movie into arbitrary chunks applying different resize filters in each of them to achieve the best overall compresibility.

DarkDudae
31st January 2005, 12:03
ARCalculator should work perfectly with XviD 1.1 since it only changes the filesize and target type (size or bitrate) in the codec settings. It should work at the same way that 1.0.3. (At least in my computer, I have not problem)

Greetings