XviD-14112002-1...

[Koepi]

sysKin is sending me a fix right now, a new build will be up soon...

regards
koepi

[sysKin]

Originally posted by Koepi
sysKin is sending me a fix right now, a new build will be up soon...
This sounds so good. Let me write it in other words:
sysKin just removed all functions which caused known problems. Encoding will be slower, because one of the functions was supposed to increase speed without changing anything (but it changed).

Encoding will be worse, because one of four macroblock modes is disabled. It didn't work correctly anyway.
DO NOT use this bulid for non-qpel, because this mode will still be disabled and encoding will suck.

But anyway, thanks for the kind words, like "fix". LOL. :D

Have fun testing,
Radek

[Koepi]

New build up, with interpolate mode switched off... ;)

Regards
Koepi

[Trahald]

well.. i guess this is the exciting world of using unstable builds.. lol

great job addressing the issues so quickly, guys

i did an encode with the 16112002 build (just b-frames and lumi) and it came out great (decoded with nics ds filter )

guess i'll try a gmc - bframes encode tonight with teh new build

[JimiK]

Sorry guys, just have to ask now. sysKin wrote that encodes will be worse. Does that apply to every setting, even with qpel? Koepi wrote at his site "do not use without qpel". If you want to encode with bframes, but without qpel, you better use the 1811-1, or the 1611 build? Is this a "only if you really like bframes and qpel and want to use them together, even though there could be a quality decrease"-build?

Best regards,
JimiK

[sysKin]

Originally posted by JimiK
[B]Sorry guys, just have to ask now. sysKin wrote that encodes will be worse. Does that apply to every setting, even with qpel? Koepi wrote at his site "do not use without qpel". If you want to encode with bframes, but without qpel, you better use the 1811-1, or the 1611 build?In this highly-experimental build, b-frames's quality will be worse (or more precise: they will be bigger at the same quality) then it should be. For non-qpel, use 'normal' builds where quality is not impared. For qpel, you don't have much choice ;)Is this a "only if you really like bframes and qpel and want to use them together, even though there could be a quality decrease"-build?
Well yes, exactly. Qpel+bframes in _this_ bulid already give better quality then only qpel or only bframes, but are absolutely sub optimal. Only for testing - but if you encode anything it's ok, you make a valid movie.

[iago]

Well, that sounds interesting ;). I'll start a fresh two pass now with "b-frames + qpel" using Koepi's new 18112002-2 build.

@sysKin and Koepi,

Thanks for all your great work!

best regards,
iago

[drebel]

Internal CVS changes are affecting Avisynth?

