Log in

View Full Version : XviD-1.0.1-05062004 Bugfix Release


Pages : 1 [2]

pelle412
24th June 2004, 00:44
Hmm, it seems strange. Maybe there's something wrong with my system? It's been encoding for quite a while. It only happens when I enable packed bitstream though, which is the truly weird thing. It also happens on the first frame which means the CPU and chipset haven't started working really hard yet.

EDIT: erhm, only happens when I disable packed bitstream, and only on this clip.

lordadmira
24th June 2004, 01:32
I have build 2439 and it didn't crash. Win98.

pelle412
24th June 2004, 02:24
Well then it seems like it's a problem on my side. It's puzzling though. It only happens with this clip, using XviD 1.0.1 and no packed bitstream. DivX 5.1.1 worked fine too.

CruNcher
24th June 2004, 15:57
@lordadmira
the whole frame flickering problem is another one and only happens when very high bitrates are used DVD kind and the quantizers look like this p2 -sharp b3 -blurry p2 -sharp b3 -blurry p2 -sharp b3 -blurry this will couse a per every b-frame flicking :) i didn't test that myself yet, but i saw it. And what i can say is that b-frames are still not that perfect this quant flickering also happens without useing AQ but is not that visible as with AQ, only a slight intensity difference is percived.

cheerow
24th June 2004, 17:32
Are there any plans on implementing AQ for B-frames in XviD?

Tuning
24th June 2004, 19:13
A question regarding decoder.

Is there problem in brightness, as i can see new XvID decoder tends to be a lot darker than FFDShow or DivX decoders.

Thanks.

Koepi
24th June 2004, 19:39
tuning:

try selecting different colour spaces for output, i.e. force YV12. Or try the compatibility renderer.

Regards
Koepi

Teegedeck
24th June 2004, 19:43
Originally posted by CruNcher
@lordadmira
the whole frame flickering problem is another one and only happens when very high bitrates are used DVD kind and the quantizers look like this p2 -sharp b3 -blurry p2 -sharp b3 -blurry p2 -sharp b3 -blurry this will couse a per every b-frame flicking :) i didn't test that myself yet, but i saw it. And what i can say is that b-frames are still not that perfect this quant flickering also happens without useing AQ but is not that visible as with AQ, only a slight intensity difference is percived.
I encode at high bitrates all the time and don't have that problem and cannot reproduce it. I think the flicker you saw probably had other reasons.

Thus I believe Didée and bond gave a far more plausible explanation.

Tuning
25th June 2004, 18:47
Originally posted by Koepi
tuning:
try selecting different colour spaces for output, i.e. force YV12. Or try the compatibility renderer.


Thanks Koepi, everything working fine now. :)

virus
26th June 2004, 16:15
@Koepi:

no silent update to fix the "wrong version in the about box"-problem scheduled? (as posted here (http://forum.doom9.org/showthread.php?s=&threadid=76557&perpage=20&pagenumber=2) a couple of weeks ago)

cheers
virus

Koepi
26th June 2004, 18:31
virus:

you consider that a real problem? That's so minor...

well, let's see if I want to install the compiler already, I still am reconfigurring my system after a fresh installation.

Regards
Koepi

virus
26th June 2004, 18:51
Originally posted by Koepi
you consider that a real problem? That's so minor...Yeah, I agree it's minor. Originally I feared other data defined in xvid.h may have been invalid, especially the bitstream version. But seeing reports that your build correctly marks the stream as "version 35", I surely agree it's really minor... anyway, as you know the About box is built dinamically querying xvidcore for the embedded version. That means that at least something's wrong in xvidcore, so just to be safe... ;)

Also, given the amount of bugreports for XviD 1.0.1 (close to zero if any), I think this version will last very long, so maybe having everything 100% perfect may be a good idea (of course, there's really _no_ hurry if you're busy on different tasks).

(BTW: have you identified what exactly caused this glitch?)

cheers :)
virus

Koepi
26th June 2004, 20:00
virus:

hm, the core has the right bitstream number in xvid.h - i'll investigate.

Regards
Koepi

galocza
6th July 2004, 19:52
hi,
now i tried the "new breed", i really liked the bitrate mode in 2-pass.
but my encodes are jerky when played back. then i found out what it was: when motion precision is on (level doesnt matter) i have this problem playing them back with both ffdshow and xvid dsdec. switched off, its ok. went back to Nics 030716 build its ok.
thought about as filters and anything but the clean material fed to vdubmod does the same so i really think its something to do with xvid.
any advice?

ps: i didnt play around with settings (im a real noob for that, almost everything is default: only max i-fr interval is set to 250 and display encoding status is swithed off).
thx

Koepi
6th July 2004, 20:25
galocza:

uninstall both ffdshow and xvid. (I mean it. uninstall them properly and don't install a 1.x build over an older build - I switched installer systems and upgrading doesn't work!)

Then, fetch the latest ffdshow from http://athos.leffe.dnsalias.com/ and install it.

After that, fetch the latest xvid binary from my site, install it.

It should work flawless then.

Regards
Koepi

egandt
7th July 2004, 03:25
I'd suggest ffdshow from: http://mitglied.lycos.de/ieggei2/ffdshow/ if you have a P4 or AMD64 processor, the SSE2 optimization make all the diffrence in the world if you resize or denoise.

ERIC

yaz
7th July 2004, 11:40
@galocza
pls, allow to PM you !
the bests
y

galocza
7th July 2004, 12:59
@Koepi:
thank you, ill follow your instructions. btw ive uninstalled xvid before the new one but not ffdshow...

@egandt:
unfortunatelly i have neither of them 8(, i dont have sse2.

@yaz:
ok ive set it but i almost never log in (im mostly a reader not a writer here 8), but i (more or less) regularly check this email account: mymovies@freemail.hu.

thank you all,
galocza