interlaced content

[Gazza]

I have a question. I have noticed with the last couple of versions of xvid that the encoded output has increased incidence of effects with object edges.

For example, with objects that move against a background that doesn't move, you sometimes get object edges that breakup. Some elements of the object edge are delayed or advanced with respect to the rest of the object. This is most noticeable with actors heads.

Is there a particular reason for this? I have been playing with alt cc and I have noticed that the latest version of codec appear to increase this affect.

I have been using motion search precision = 6 - ultra high. Is this causing problems? Could it be over compensating for movement in the image? Or maybe I have just mis-understood what these parameters do for me. The other parameters I set are;
Quantization type : mpeg
FourCC used: xvid
Max I frame interval: 300
Min I frame interval: 6
Lumi masking and interlacing is not enabled
Aggression: low
High distance is 200%
Low distance is 100%
Strength is 50
[edit] I also use ME hints

I tend to do 2 pass encodes.

Do I need to choose motion search precision of 5 - very high instead of 6?

Could it be just an effect of the speed of the graphics card cause these effects never appear in a video frame that is frozen or paused.

[Teegedeck]

Originally posted by Gazza
For example, with objects that move against a background that doesn't move, you sometimes get object edges that breakup. Some elements of the object edge are delayed or advanced with respect to the rest of the object. This is most noticeable with actors head

Hello Gazza,

are you sure your source isn't interlaced? It sounds a bit like that.

[Gazza]

@Teegedeck

Thanks for the hint. I don't think the sources where interlaced. What would be the quickest way to find out? Using dvd2avi the sources are PAL 16.9, 25fps. I will try again with interlace checked.

I was using ffdshow to view the outputs but removing xvid from ffdshow did not seem to have an impact (i.e. ffdshow is not causing the problem).

But then again, whats to say that the latest version of codec loses synch or control between neighbouring regions (boundaries) of noticeable contrast. If you take a slow panning camera shot which has, for example, a door frame I notice that the edge of the door frame will appear to have a discontinuities (parts of the image are either delayed or advanced horizontally). As the camera moves, the edge of the door will be corrected and everything looks good. But then the whole process repeats at random and quite quickly. Could it be that the codec is under/over compensating for motion at contrast boundaries and maybe between I frames and/or P frames? Has some code from B frames been accidently compiled in the latest versions?

It's impossible to freeze a frame that shows what I mean so I am unable to post an example. Once the image is frozen the image always looks good - which is strange anyway.

[Teegedeck]

Originally posted by Gazza
@Teegedeck

Thanks for the hint. I don't think the sources where interlaced. What would be the quickest way to find out? Using dvd2avi the sources are PAL 16.9, 25fps. I will try again with interlace checked.

You better not try this - the 'interlaced' checkbox is NOT for a de-interlacer! Try using the 'decomb' filter for AviSynth instead.

The only reliable way to find out whether your source is interlaced or not before encoding, is to watch the preview in DVD2AVI (press F5) and watch the edges of moving objects. If just the edges seem to 'break', use the setting 'Telecide()' for decomb. If the whole picture seems to have horizontal lines through it, you have video content and can use the 'FieldDeinterlace()' command for decomb.

It's impossible to freeze a frame that shows what I mean so I am unable to post an example. Once the image is frozen the image always looks good - which is strange anyway.
Try a free screenshot-tool like "2020 Screenshot".

If your soure really isn't interlaced: Try opening your file with VirtualDub and go through it frame by frame in one of the critical scenes. If there actually is an encoding-problem, you'll see the effects in the still-frames, too, and can take a screenshot with VDub. If you can't detect the poblem in VirtualDub, you have a playback-problem that's either to do witch your graphics-adaper or the XviD-DSF. Let us know.

[rui]

Originally posted by Teegedeck

You better not try this - the 'interlaced' checkbox is NOT for a de-interlacer! Try using the 'decomb' filter for AviSynth instead.