Using latest Koepi's compilations(16/11 and 18/11-1)i came across the following phenomenon;it's been more than a year that i'm using VirtualDub jobs to encode only a portion of the movie to check the final(more or less) result.That means i'm aborting first pass after ~3000 frames which leaves VDuB job to perform the second pass UNTIL that frame comes(causing an internal avisynth error and VDub to stop because of "possible data corruption"...
During the latest two builds,i noticed somethind strange:VirtualDub keeps encoding for the second pass AFTER the certain frame(and after more than 1000 frames-i dont really know if it completes the 2nd pass).Image visual quality of the encoded part is not bad ,but it seems to me that i get more compression artifacts AFTER that frame.
I've passed to YV12 lately,using all the required stuff from the Avisynth Faq with no probs fo far except for this one.To avoid the problem,i changed almost EVERY Xvid option(except lumi and interlaced),with the same NON FATAL result for VirtualDubMod.Only when changing back to Koepi's 14/11 i saw the usual response.(it's not a script prob,avs is fine with Avisynth 2.5 11/11)
Does anybody have any ideas?Am i missing anything critical here?Could anyone else confirm this?What's been feeding the 2nd pass if stats file from the uncomplete 1st pass contains data up to that frame...?

thanks in advance,
george

[AndyP]

I might be missing the point, but have you tried using trim in the script. Relying on errors and aborting things seems a little risky.....

Kind Regards,
Andy

[unplugged]

It's just a sensation, it seems that after these modifications even the little smearing visible with non xvid-ax decoder (ffdshow...) is *ENTIRELY* gone...

:D ?

[vinks]

been testing out this qpel stuff on this new build dated as of today on "The Test" the dvd single by the chemical bros (lots of varying scenes its a difficult enough clip to encode)

and it came out much "sharper" and more detailed than with out, didn't have any problems on playback either in xvid or ffdshow, here are the details...

--
Quantizers Analisis
---------------------

Quantizers Used For Movie :
------------------------------
Quant 2 Used : 3 Times, Percentage Used : 0.03%
Quant 3 Used : 4095 Times, Percentage Used : 44.89%
Quant 4 Used : 4827 Times, Percentage Used : 52.92%
Quant 5 Used : 190 Times, Percentage Used : 2.08%
Quant 6 Used : 7 Times, Percentage Used : 0.08%

Average Quantizer Used for Movie : 3.573

No credits encoding!!

H.263 Quantization Type Used 9122 timed, Percentage Used : 100.00%

Quantizers prevented from rising too steeply 2 times


Intra-Frame (Key-Frame) Quantizers
------------------------------------

Movie
-------
Quant 2 Used : 3 Times, Percentage Used : 1.89%
Quant 3 Used : 156 Times, Percentage Used : 98.11%

No credits encoding!!

Inter-Frame (P-Frame) Quantizers
------------------------------------

Movie
-------
Quant 3 Used : 3939 Times, Percentage Used : 43.95%
Quant 4 Used : 4827 Times, Percentage Used : 53.85%
Quant 5 Used : 190 Times, Percentage Used : 2.12%
Quant 6 Used : 7 Times, Percentage Used : 0.08%

No credits encoding!!



Frame Analisis
----------------

Number Of Intra-Frames (Key-Frames) : 159
Number Of Inter-Frames (P-Frames) : 8963
Total Number Of Frames : 9122

1.74% of the Movie is Intra-Frames (Key-Frames)
98.26% of the Movie is Inter-Frames (P-Frames)



Size Analysis
----------------

1-Pass Size : 77402458 Bytes or 75588 KBytes or 73 MBytes
Scaled Size : 41132481 Bytes or 40168 KBytes or 39 MBytes
Actual Size : 41126360 Bytes or 40162 KBytes or 39 MBytes

Usefull Statistics
------------------
Compressibility : 53.13%
Relative Quality of XviD avi : 55.98%
Absolute Quality of XviD avi : 95.28%
--

used the following avs file

--
LoadPlugin("C:\PROGRA~1\GORDIA~1\MPEG2dec3.dll")
LoadPlugin("C:\PROGRA~1\GORDIA~1\undot.dll")
mpeg2source("C:\divx\the_test\work\the_test.d2v",idct=5)
crop(0,70,718,436)
undot()
LanczosResize(608,336)
--

i shall have to try it with bframes later on and see how it all goes.

nifty work people. keep it up.

note: oh yea playback with ffdshow-20021113 seemed to be better than xvid. xvid blured things a little, ffdshow seem to "degrade" the quality of the clip till the next keyframe comes about, i think this is a known issue?.

[drebel]

@Andy
thanks for the quick reply.
So,here's the script to avoid misunderstanding(BTW i didnt change avisynth version : 2.5 , 11/11)


LoadPlugin("C:\Program Files\Avisynth2.5\MPEG2Dec3.dll")
#LoadPlugin("C:\Program Files\Avisynth2.5\TomsMoComp.dll")
LoadPlugin("C:\Program Files\Avisynth2.5\UnDot.dll")
#LoadPlugin("C:\Program Files\Avisynth2.5\UnFilter.dll")
#LoadPlugin("C:\Program Files\Avisynth2.5\Convolution3DYV12.dll")
#LoadPlugin("C:\Program Files\Avisynth2.5\Focus2.dll")
LoadPlugin("C:\Program Files\Avisynth2.5\FluxSmooth-2.5.dll")
clip=mpeg2source("D:\Movies\Time\time.d2v",cpu2="ooooxx")
Part1=trim(clip,0,1277)
Part2=trim(clip,1278,130300)
Part3=trim(clip,130301,0)
Start=Part1.crop(0,75,720,424).LumaFilter(-3,1).BilinearResize(672,272).FluxSmooth(0,5)
Movie=Part2.crop(0,75,720,424).LumaFilter(-3,1).Undot().LanczosResize(672,272)
Credits=Part3.crop(0,75,720,424).LumaFilter(-3,1).BilinearResize(672,272).FluxSmooth(0,5)
Return Start+Movie+Credits

I always use trim,but for another reason....
I'm only concerned if something 's changed inside curve compression treatment to cause such a difference

have fun with xvid,
george

[vinks]

this might be a bit pointless, since my copy of xvid analyser is old and out of date, (same settings as above post, but bframes and qpel turned on)


--
XviD Analyzer v0.14 by MoonWalker & MarcFD
e-mails : s_ilias@gmx.net & marc.fd@libertysurf.fr


Quantizers Analisis
---------------------

Quantizers Used For Movie :
------------------------------
Quant 2 Used : 39 Times, Percentage Used : 1.07%
Quant 3 Used : 2460 Times, Percentage Used : 67.60%
Quant 4 Used : 1085 Times, Percentage Used : 29.82%
Quant 5 Used : 50 Times, Percentage Used : 1.37%
Quant 6 Used : 3 Times, Percentage Used : 0.08%
Quant 7 Used : 2 Times, Percentage Used : 0.05%

Average Quantizer Used for Movie : 3.320

Quantizers Used For Credits :
--------------------------------
Quant 2 Used : 104 Times.
Quant 3 Used : 4247 Times.
Quant 4 Used : 1089 Times.
Quant 5 Used : 33 Times.
Quant 6 Used : 5 Times.
Quant 7 Used : 2 Times.
Quant 8 Used : 3 Times.

H.263 Quantization Type Used 9122 timed, Percentage Used : 100.00%

Quantizers prevented from rising too steeply 15 times


Intra-Frame (Key-Frame) Quantizers
------------------------------------

Movie
-------
Quant 2 Used : 8 Times, Percentage Used : 0.14%
Quant 3 Used : 412 Times, Percentage Used : 6.97%
Quant 4 Used : 11 Times, Percentage Used : 0.19%

Credits
---------
Quant 2 Used : 104 Times, Percentage Used : 1.76%
Quant 3 Used : 4247 Times, Percentage Used : 71.81%
Quant 4 Used : 1089 Times, Percentage Used : 18.41%
Quant 5 Used : 33 Times, Percentage Used : 0.56%
Quant 6 Used : 5 Times, Percentage Used : 0.08%
Quant 7 Used : 2 Times, Percentage Used : 0.03%
Quant 8 Used : 3 Times, Percentage Used : 0.05%

Inter-Frame (P-Frame) Quantizers
------------------------------------

Movie
-------
Quant 2 Used : 31 Times, Percentage Used : 0.97%
Quant 3 Used : 2048 Times, Percentage Used : 63.84%
Quant 4 Used : 1074 Times, Percentage Used : 33.48%
Quant 5 Used : 50 Times, Percentage Used : 1.56%
Quant 6 Used : 3 Times, Percentage Used : 0.09%
Quant 7 Used : 2 Times, Percentage Used : 0.06%

Credits
---------



Frame Analisis
----------------

Number Of Intra-Frames (Key-Frames) : 5914
Number Of Inter-Frames (P-Frames) : 3208
Total Number Of Frames : 9122

64.83% of the Movie is Intra-Frames (Key-Frames)
35.17% of the Movie is Inter-Frames (P-Frames)



Size Analysis
----------------

1-Pass Size : 51519504 Bytes or 50312 KBytes or 49 MBytes
Scaled Size : 31518312 Bytes or 30779 KBytes or 30 MBytes
Actual Size : 28715821 Bytes or 28042 KBytes or 27 MBytes

Usefull Statistics
------------------
Compressibility : 55.74%
Relative Quality of XviD avi : 60.25%
Absolute Quality of XviD avi : 96.04%
--

i did notice though that there were quite a few intra frames used consequtively, even though i set the min iframes to 10. i wont comment on the quality though.

bframes were set to 3, 150%

[AndyP]

Hi drebel,

I'm certainly no expert but as the second pass is going on beyond the first pass end is it not bound to look bad as the first pass info is not available for the curve compression etc.. to use. Now why it allows itself to carry on is another matter (I honestly have no idea). It's as you say what is feeding the second pass...

Kind Regards,
Andy

[NoLogo]

Originally posted by vinks
i did notice though that there were quite a few intra frames used consequtively, even though i set the min iframes to 10. i wont comment on the quality though.


I have noticed that point too, and it seems quite odd to me...

I've done some tests using the 16/11/02 build by Koepi, with a short part of Ghost Dog (2'20, frames 112000 to 115546), composed with slow- and low-motion scenes, with the following tuning:

Duration: 2'20
Size: 11000ko (about 700kbs)
MSP: 6
Quant. type: H263/New mod. HQ
Max I-frames interval: 300
Min I-frames interval: 9
Lumi: off
Interlacing: off
Qpel: off
Packed bitstream: on
DX50 B-VOP compatibility: on

Then:
BF(2/150)
BF(3/150)
BF(2/200)
BF(3/200)
GMC only
Chroma motion only
BF(2/150)+GMC

that is to say 7 encodings.

Using DebugView and XviD Analyzer, I obtained the results for each encode, and it's quite dissapointing: using BF, 90% of the movie is KF (despite the fact i chose "Min I-frames interval=9), whereas without them, it's pretty normal, only 5-10% of the frames are KF.
Nevertheless, the quality is better with BF, with an average Quantizer=2.2 (2.8 without BF), and the compressibility grows as well (110% against 65%). Moreover, I can see that H263 is never used, whereas it was with the same tunings with older builds.

Here one analysis with BF:

Quantizers Analisis
---------------------

Quantizers Used For Movie :
------------------------------
Quant 2 Used : 85 Times, Percentage Used : 76.58%
Quant 3 Used : 26 Times, Percentage Used : 23.42%

Average Quantizer Used for Movie : 2.234

Quantizers Used For Credits :
--------------------------------
Quant 2 Used : 2785 Times.
Quant 3 Used : 651 Times.
Quant 4 Used : 3 Times.

MPEG Quantization Type Used 3550 timed, Percentage Used : 100.00%

No prevention happened

Intra-Frame (Key-Frame) Quantizers
------------------------------------

Movie
-------
Quant 2 Used : 27 Times, Percentage Used : 0.78%

Credits
---------
Quant 2 Used : 2785 Times, Percentage Used : 80.35%
Quant 3 Used : 651 Times, Percentage Used : 18.78%
Quant 4 Used : 3 Times, Percentage Used : 0.09%

Inter-Frame (P-Frame) Quantizers
------------------------------------

Movie
-------
Quant 2 Used : 58 Times, Percentage Used : 69.05%
Quant 3 Used : 26 Times, Percentage Used : 30.95%

Credits
---------
Frame Analisis
----------------

Number Of Intra-Frames (Key-Frames) : 3466
Number Of Inter-Frames (P-Frames) : 84
Total Number Of Frames : 3550

97.63% of the Movie is Intra-Frames (Key-Frames)
2.37% of the Movie is Inter-Frames (P-Frames)

Size Analysis
----------------

1-Pass Size : 1047751 Bytes or 1023 KBytes or 0 MBytes
Scaled Size : 864864 Bytes or 844 KBytes or 0 MBytes
Actual Size : 1099778 Bytes or 1074 KBytes or 1 MBytes
Actual Size of Avi File without Sound : 1193984 Bytes or 1166 KBytes or 1 MBytes

Usefull Statistics
------------------
Compressibility : 104.97%
Relative Quality of XviD avi : 89.52%
Absolute Quality of XviD avi : 99.30%

When i try to read the vids, I always got the same result: the decoding is quite jerky (using either Nic's DShow filter or FFDShow), as if I got 25fps then 10, then 25 again. I have only 30-40% CPU load, so I think it has nothing to do with this. But the quality is perfect, considering the birate i had, XviD's BF are lot better than DviX's ones.

I have tried later with the new build (18/11/02-2), without "packed bitstream" and "DX50 B-VOP compatibility" and it's exactly the same.

So my question is: does it come from what i did (e.g. BF and New Mod HQ), or is it something that was changed in the build ?

Hope my problem may help (or maybe I'm just an idiot...).

NoLogo

PS: XviD is getting better and better, thanx to all developpers.
PPS: sorry for the long post :).

[MaTTeR]

Originally posted by NoLogo
XviD's BF are lot better than DviX's ones. I have to say I was never much of enthusiast of B-Frames until seeing some recent tests myself. Admittingly it was because I was use to seeing the (blurred)implementation of DivX 5.x. However, my recent tests on some 4:3 films made a true believer out of me! The quality is indeed outstanding to say the least with these latest builds, I still prefer Koepi's 09112002 build myself.

A big thanks from me to all the developers and contributors. I never doubted for a moment the implementation would be greater than that of a commercial codec(no names mentioned):D

Edit- I should have mentioned B-Frames play perfectly smooth for me using a 10-10-2002 build of ffdshow decoding with libavcodec.

[NoLogo]

Originally posted by MaTTeR
I should have mentioned B-Frames play perfectly smooth for me using a 10-10-2002 build of ffdshow decoding with libavcodec.

Booooooh... why not by me ?... :(
And i suppose you have no problems with I-frames ?
Whatever, maybe i should try some older builds. Thanx for the advice.

NoLogo

[scorchED]

when i am using koepis built 14112002 then i get a very nice result of every encoding. i tested only first pass with all standart parameter and MSP: 6-Ultra High, QT: H263, b-frames: 2@150, chroma motion enabled. the encodet movies (res 640x352) are clean and without any jerky playback by using ffdshow 20021113.
this built is my reference built now:)
i also tried koepis built 18112002 with the same settings (and qpel+bframes enabled), but i don't like the results i get. you have to enable q-pel with b-frames and you get a movie with some smearing effects in high and slow motion scenes. you get some sharper frames too, but the smearing is too much. also there is a lot of backround noise in slow motion areas. (in the source isn't any noise, because i use a very efficient filter chain to eleminate all noise.)

[lighty]

Just finished encode with Koepi's build 18112002-2 and used QPel+GMC+B-frame3/200+NewModHQ.

Everything plays fine without any sound desync (so B frames are then working as they suppose to?) with FFD show. It reports Bframes, QPel and GMC used. XviD decoder however plays in "slow motion".

I am VERY happy with this build it is obviously a step in the right direction.:D

[iago]

Hello all,

After some short tests and especially after a full two-pass encode of a 2+ hr. and hard to compress movie with "b-frames 5/200 + qpel + gmc" using the 18112002-2 build from Koepi, together with UnFilter(-10,-10) in the script, I must admit that I'm quite surprised to get such good results! ;) Also, no decoding problems with the latest ffdshow - libavcodec, dated 13/11.

The giant steps being taken in XviD development recently are absolutely great; and XviD is, without any doubt, "the" codec at the moment!

Thanks again to all the developers for all their effort!

best regards,
iago

[neo_sapien]

Originally posted by scorchED
when i am using koepis built 14112002 then i get a very nice result of every encoding. i tested only first pass with all standart parameter and MSP: 6-Ultra High, QT: H263, b-frames: 2@150, chroma motion enabled. the encodet movies (res 640x352) are clean and without any jerky playback by using ffdshow 20021113.
this built is my reference built now:)
i also tried koepis built 18112002 with the same settings (and qpel+bframes enabled), but i don't like the results i get. you have to enable q-pel with b-frames and you get a movie with some smearing effects in high and slow motion scenes. you get some sharper frames too, but the smearing is too much. also there is a lot of backround noise in slow motion areas. (in the source isn't any noise, because i use a very efficient filter chain to eleminate all noise.)

