View Full Version : Xvid 1.1 beta1 build 2005.03.05 -- 1st pass bug if cartoon mode enabled


Spyn
9th March 2005, 16:12
Hi,

When enabling cartoon mode on this release (2005.03.05), 1st pass end at XX % or don't scan any frame depending on the .d2v duration
result is same for two movies

.d2v is created using Dgindex 1.2.1

Avisynth version is 2.5.5

encoding with GKnot 0.35.0 (vdubmod 1.5.10.1)

Xvid 1.1 beta1 2005.03.05 : http://www.aziendeassociate.it/./cd///XviD.cvs.head.exe

----------------------

Xvid settings :
quarter pixel : checked
B-VOP : checked
max consecutive B-VOP : 2
quantizer ratio : 1.50
quantizer offset : 1.00
quantization type : H.263

Motion search precision : 6
VHQ : 1
use VHQ for bframes too : checked
use chroma motion checked : checked
frame drop ratio : 0
maximum I-Frame intervall : 250

quantization : 2-31 2-31 2-31
chroma optimizer enabled : checked
cartoon mode : checked

-----------------------

Gknot log :

15:57:08: Started Xvid - First Pass: H:\test.avs
15:57:36: Finished Xvid - First Pass: Duration: 28 seconds.
15:57:36: Trying to open Log-file.
15:57:36: Success: Log-file open.
15:57:36: Encoded: 0 Frames.
15:57:36: Speed: 0.000 Frames per Second.
15:57:36: WARNING: Number of counted frames differs from settings!
15:57:36: WARNING: Settings: 11038
15:57:36: WARNING: Counted: 0
15:57:36: WARNING: Difference: 11038
15:57:36: Correcting Bitrate...
15:57:36: Original Bitrate = 11879 k(=1000)Bits/s
15:57:36: Error: Correction impossible.
15:57:36: Now encoding at 11879 k(=1000)Bits/s
15:57:36: New target size = 640240 Kb

with cartoon mode unchecked :

15:58:20: Started Xvid - First Pass: H:\test.avs
16:05:15: Finished Xvid - First Pass: Duration: 6 minutes, 54 seconds.
16:05:15: Trying to open Log-file.
16:05:15: Success: Log-file open.
16:05:15: Encoded: 11037 Frames.
16:05:15: Speed: 26.605 Frames per Second.
16:05:15: New target size = 640240 Kb

no problem...

avs script :

LoadPlugin("C:\PROGRA~1\GORDIA~1\DGMPGDec\DGDecode.dll")
LoadPlugin("C:\PROGRA~1\GORDIA~1\AviSynthPlugins\UnDot.dll")
mpeg2source("H:\test.d2v")
crop(0,0,720,576)
LanczosResize(672,368)
Undot()

cartoon mode enabled :

complete Gknot log : http://naxxalite.free.fr/ripdvd/test_1_GKnot.log
stats file : http://naxxalite.free.fr/ripdvd/test_1.stats
first pass settings : http://naxxalite.free.fr/ripdvd/test_1_firstpass.settings
second pass settings : http://naxxalite.free.fr/ripdvd/test_1_secondpass.settings

cartoon mode disabled
complete Gknot log : http://naxxalite.free.fr/ripdvd/test_2_GKnot.log
stats file : http://naxxalite.free.fr/ripdvd/test_2.stats
first pass settings : http://naxxalite.free.fr/ripdvd/test_2_firstpass.settings
second pass settings : http://naxxalite.free.fr/ripdvd/test_2_secondpass.settings

Teegedeck
9th March 2005, 16:33
Hm, confirmed. VDub crashes during 1st pass only.

And - excellent bug report, Spyn.

squid_80
10th March 2005, 00:10
Is it the same as what Selur reported here: http://forum.doom9.org/showthread.php?s=&postid=620049#post620049 ? Does changing DGIndex's iDCT make a difference?

Leak
10th March 2005, 00:26
Originally posted by squid_80
Is it the same as what Selur reported here: http://forum.doom9.org/showthread.php?s=&postid=620049#post620049 ? Does changing DGIndex's iDCT make a difference?

Wouldn't the problem in the other thread suggest there's an emms instruction missing somewhere?

np: C.J. Bolland - Bones (Electronic Highway)

Teegedeck
10th March 2005, 02:39
BTW, Spyn, just do the first pass without cartoon mode for the time being.

CruNcher
10th March 2005, 03:35
the problem with the crash apeared after Michaels first fix for Cartoon Mode

ChronoCross
10th March 2005, 07:02
hmm I don't get an erro just using vdubmod without gknot....perhaps it'sa gknot error/

Spyn
10th March 2005, 11:55
vdub crash even by using it apart from gknot, I have just made the test.

edit : 16.01.2005 release don't get this bug

Spyn
17th March 2005, 14:09
2005.03.14 version got same bug :/