No?
I used it with a rip done from a rock concert dvd, which had the typical interlace artifacts, and worked like a charm. :confused:

[Gazza]

@teegedeck

Searched high and low but could not find '2020 Screenshot'. Got any ideas where to get it?

Thanks in advance.

[Teegedeck]

Originally posted by rui


No?
I used it with a rip done from a rock concert dvd, which had the typical interlace artifacts, and worked like a charm. :confused:

Well;
-h wrote on that:

MPEG4 interlacing doesn't remove the interlacing artifacts, but preserves them by separating fields when suitable. It'll allow you to capture interlaced content in either 1) better quality or 2) smaller files.

Lookitup: http://forum.doom9.org/showthread.php?s=&postid=108565&highlight=interlace#post108565

So I don't know exactly why it removed any interlacing from your file; it had been designed for TV-capture (capturing interlaced content). You probably just don't realize the interlacing anymore? Well, that's fine, too, why not! I'll give it try, too, perhaps I can dump that decomb-filter, then (though I think the chances are thin). And on NTSC-movies, I guess we should still do IVTC.

@Gazza: http://www.hotfreeware.com/2020/2020.htm

(The software was called 20/20 - sorry.)

[Teegedeck]

Because this isn't an easy topic, here's another quote from our great teacher -h:

Well, if you feed XviD an interlaced stream, it stores fields *exactly* as they were fed into it - it doesn't flip fields, skip them, change them at scene changes, or any such munging. The fields that go in are the same as the fields that go out. Any problem with field order is the responsibility of the player getting it wrong, as I can guarantee that XviD doesn't change anything in that regard.

And I'll move all this to a new thread called 'interlaced content', soon, as it really is OT.

OK, done.

[Teegedeck]

I've tried the 'interlacing'-option myself now and it definitely doesn't remove interlacing. It processes the video very nicely though, the resulting interlaced file looks very crisp.

[rui]

Teegedeck, thanks for clearing this :)

Since my knowlodge can't even begin to compete with yours, and after reading the link you gave for Sprits's post and -h and others explanations, i must come to the conclusion that what i thought to be interlacing artifacts must be something else. :o

P.S. Today my advice posts in the forum were all dead ends :rolleyes: I'm turning clumsy or something :scared:

[Teegedeck]

Interlacing is a real mind-twister. :confused:
I had to look for -h's posts and read them, too, before I was absolutely sure about what I wrote.

[Gazza]

@Teegedeck

Thanks for the assistance. I checked the source with dvd2avi and sure enough the frame type is 'Interlaced'. You are definetly an expert in this areas :) Thank you.

I've been following Doom9's excellent guides for xvid and maybe it needs to be modified to cater for 'interlaced source'?

Anyway, I have checked the guides and I am not sure how I can implement your suggestions for using the setting 'Telecide()' for decomb. I've not had much experience with Avisynth so I am at a disadvantage here. Can I be a pain in the royal behind and ask you for more details? ;)

Thanks in advance.

[Teegedeck]

Hello again,

just follow Doom9's excellent guides for the deinterlacing (first check whether you can get hold of the problem by changing the field order in DVD2AVI). BTW, DVD2AVI reports almost ALL PAL-movies as 'interlaced', this doesn't mean a thing. You rely on your own eyes, here...

As for decomb, copy it somewhere to your HD, open your .avs-script (I take it that you use GKnot) in an editor and replace the path to one of the unused plugins with the path to decomb. To actually load it, you have to delete the '#' at the beginning of the line. Next, right below the line that specifies your video-input, insert a line with one of the deinterlacing settings. That should do it.

[Gazza]

@ Teegedeck,

Thanks for the info. Tried it last night and it seems to improve the problem. There is the occasional 'break' but it seems better. The source I chose wasn't the best (digitised 1950's back and white which had color added later), so I need to repeat the process again on another more recent source to confirm absolutely.


Two things I did notice though, the opening titles with decomb had a lot of pixelisation or macroblocks around the edges. Using decomb and telecide improved things by reducing these macroblocks around the title edges. Also the encode took about 35% longer to do with the extra filtering by decomb.