I concur. I did a 30 second low motion sample of Star Trek TNG 220 Cost of Living at 1-pass quant 3, and it amplified the noise present in the source. The first thing I'm thinking is really, really really high motion search precision.

Settings for XviD (11/18/2002 8:32:34 AM)
Mode: 1 Pass - quantizer, Quantizer: 3
Motion Search Precision: 6 - Ultra
Quantization Type: H.263
FourCC Used: XVID
Max I-frame Interval: 240, Min I-frame Interval: 5
Lumimasking: OFF
Interlacing: OFF
Greyscale: OFF
Use Chroma Motion-ON
Global Motion Compensation-ON
Quarterpel-ON
Max B-frames: 2
B-frames Quantizer Ratio: 200%
Packed Bitstream: OFF
DX50 B-VOP Compatibility: ON
Print debug info on each frame: OFF
Min I-frame Quantizer: 2, Max I-frame Quantizer: 2
Min P-frame Quantizer: 2, Max P-frame Quantizer: 16
Max Bitrate: 10000kbps, Max Overflow Improvement: 60%, Max Overflow Degradation: 60%
Start Credits: OFF, End Credits: OFF,



AVS Script:
SetMemoryMax(40)
LoadPlugin("D:\PROGRA~1\GORDIA~1\mpeg2dec.dll")
LoadPlugin("D:\PROGRA~1\GORDIA~1\decomb.dll")
mpeg2source("H:\DivX\Unfinished DivX\Season 5 Disc 5\PROCESSING\sample.d2v")
Telecide(guide=1,firstlast=true,gthresh=10,post=true)
Decimate(mode=2,cycle=5,quality=3,threshold2=2.0)
crop(13,0,701,478)
BicubicResize(576,432,0,0.5)

