Problem with the latest CVS build?

[Jeffster]

Hi,

I've just installed the latest CVS build from celtic_druid and there appears to be a problem with it, at least on my system anyway. (actually builds from both the 15/09 and 16/09)

Maybe it is already known, but I haven't seen any reports here so I thought I'd mention it. The video produced it is barely watchable, and I've never seen that happen before.

I've temporarily uploaded two samples to my homepage server for anyone who wishes to see what I mean.

The first sample from 08/02 build is normal, as expected. By contrast, the second sample from 09/16 build clearly demonstrates the problem. Both were encoded at Q3 and the rest of the settings were the defaults. Interestingly the filesize is different too.

FWIW - my cpu is Intel (celeron)

Jeff

[celtic_druid]

Downloaded both, compressed the good one myself with Q3 + defaults and it looks fine.
My other limited tests also came out fine.

On the 15th I released gcc, ICL7 and ICL9 builds. Are they all effected? The one on the 16th was patched ICL9. Only the genuine intel check was removed though so it shouldn't make any difference.

Some one else want to test since I don't appear to be able to replicate the problem.

[Jeffster]

After seeing the result with 16th I went back and grabbed one from the 15th packed in 7z "xvid.cvs.head.2005.09.15.7z"...

I'm not sure which compile it is sorry, except it wouldn't be the ICL9 one since that is named as such.

I just checked another mirror and it has 3 files dated the 15th and I guess they are different compiles?
XviD.cvs.head-20050915.exe
XviD.cvs.head-20050915_2.exe
XviD.cvs.head-ICL9-20050915.exe

I've tried all 3 now and get the exact same (weird) result.

[celtic_druid]

XviD.cvs.head-20050915.exe & XviD.cvs.head-20050915_2.exe I think are basically the same. I added a userdata field with the build date and updated the installer.

I can't reproduce the problem at all though and I don't have any Intel CPU's to test with, let alone a celeron.

[boombastic]

just to know because i am a newbie of compiling stuff:

which is better between the ICL9,ICL8 and GCC compiles for an Athlon XP 3000+?
Besides this, i tried the compile of the 15th and got a fine result.

[Episode]

ICL9 should still be faster than the others, even on AMD processors.

[celtic_druid]

Since I removed the genuine intel checks from the ICL9 compile it should definatly be faster on AMD's. With the checks in place ICL7 I would think would be faster.

How gcc fares I don't know. People always wanted gcc compiles though, so I still do them occasionally.

[Jeffster]

Some one else want to test since I don't appear to be able to replicate the problem.
[...]
I can't reproduce the problem at all though and I don't have any Intel CPU's to test with, let alone a celeron.
I hope someone else is able to test this and reproduce the problem too. I'm beginning to wonder if it may somehow be cpu related.

I'm gonna try attaching a screenshot showing what I mean for those unable to check out the sample clip. This time I also enabled 'Print debug info', not that it is very helpful since it's unreadable.
(bare in mind this was encoded at Q2 this time!)



http://homepages.ihug.co.nz/~jefx/temp/xvid_2005.09.16.jpg

[celtic_druid]

Surely there must be someone else here able to test? I tested on one AMD 64 and a thunderbird. Both were fine.

I'll put up a plain MSVC build for you to test.
http://mirror05.x264.nl/celtic_druid/force.php?file=./xvid_msvc.7z

[Jeffster]

Thanks celtic_druid.
I tried with the plain build but unfortunately the results were still the same for me.

[celtic_druid]

Ok, so it probably isn't a compiler issue.

[Koti]

I can confirm and reproduce this 100% ( intel celeron mobile 1333mhz )
with that build posted above - Vob > VDubMod > Xvid (Q2 defaults) = Disaster just as Jeffster has show in post above

edit - no problems on P4 3.2 Prescott or AMD2100+

edit 2 - performance optimizations - xvid on celeron detects and uses MMX , Integer SSE , SSE
When MMX is disabled the output is fine.
(I hope that can narrow down where to look for the bug )

[kesako]

i've got a problem too.
i've downloaded XviD.cvs.head.MTK__20050921.exe.i've tested the MTK PAL profile with these settings :
2 pass
quantizer type : MPEG
adaptive quantization
1000 kbps
motion search precision: ultra high
VHQ mode : wide search
use VHQ for b-frames too.
use chroma motion
max i frame interval : 250

other settings by default
result is very bad.

[suxen_drol]

confirmed. to reproduce the problem, force the use of MMX optimised functions only in advanced->debug window.

this suggests a bug within one or more of the mmx-only optimised functions. the equivalent sse2/3dnow function(s) are working correctly, and as most users have p4/athlon/modern-celeron cpus, this explains why few people have detected the fault.

-- pete

[celtic_druid]

So it looks like one of the new ASM functions added recently is responsible.

Someone really should post this on the mailing list.

[Jeffster]

Thanks everyone. :)
I'm glad the bug has been confirmed and narrowed down at least.

[ChronoCross]

it happened to me using megui. Pentium 3 so it's most definitely one of the MMX functions. Happened it 2 pass mode for every single frame no matter the quant.

[squid_80]

Looks like the AC coefficients are missing. Could the new cbp_mmx function be responsible? (I'm only looking at the cvs log, haven't checked the code...)

EDIT: Yep, looks like calc_cbp_mmx is doing something it shouldn't.

EDIT2: The packssdw/pcmpgtw instructions are buggy. I can explain in greater detail if required.

[sysKin]

Could the new cbp_mmx function be responsible?
It's funny how cbp calculations, were optimized over and over again, while they have no impact on the speed at all ;)

[Sharktooth]

Well, but now it's optimized... :rolleyes:

[squid_80]

In 64-bit mode calc_cbp_c is quicker than the assembly versions.

[Sharktooth]

It was sarcasm :p

[ChronoCross]

It's funny how cbp calculations, were optimized over and over again, while they have no impact on the speed at all ;)

Just as long as it gets fixed xvid is already fast enough for me lol.

[suxen_drol]

Just as long as it gets fixed xvid is already fast enough for me lol.

fix applied to cvs head.

[celtic_druid]

http://mirror05.x264.nl/celtic_druid/force.php?file=./xvid.cvs.head.exe

[ChronoCross]

Fixed in CVS head vfw. Broken in mencoder but hopefully that'll change soon.

[celtic_druid]

Well it is also fixed in mencoder, you just have to link against the fixed lib. I've built the updated XviD libs, but I haven't gotten around to compiling mplayer/mencoder. That's if you are talking about my builds.

[fight2win]

pls can someone give me link for xvid latest builds?

[fps]

http://www.aziendeassociate.it/cd.asp?dir=/

[fight2win]

thanks!