[Gazza]

@teegedeck

Tried encoding another more recent source. Within dvd2avi I could not see any problems so I encoded without decomb first. Noticed that the same problem exists. Then re-ran the encode with decomb/telecide. The same problem exists. Therefore, decomb did not improve the result (even though the image is nice and crisp).

Any ideas? I was using the xvid directshow filter. There doesn't seem to be any difference between xvid and ffdshow filters.

[Gazza]

@teegedeck

Further to above - I viewed the encoded output using vdub and there was no problems at all. I viewed the encoded output again (I tried a few different players) but altered the image size to the same as seen in vdub (in case of graphics adaptor issues). When viewed with most viewers I can clearly see the problem.

In summary therefore, viewed in vdub - no problem.
Also, viewed with bsplayer version .85 - no problem (even when viewed full screen).

However, viewed in zoomplayer, ms media player 6.4 and 7.1 - problems.

I checked and all viewers are using the xvid directshow filter. Note, though, I have seen the same problems with ffdshow. Also resolution of my sample encoded output is 672x288.

Got ant ideas (apart from only using bsplayer in the future).

Why is it that vdub seems to give the cleanest picture?

[Koepi]

a) Check your post processing settings in the xvid dsf (reachable via the player's context menu / properties).

b) press "reset" in the DSF.

Now the shown content should be _absolutely_ the same as shown in vdub.

The DSF relies on the xvid.dll internal routines for decoding xvid content. With post processing activated, this "input" gets altered. That's why you see a difference between vdub and any media player (that relies on direct show).

On the general topic, you might be intrested in using vdubs built-in deinterlace (->blend fields).

Smoothes much dirt out of old movies, removes interlacing artifacts (introducing fine ghosting artifacts but who cares), reserving more bitrate for the actual content,... Those old movies really are smoothered out already so you won't notice a difference but the amazing quality gain.

[Gazza]

@koepi
Thanks for the advice. I did the reset but still get the same image break problem. But not with bsplayer though !


I quote

On the general topic, you might be intrested in using vdubs built-in deinterlace (->blend fields).

I checked doom9's guide for vdub which is linked on his first 'Guides' page, but it doesn't mention this. Where can I find the details?

Thanks in advance

[Koepi]

r u kidding me?

in the filters setup of course.

you may want to checkout the vdub forum here at doom9, or go over to www.virtualdub.org and read through the help.

[Gazza]

Yes of course ! Forgive me - its the late end of a long night.

[rui]

Well, i decided to step in again. About your problems with the other players, except for bsplayer:
Horny_German had a problem similar to yours, maybe you would find helpfull to read this thread: http://forum.doom9.org/showthread.php?s=&threadid=24577
P.S. It's another thread where my advice posts weren't good :D
But i hope this can help you. Look for avih's post in second page.

[Gazza]

Thanks Rui. I will have a look at the thread and see if it sheds some light on my issues. By the way, I've done some more testing but the result is always the same. bsplayer doesn't have the same image breaking up problem. Weird stuff!!

[rui]

This is a post with some great tips from unplugged, to capture interlaced source material. My original idea was to capture to MPEG2, and from there proceed exactly like one would do with a DVD rip.
I believe this should be in this thread. Hope that the Mods are the same opinion has i :)


Originally posted by unplugged


Check if you your intermediate MPEG file is "ready" to host interlaced stuff or you get ugly images with motion messed up; this for first.

I am planning on using Ulead Visual Studio 6, i hope it has that option.

Originally posted by unplugged
2nd, when you encode to XviD you can choice the way to deinterlace the content or not.
Thus you can target to obtain a XviD video progressive or interlaced too:

- if you want resize down the image or could not wait a media player that support that XviD/MPEG4 interlaced frames choice to deinterlace.
Then check if your encoding utility has deinterlace option and don't forget to keep disabled XviD interlace support (since your content becomes progressive)