Attached is a screen of the AVS and a screen of the XviD. Attachment is pending mod confirmation. Images had to be saved in JPEG at Quality 94 in Adobe PS 5.5 because max attachment size is 204kb, so no PNG.

[MaTTeR]

scorchED,

Do you see the smearing with Qpel disabled? I've noticed B-Frames does seem to leave motion trails around small movement in darker scenss. It almost reminds me of the problem I seen with Qpel some weeks back.

NoLogo,

No I had no cosecutive I-Frames and I reproduced your problem last night. I set ffdshow to decode with XviD instead of libavcodec and the playback was very choppy and sometimes in slow motion.I switched back to libavcodec on the PIII 850 and it played the frames perfectly.

[NuclearFusi0n]

I got a small amount of shitframes when I encoded run lola run with 11/18, with ffdshow 11/13, but when I open it in virtualdub, there are no shitframes, and when i disable ffdshow and open it in windows media player 6.4, the entire movie is garbled

:confused:

edit: the entire movies looks excellent except for some light smearing at parts :(

settings:

Mode: 2 Pass
Motion Search Precision: 6 - Ultra
Quantization Type: MPEG for both passes
FourCC Used: XVID
Max I-frame Interval: 300, Min I-frame Interval: 1
Lumimasking: OFF
Interlacing: OFF
Greyscale: OFF
Use Chroma Motion: OFF
Global Motion Compensation: ON
Quarterpel: ON
Max B-frames: 2
B-frames Quantizer Ratio: 125%
Packed Bitstream: OFF
DX50 B-VOP Compatibility: ON
Print debug info on each frame: OFF
Min I-frame Quantizer: 2, Max I-frame Quantizer: 4
Min P-frame Quantizer: 2, Max P-frame Quantizer: 16
Max Bitrate: 10000kbps, Max Overflow Improvement: 60%, Max Overflow Degradation: 60%

Curve was linear, no iframe boost, 0% for high bitrate scenes, 0% for low, 250 bitrate payback delay, and payback proportionally

edit: found another area with heavy shit, and when opened in virtualdub, it's totally clean

[Pasqui]

@NoLogo
I guess XviD Analyzer does not support yet B Frames. That's why you get such a high amount of "keyframes" (in fact real keyframes + B Frames).
BTW, in all my tests, checking Packed bitstream always resulted in a jerky playback. Just unticking it and activating DX50 BVop Compatibility always resulted in a perfectly smooth playback.

[NoLogo]

Yeah, since Matter told me he had no problem with an older Build of libavdec, I tried the 9/27/02, and i have to say it seems to look better (but maybe I managed to convince myself there is a problem, and now I can't believe it's OK). But I have re-thought about all this stuff, and I have the same conclusion: maybe XviD analyzer is not B-frames compliant...
Whatever, I have launched a pretty long encode (still 10 hours), with a whole movie (Ghost Dog, again :)), I'll see tomorrow what it looks like. I keep my finger crossed (not easy to type).
Thanx for all.