Isibaar
26th March 2005, 15:55
Is that bug report still valid? I simply cannot reproduce the fault. I have tested with uncompressed input and also with a mpeg2/avs source but there seems to be no problem.

I have to admit though that I didn't use Undot or LanczosResize. But, if it's a XviD problem, the crash should occur also without the filters and for all input types. Can anyone suggest a simple configuration (no avs input and without fancy filters at best) that crashes?

CruNcher
28th March 2005, 03:32
Ok i was testing a little more on this matter and this is the result

1.5.10.1 VdubMod XviD Cartoon Mode Crashtest
2366 crash
2389 crash
2407 crash
2424 crash different place
2439 crash
2496 crash (non official) different place

its moving from some builds to another location

http://cruncher.mufflastig.com/XviD/cartoonbug/cartoon-crash.avi
the sample is only crashing with cartoon mode enabled and builds 2424 and 2496 it's a ffv1 video out of the source


AVS2AVI v1.39x (c) 2002-2004:
Christophe Paris, David Leatherdale, int21h, Moitah
http://www.avs2avi.org/

Source:
* Filename: "E:\VIDEO_TS\sp2tr.avs"
* FourCC: YV12
* Frames: 19
* Resolution: 720x384
* Frame rate: 25.000 FPS
Compressor:
* Name: XviD MPEG-4 Codec
* FourCC: XVID
Destination:
* Filename: "E:\VIDEO_TS\j.avi"
* Pass 1/1: Frame 16/19, 0 B, 25.32 FPS, ETA 00:00:00
Press any key to continue . . .

crashed here

here is the crash happening

xvidcore.dll
0BF8D08F mov esi,dword ptr [ebx*8+0BFF48C0h]

Edit: changed my compiler flags (microsoft) now and it seems to be stable for this sequence now with all vdubmod builds and avs2avi i have to test full 2pass things first to be absolute sure

CruNcher
29th March 2005, 22:01
after preventing Isibaars Fix to crash by changeing compiler flags

http://cruncher.mufflastig.com/XviD/cartoonbug/cbug.avi

squid_80
30th March 2005, 00:32
Any hints what those compiler flags might be so we know what to avoid?

Isibaar
30th March 2005, 14:40
CruNcher, can you post the exact XviD encoder settings you were using? I've tried with pretty much everthing turned on (B-frames, qpel, GMC + VHQ) and it's not crashing. Also, your first sample looks ok if encoded with cartoon mode.

I don't have the source for your second sample so I can't check. But for sure, it looks rather nasty. However, I also experienced ugly artifacts with MS VC++ 6 for some sequences (even with latest service pack and processor pack) some time ago. If compiled with gcc or Intel compiler, there was no problem. So probably this is a compiler bug after all?

CruNcher
30th March 2005, 15:41
Ok so i used Virtualdub 1.6.4 latest

Settings for every build where Fast1pass Output non discarded, bvops off, aq off,qpel off,fast qpel off, chroma motion off,bvhq off, vhq off,trellis off so basicly everything OFF except Cartoon Mode here are the results and the source

Source
http://cruncher.mufflastig.com/XviD/cartoonbug/source-cbug.avi


CelticDruids CVS Build
http://www.aziendeassociate.it/cd///XviD.cvs.head.exe
result = http://cruncher.mufflastig.com/XviD/cartoonbug/cds_build.avi

Koepis 1.1beta1 Build
http://www.koepi.org/
result = http://cruncher.mufflastig.com/XviD/cartoonbug/koepis_build.avi

same results for my GCC(mingw) and VS6 CVS build as with celticdruids

Koepis build is almost 100% ok but frame 38 shows problems too

Isibaar
31st March 2005, 23:18
I've committed a fix for the problem. It doesn't qualify as a compiler bug - rather, it was my fault after all. :(

Thanks, CruNcher, for pointing this out and providing the very valuable test sequences! :)

neo_anderson
10th April 2005, 15:20
Press any key to continue . . .

crashed here
[/CODE]
here is the crash happening

xvidcore.dll
0BF8D08F mov esi,dword ptr [ebx*8+0BFF48C0h]

Edit: changed my compiler flags (microsoft) now and it seems to be stable for this sequence now with all vdubmod builds and avs2avi i have to test full 2pass things first to be absolute sure [/B][/QUOTE]

hi, i am having xvid crashes at first pass if trellis is enabled, and if it is disable, it crashes at 2nd pass, u say u changed compiler flags, how to do this to prevent crash?

Koepi
10th April 2005, 15:31
neo andersen,

just because you don't like the answer you got for your first question to that issue you're experiencing it doesn't mean that you should go on and pollute other threads with that issue again.

Your issue is hardware or software related, it is limited to your system, and to your system alone. So please consider what you got as answers until now and make absolutely sure that those aren't the problems _before_ you go on nagging about it, please - pretty please.

Cheers
Koepi