Here you mean to use, for example, greedyHMA plugin (or other) for deinterlace my content, right?

Originally posted by unplugged
- if you have planned to dedicate more space, thus you not want to resize.
And, you want to keep the great "human" fluidity (50fps, that movies never will have ...:angry: ) of interlaced captures, then do NOT use any intermediate filter or resize, simply activate "interlaced support" in XviD options tab.
Note that the resulting file will be physically registered having 25 "full" fps, this is how interlaced content get stored (50 half-frames, as MPEG2 streams).
The negative point is, FOR NOW, that there isn't yet a media player that carefully expands the real 50 half-fps. So, the playback will be at 25 fps, resulting image ghost effect because each couple of half-frames still remains joint and plus the time-stretch is not done 50 times per second :(. )

Do you know of any future project of such a player? That would be GREAT!

Originally posted by unplugged
Note: avisynth is a powerful script language (batch-like) for decoding videos and filtering, it has many functions bundled yet, but you need plugin for deinterlace. Mpeg2avi and Xmpeg have also deinterlace option.

I have been reading some guides (http://www.lukesvideo.com), like Lukes's guide, who explains the interlace very well, and all methods that we current have, in some way or another, simply 1-reduce the vertical resolution by half, or 2-introduce the ghosting effect when blending the odd and even lines, correct?

Originally posted by unplugged
NOTE that if your capture source setup resolution is set to have less or half than 480-576 lines probably doesn't give you interlaced input (704x576@50fps PAL Europe, 704x480@60fps NTSC).

My capture source will be my TV antenna signal. Since i live in Portugal, Europe, i have a PAL signal. But has the PAL analogic signal the same resolution has the PAL digital signal?? This is something that i could't get cleared, no matter how much i lurked in the video capture forum...

EDIT: i forgot something: since i plan to watch all my movies and captures in a tv set, i don't have to worry with the interlace problem in the first place, do i? I just have to capture the MPEG2 with interlace content enabled, then use the interlace option in xvid to mantain the original interlace video, and then, supposedly, when playing it on a tv, i will not have any artifacts, correct?

[trbarry]

The negative point is, FOR NOW, that there isn't yet a media player that carefully expands the real 50 half-fps. So, the playback will be at 25 fps, resulting image ghost effect because each couple of half-frames still remains joint and plus the time-stretch is not done 50 times per second . )
--------------------------------------------------------------------------------

Do you know of any future project of such a player? That would be GREAT!

When run on live data in DScaler the Greedy/HM plugin actually makes 50/60 full frames/second from interlaced fields. But when I made the GreedyHMA Avisynth version of it I only made it put out 25/30. It would mostly double the file size to have 50/60 frames / second and most folks probably wouldn't think it was worth it.

But since Xvid can now store the data in interlaced form it might be possible for one of the Xvid dshow filters to keep up with 50 / 60 full frames if we added deinterlace, but only on a very fast machine if you wanted 576 / 480 lines resolution.

I have been reading some guides (http://www.lukesvideo.com), like Lukes's guide, who explains the interlace very well, and all methods that we current have, in some way or another, simply 1-reduce the vertical resolution by half, or 2-introduce the ghosting effect when blending the odd and even lines, correct?

This is not completely true. When you have confidence that some pixels are not moving then you can display the pixels from adjacent fields, getting more resolution than just interpolating from the current field. GreedyHMA and other adaptive deinterlace methods like the Radeon cards adaptive DVD deinterlace do this so I think may you lose (swag) 1/4 of the resolution, but not half.

And when you add motion compensation into the picture then the number of pixels you have confidence in increases a bit more, though never to 100%.

The process works much better if you only have to put out 25 / 30 frames / second because then you can use methods that might produce visible jitter if you had to construct both even and odd frames for a progressive display.

- Tom

[unplugged]

Originally posted by rui
I am planning on using Ulead Visual Studio 6, i hope it has that option.

Check if you have possibility to use HuffYUV or a good MJPEG as codec, usually these are the best and very fast lossless/loss codecs for temporary storing (fast, so there isn't risk to lose frames), though if HD space isn't a problem :D:rolleyes:.(though I don't know if Visual Studio can uses Windows installed codecs).

Originally posted by rui
Here you mean to use, for example, greedyHMA plugin (or other) for deinterlace my content, right?

Well, just according to coder (trbarry) info it should be the smartest available ;).

Originally posted by trbarry
But since Xvid can now store the data in interlaced form it might be possible for one of the Xvid dshow filters to keep up with 50 / 60 full frames if we added deinterlace, but only on a very fast machine if you wanted 576 / 480 lines resolution.

You say "...if we added deinterlace", but Why deinterlace even for video output? :D
I have red that principle of interlaced video is to obtain 50fps AT THE COST of 25 ;), so who invented this had in mind the exact behavior of home TVs refresh.
That refresh is performed 50 times per second, but not each time for full lines, but by alternate way: odd lines, even lines, odd lines, even lines... (anyone has always seen thin horizontal lines flashing :D while watching TV)
Each even/odd image hasn't a quick switch off so it tends to blend with the next refreshed image that comes more strongly bright; by this way the motion shows its fluidity very softly to human eye, and thus maintaining all the 50 "EVENTS" per second.

Deinterlace should be only used to reencode, deinterlacing also video output kills the benefits that have spured to adopt the the widely used interlaced-format (all analog-digital cam-recorders).

Sure, you can say: "but monitors are quite different from TVs!"
Of course, refresh is non-interlaced, resolution is pain to be adapt and 50hz refresh rate is hell of flashing for a monitor :).
But whe should only need a good on-video frame-interleaving algorithm (midway between BOB and WEAVE technique) and 100Hz refresh rate in our monitor as near multiply of 50Hz PAL for correct synchronism.

DirectShow filter
The stuff to compute isn't so much heavy as seems, I think most of computing time is raised (doubled) on video card overlay department (video acceleration), to put 50 instead of 25 per second.
I would remark those 50 or 60 (NTSC) are HALFframes so the decoding speed demand is same for a 25fps progressive video.

Theorically the decoder have to interleave all the half (or semi) frames by an alternating behavior...
HALFFRAME N° - EVEN/ODD LINES FROM VIDEO FRAME X
Frame 0: even0 + odd0
Frame 1: even0 + odd1
Frame 2: even1 + odd1
Frame 3: even1 + odd2
Frame 4: even2 + odd2
Frame 5: even2 + odd1
...
Frame 49: even24 + odd25

This could be an example of playback 1st second of PAL interlaced video.
...guess some ghost effect with this one :rolleyes: ...?
Maybe useful for "leaving" half-frames to assign them less brigthness, to enforce the other just arrived.

Originally posted by rui
My capture source will be my TV antenna signal. Since i live in Portugal, Europe, i have a PAL signal. But has the PAL analogic signal the same resolution has the PAL digital signal??

I'm almost sure that should be same, 704x576 (or 720x576), I don't imagine different... this is the standard (but don't ask me about HDTV).

Originally posted by rui
...then use the interlace option in xvid to mantain the original interlace video, and then, supposedly, when playing it on a tv, i will not have any artifacts, correct?

Since there will not be the "right" media player or DS-filter you will see only 25 frames per second, plus interlaced. NOT 50 time shifted.
So, of course this appears as artifact :o, even if it's only a player lack.

[rui]

I must say that, with these two posts from both Trbarry and unplugged, i fell that i advanced in my knowlodge something equivalent of reading forums for a year :D
Thanks you guys :)

quote:
--------------------------------------------------------------------------------
Originally posted by trbarry

But since Xvid can now store the data in interlaced form it might be possible for one of the Xvid dshow filters to keep up with 50 / 60 full frames if we added deinterlace, but only on a very fast machine if you wanted 576 / 480 lines resolution.
--------------------------------------------------------------------------------

Trbarry, i believe that you are responsible for the optimization of the deringing part of the current Nic's post processing filter xvid has, correct? Sorry if i missed anything.

To you , and Nic: Can this be made?? ;)
I for one would LOVE such an option, it would take away the extra time to add in the encoding time because of deinterlace action. Plus it would maintain the picture in it's original form.