NoLogo

PS: does anybody know if Nic has planned to make anew DShow filter ?

[scorchED]

@Matter
i only get smearing effects on all movements when i used the 18112002built from koepi with q-pel enabled. without q-pel and with the 14112002built everything is very fine. i encodet the same movie with the same script and other parameters two times.

[Koepi]

XviD-20112002-1:
- Fresh CVS checkout. Plenty bugfixes and additions...

Short summary:

- bframes: interpolated prediction mode works again
- major slowdown when using bframes, qpel, gmc, chroma me together ;)
- some more bugfixes in the ME according to sysKin
- the rest I've forgotten - sysKin is sure to have introduced some new bugs ;)

Enjoy testing the new build,

best regards
Koepi

[Koepi]

Hm. For me, the code crashed again. If that happens, try disabling "Integer SSE" in the debug-panel of xvid and try again.

Regards
Koepi

[HarryM]

I use only q-pel.
Other special features are possible buggy for me.

[celeron]

Hi 1º post :)
I have test the today Keopi build and it rocks i dont have no prob now whit this new one, i have made a short encode(250mb vob from Perfect storm) and realy it looks great.
I only have test it whit Bframes 3/150 and chroma motion, even the final size have drop from 32.3mb too 31.2mb.
And now i can decode the clip even whit the xvid.ax whitout the clip being in slow motion.

@Keopi
No crash in here i have done 2-pass, i dont have need it too dissable the "Integer SSE" :)(Win2k+SP3 and Duron Morgan 1.2Ghz)

Thks for your hard work guys ;)

PS: sorry very bad english :)

[Koepi]

That crash only occurs very seldom (and somewhat randomly) when using qpel+bframes (and there it's exactly located within "bframe interpolate qpel search").

I'm using the old duron700, no real SSE in there - but it's more likely that a vriable/pointer gets messed up, but strange enough this behaviour changes if I disable XMM (integer SSE).

Just to clear that up :)

Best regards,
Koepi

PS: welcome aboard, celeron!

[cult]

true true!now we can check use xvid in ffdshow without slowmotion fx.And what a quality that is!
Thanx all-lets do the happy dance

[celeron]

Thks Keopi its nice 2 be here :)

I have made again another short encode whit 02112002-1(same source as my previus post) this time whit Bframes-3/150+Qpel+chroma motion.
Cunclusion no crash but the quality its very bad.
For me only whit Bframes and chroma motion the quality its great.

PS: Bframe+qpel decoding only work whit ffdshow if i try to open in virtualdub or open whit xvid.ax it just crash the xvid.dll.

Thks :)

[NuclearFusi0n]

i crash with MMX, SSE, 3Dnow, and 3dNow2 enabled, Integer SSE, and SSE2 disabled
AMD Athlon XP 2000+