[trbarry]

Trbarry, i believe that you are responsible for the optimization of the deringing part of the current Nic's post processing filter xvid has, correct? Sorry if i missed anything.

To you , and Nic: Can this be made??


rui -

Nic wrote the deringing code. I just made an assembler optimized version of it.

I started looking into adding GreedyHMA to Xvid some time back but then instead had some ideas and created an entirely new deinterlace filter with some rudimentary motion comp code in it. It's not done yet but so far I have only DScaler and Avisynth versions, sort of working.

I still haven't made up my mind whether it would do better in Xvid to deinterlace first and store progressive or to put it into the player and deinterlace at playback time. I sort of thought that deinterlacing first might compress better but I'll defer to the compression experts here if anyone knows the answer.

I'll probably add deinterlacing to the Xvid or ffdshow filter, whichever has up to date source publicly available by the time I get to it. But either way I'll do dshow versions last because they are harder to debug. In my programming style I like to set breakpoints and debug assembler code by stepping through it watching one instruction at a time and I don't seem to be able to do that in dshow.

Also, I haven't used it but there is already a DScaler dshow filter that does some type of deinterlacing. I think it's available at Sourceforge. But I don't think it supports GreedyHMA yet. On a screen shot I saw recently the best available method in it was the Blended-Clip deinterlace method.