when running with only SSE, 3dnow and 3dnow2 enabled, i have 8 hours left in my firstpass! :(

I need to stop MMX and Integer SSE to be stable. I don't know wether that is causing the slowdown, or whether it's the QPel + BFrame issue.

[Pasqui]

So as to encode a movie with BFrames + QPel on my AMD Athlon 500, I have to disable MMX otherwise I get a crash.

[Gaia]

No crashes with Duron 950. I didn't disable anything but i used only b-frames, no QPel or GMC.

[tiki4]

Just a short question:

Is it now safe again to use the latest build of Koepi without QPel? The build from 1811 was said to be 'QPel only'.

Regards,

tiki4

[drebel]

Encoding+decoding probs here ...

Only by disabling MMX,int.SSE,3Dnow2! i can avoid crashes, with severe speed penalty which drops my Duron 1 GHZ to ~2 fps.

The decoding problem appears as huge black pixels aroung moving edges(no choppy playback though)and crashes ZoomPlayer 2.90 after a while.

All that with Qpel+GMC+Bframes enabled.Waiting a little longer(for other compilations) is definetely NOT a problem...;)

Should we switch back to 14/11 or this one will do the trick,as Tiki4 suggested ?

regards,
george

[Gaia]

I can confirm that if you use just b-frames everything works just fine. No crashing. I haven't tried QPel or GMC.

[glenn]

Perhaps it's worth giving it another go now;

20.11.2002 15:40:
U xvidcore/src/motion/motion_est.c (rev.1.44.) syskin:
- all qpel code rewritten
U xvidcore/src/motion/motion_est.h (rev.1.1.2) syskin:
- all qpel code rewritten

20.11.2002 20:20:
U xvidcore/src/decoder.c (rev.1.37.) Isibaar:
- bframe+qpel decoding support, bframe decoding bugfix, qpel interpolation speedup, bframe decoding speedup
U xvidcore/src/xvid.c (rev.1.33.) Isibaar:
- bframe+qpel decoding support, bframe decoding bugfix, qpel interpolation speedup, bframe decoding speedup
U xvidcore/src/image/interpolate8x8.c (rev.1.4.2) Isibaar:
- bframe+qpel decoding support, bframe decoding bugfix, qpel interpolation speedup, bframe decoding speedup
U xvidcore/src/image/interpolate8x8.h (rev.1.5.2) Isibaar:
- correct interpolate8x8_avg2 calls
U xvidcore/src/image/x86_asm/interpolate8x8_mmx.asm (rev.1.8.2) Isibaar:
- bframe+qpel decoding support, bframe decoding bugfix, qpel interpolation speedup, bframe decoding speedup
U xvidcore/src/motion/motion_est.c (rev.1.44.) Isibaar:
- bframe+qpel decoding support, bframe decoding bugfix, qpel interpolation speedup, bframe decoding speedup

I'm not at home, so I can't test, but... anyone else?

[MaTTeR]

Ran several tests with B-Frames alone and then with GMC and all worked perfectly, no crashes or artifacts.

Edit- Actually I did notice that scene changes seem to "flash" instead of being seemless now. I had never seen that happen before but it happens with B-Frames @ 2/150.

[iago]

Imho, latest developer build, XviD.Alpha.20.11.2002.2300.exe from uManiac's site, is absolutely great in terms of both quality and decoding! :)

After several tests with "b-frames 4/150/150", "b-frames 4/200/200", and "b-frames 4/200/200 + qpel" I started a full two pass encode of a rather difficult 121 min. movie with only "b-frames 4/200/200" (fourCC XviD, "Packed bitstream" and "DX50-BVOP compatibility" unchecked), aiming for 592500 kb (with 128 abr mp3 audio), BicubicResize(512,288,0,0.4) and together with UnDot() and UnFilter(-10,-10) in the script without any special credits treatment.

Second pass is to finish after some 5 or 6 hours, and I'll report back the complete results then, but as I can see from the debugview output, everything seems great atm! ;)

Many thanks to all developers of XviD one more time!

best regards,
iago

[celeron]

hi again i have test it the uManiac's build XviD.Alpha.20.11.2002.2300.exe Like Iago as sayd its beter, but for me the Qpel still produces some sh*ty frames but its faster 2 encode.
But again whit this build i cant play Bframe in virtualdub whitout being in slow motion (droping frames) i can decode good only whit ffdshow or xvid.ax from nick´s.
And no more crash in deconding.

Thks :)

[sysKin]

Hi,
Today's builds are much better because I found a lot of bugs and removed them. Expect more bugs to be found.

However, Koepi and I just discovered that GMC does something very wrong when combined with qpel and bframes. I never recommended using GMC (not in it's current state), now I recommend even less.

See ya,
Radek

[Koepi]

Just to agree with syskin:

XviD-21112002-1:
- Fresh CVS checkout. Plenty bugfixes and additions...
- Don't use GMC for now, it's buggy. The rest should work fine though.

But it was him who discovered that the GMC option caused the error, so all praise him :)

Best regards
Koepi

[Nic]

Well done the both you :D Hopefully ill be able to get back in the running...Im still not sure if the colorspace code is correct or its just my cr*ppy computer. Its works in RGB though & thats good enough to start releasing again ;)

-Nic

[celeron]

Hi again.

only 2 say that in XviD-21112002-1 all its good again nice speed good quality.
Both Bframes+Qpel or only Bframes, no more probs. whit decoding :)

Great work guys ;)

PS: about GMC i never use.

[scorchED]

could somebody explain us what "b-frame quantizer offset" is, please? what is the setting of 100 or 150 or 200 doing:confused:

[scorchED]

what i've done wrong?
i installed koepis new build 21112002 and tried to make an encode, but the first pass doesn't work. it doesn't matter whicj option i selected. VDubMod starts to encode, but only 1kb per sek is written and i get only a blanc "video" window. Quantizer Mode at Q2 work well with b-frames and qpel.
i tried to switch back to a working 14112002 built but the same problem occurs:eek:
i tried to disable all CPU optimizations, but this problem is still there.
does somebody have an explanation, whats wrong?

[MaTTeR]

scorchED,

Did you load the defaults and then try it?