- Tom

[rui]

Trbarry, thanks again for the info.
I searched for DScaler, and found out that the project's site: www.dscaler.org

I must admit that i didn't know anything about DScaler. I already had hear about it, but thought that it was another plugin that we could load in avisynth scrip to Vdub, for example. But it's much more than that. For people (like i intent to do) that want to capture video from interlaced source (pal analogic tv signal), probably it's great. I must try it when finally purchase my TV card. ;)

I saw in the site that the latest version (3.1.0) already supports greedyHMA, Greedy Low montion, Greedy High motion and Greedy 2 Frame.
Just one question: i have been using your greedyHMA plugin that comes with the Gnot instalation. Your plugin incorporates all this methods or is a prior build? Or is the 2 frame option that DScaler has?

About the ds filter, i am not exactly sure of how to use it, but i don't think i can use it yet for decode some xvid clip, or can i? (i saw that you gave some contribution to it, in the authors txt;)

[Nic]

OT:
@rui:
Would you like to see GreedyHMA as an option in D2A?

-Nic

[trbarry]

I saw in the site that the latest version (3.1.0) already supports greedyHMA, Greedy Low montion, Greedy High motion and Greedy 2 Frame.
Just one question: i have been using your greedyHMA plugin that comes with the Gnot instalation. Your plugin incorporates all this methods or is a prior build? Or is the 2 frame option that DScaler has?

About the ds filter, i am not exactly sure of how to use it, but i don't think i can use it yet for decode some xvid clip, or can i? (i saw that you gave some contribution to it, in the authors txt

rui -

GreedyHMA and Greedy (High Motion) are much the same thing, the first for Avisynth and the other for DScaler. But I don't think it is included in the 3.1 verson of the dshow filter. I'm not sure about the 4.0 alpha that's around somewhere.

Again, I've never used the dshow filter version. I really should try it someday but my DScaler involvement has been intermittent for some months now. I'm not sure exactly what's in it but my listing in the authors section is probably just because I also wrote the Blended-Clip and Greedy (Low Motion) methods.

The current GreedyHMA is still based upon the DScaler 3.1 Greedy (High Motion) version. There were some changes in calling conventions in DScaler 4.0 that I never ported to Avisynth.

- Tom

[rui]

Nic, when i am doing a rip of a interlaced movie, i have always used GreedyHMA, with good results, so i would like to have such an option. But that's my opinion, maybe others think diferently. Some say (i never tested) that, for example, fast deinterlacing is...faster. I can't speak about fast deinterlacing end picture quality also, i never compared the two.

Trbarry: i thought that Greedy was already supported in DScaler version 3.1.0 because in the help section (http://www.dscaler.org/Help/), in the Deinterlace methods they mention Greedy.
In the site it mentions:
DScaler supports a plug-in architecture for video deinterlacing

At start up it will load up any plug-ins and display those loaded sucessfully in the Deinterlace Mode submenu.

All of the various methods have there own set of compromises and none are perfect in all situations. The closest to an all round method is Greedy 2 Frame.

[Gazza]

This is very interesting and educational. Thank you for all the inputs and advice.... I tried using telecide as suggested but this did little - I suspect my sources are not interlaced afterall?

It seems that the fix to my original problem was to simply set my desktop to 32 bit. In most cases (I have been reading a few other threads of similar issues to one I raised) this fixed the problem. However, my desktop has always been 32 bit. Hence I have been off researching and reading, etc, etc.

I think I may have found an alternative solution which was prompted by a recent thread - by simply uninstalling divx5 and divx5 pro and hey presto my 'broken video' issue disappears.

The thread is http://forum.doom9.org/showthread.php?s=&threadid=25213

I don't pretend to know why but I would appreciate anyone else having a look at this and maybe confirming my suspicions that divx5 is impacting on xvid or maybe the directshow filters?

[edit] I did mention before that my problem was a recent one. And recently I did install the latest divx5 packages as reported in doom9's excellent news updates. The plot thickens !!!

[rui]

Gazza, i am not using divx5 anymore for some time, but in the time that i had both divx5 pro and xvid builds installed, i never had any problems with my xvid encodes being messed up by divx5 ds filter.

That problem is old, there was a thread in divx5 forum that related to that http://forum.doom9.org/showthread.php?s=&threadid=19404&highlight=xvid

This thread speaks mainly about divx5 doen't give you a chance of not choosing it to decode divx3 avi's, but there are some posts about xvid decoder being messed up by divx.

[Gazza]

@rui

I agree it is an old issue but worth posting here as removing divx5 resolved my issues. Therefore my experience may help others with similar issues. My problems have only appreared recently so maybe installing the lastest divx5 a few weeks ago is the root cause?

Gazza

[rui]

Originally posted by Gazza
My problems have only appreared recently so maybe installing the lastest divx5 a few weeks ago is the root cause?

Gazza

I believe not, because if in reality is divx5 that is behind that, it started when the first version came out. At least people where already stating that when having divx5.0 pro was messing their xivd decoding.

Please, don't miss understand my words. I give every credit to your experience.
I didn't had any problems with it, but one never knows...maybe if i had kept divx5 in my system (i don't like having gator in my comp, in spite of being able to control it like doom9 explained), in time i would experience problems too, who knows... ;)

[Aktan]

Originally posted by Gazza
.. I tried using telecide as suggested but this did little - I suspect my sources are not interlaced afterall?


did u resize before you telecine? the telecine does not work on resized video

[chemmajik]

I have been silent of sorts about XVid but to make a long story short. My interlaced problem with white moving blocky area's disappeared. But that was after I had to reinstall windows, ran a old stupid nortons unerase, fried my drive good. But in the process I didnt reinstall DIVX5. I'm not going to install it to see if it was the cause. I do know it effects my nandub divx3 usage & divx playing. If I get a divx4-5 file I found you can just change the 4cc code & it will play just fine under the dshow xvid filter. Also I can always convert it if I want with Vdub. They can use someone else as there bug tester. Anyways my interlaced blocks for white moving area's disappeared thats all that matters. But I am using 5-12 umaniac fresh install build also. So I'll be doing more testing soon when I have time for other interlaced issues. Just busy with other projects outside mpeg4, keep up the good work.