New ffdshow build (?)

[BlindWanderer]

No, I think MPC supports hardware deinterlacing. Read my prior post again.

I didn't know it would do that. Checking the check box did not enable deinterlacing (though software deinterlacing works find in MPC). I'll try the newer video driver (it's supposed to be for Nvidia's high def video decoder; which is neither here nor there).

[BlindWanderer]

*slams head into keyboard*
helps to make sure you have overlay mixer set as the video renderer.
Which begs the question, how & why *was* i able to get hardware deinterlacing to work *without* the overlay mixer before? Seems like hw deinterlacing isn't dependent on overlay.

EDIT:
Course the screen saver i use doesn't let you choose the renderer.

[haruhiko_yamagata]

*slams head into keyboard*
helps to make sure you have overlay mixer set as the video renderer.
Which begs the question, how & why *was* i able to get hardware deinterlacing to work *without* the overlay mixer before? Seems like hw deinterlacing isn't dependent on overlay.

EDIT:
Course the screen saver i use doesn't let you choose the renderer.
In my PC, hw deinterlacing is working with overlay mixer. Unless you are very sure that the bug is within ffdshow, please report the bug to nvidia. They'll make sure which is bugy.

[Jeremy Duncan]

Does the FFdshow HW Deinterlacing feature allow Nvidia purevideo to use HW Deinterlacing ?
If so, which is recommended Bob, or Weave in FFdshow ?

[Bathrone]

Motion adapative temporal deinterlacing. Bob and weave are so poor. I reckon ATI and NVIDIA's hw deinterlacers are great - check out the HQV benchmark disc.

[Jeremy Duncan]

Motion adapative temporal deinterlacing.

Does the FFdshow HW Deinterlacing do "Motion adapative temporal deinterlacing" ?

With the FFdshow HW Deinterlacing enabled and if I used the Purevideo codec and hardware, do I get "Purevideo HW Deinterlacing" ?

[foxyshadis]

Er, there is no ffdshow "hardware" deinterlacing; it has its own software deinterlacing, or you can ignore it and run whatever your ATI, Nvidia, or other DXVA drivers do. (So yes, Purevideo or AVIVO.) ffdshow has no control whatsoever over downstream deinterlacing, other than being able to signal that the video's interlaced.

Weave isn't even "deinterlacing", it just displays combined fields. Both ATI & Nvidia's hardware methods have mocomp and pulldown detection, and look nearly as good as tdeint in a fast mode.

[Jeremy Duncan]

Er, there is no ffdshow "hardware" deinterlacing; it has its own software deinterlacing, or you can ignore it and run whatever your ATI, Nvidia, or other DXVA drivers do. (So yes, Purevideo or AVIVO.) ffdshow has no control whatsoever over downstream deinterlacing, other than being able to signal that the video's interlaced.

Weave isn't even "deinterlacing", it just displays combined fields. Both ATI & Nvidia's hardware methods have mocomp and pulldown detection, and look nearly as good as tdeint in a fast mode.

Does this mean that if I enable HW Deinterlacing in FFdshow, that my Purevideo certified video card and purevideo codec will use "Motion adapative temporal deinterlacing" ?
If so, why is there a box to choose from bob or weave when I enable HW Deinterlacing in FFdshow ? What's that for ?

[foxyshadis]

All of that is controlled by the driver's control panel. I only have ATI, so I have only vague recollections about Purevideo, but I know it's in its control panel too. Bob and weave are relics of the stone age of gpu-assists, when it only worked with MPEG2, both flags are probably ignored now.

[Jeremy Duncan]

All of that is controlled by the driver's control panel. I only have ATI, so I have only vague recollections about Purevideo, but I know it's in its control panel too. Bob and weave are relics of the stone age of gpu-assists, when it only worked with MPEG2, both flags are probably ignored now.

Since they are probably ignored.
Does this mean if I enable HW Deinterlacing in FFdshow's output tab that "Motion adapative temporal deinterlacing" is available with the right hardware and codec ?

[Bathrone]

A developer can confirm, but I believe that if you dont enable any deinterlacing within ffdshow and set your driver to do the deinteracling and the method thats what I do. I use ati, there is an applet that let's me configure my deinterlacing preference.

[haruhiko_yamagata]

foxyshadis is right, there is no hardware deinterlacing control in ffdshow. But generally the downstream of ffdshow is video renderer and the check box works as hardware deinterlacing. If the downstream of ffdshow is software deinterlacer, it works as hint for the software deinterlacer.
Bob and Weave is a hint for downstream. In most cases Weave is same as unchecked hardware deinterlacing.
ffdshow can only show hint for down stream. What happens in down stream is down stream's responsibility.

[Jeremy Duncan]

foxyshadis is right, there is no hardware deinterlacing control in ffdshow. But generally the downstream of ffdshow is video renderer and the check box works as hardware deinterlacing. If the downstream of ffdshow is software deinterlacer, it works as hint for the software deinterlacer.
Bob and Weave is a hint for downstream. In most cases Weave is same as unchecked hardware deinterlacing.
ffdshow can only show hint for down stream. What happens in down stream is down stream's responsibility.

In other words. If my video card and Video codec support "Motion adapative temporal deinterlacing" / "Purevideo Deinterlacing".
Running FFdshow won't cancel this and force it into software mode, as long as HW Deinterlacing is checked, and Bob is selected in the Output tab ?

[BlindWanderer]

New bug, when parsing FLV1 (which seems to have no restrictions on resolution) with the OSD turned on, the osd color is overlayed in the wrong (vertical) position when the video resolution is not divisible by 4. This bug does not effect playback (read: ffdshow doesn't crash & no new artifacts).

So a video with a resolution 320x239, the osd color is rendered about 3 pixels higher then the the text.

http://mailerdaemon.home.comcast.net/6SK-bcWCU8w.flv

[haruhiko_yamagata]

In other words. If my video card and Video codec support "Motion adapative temporal deinterlacing" / "Purevideo Deinterlacing".
Running FFdshow won't cancel this and force it into software mode, as long as HW Deinterlacing is checked, and Bob is selected in the Output tab ?
I don't have nvidia cards and don't know what to answer.

[clsid]

List of known issues in revision 483:

1) Interface bug in Windows Vista. Details and screenshot (http://forum.doom9.org/showthread.php?p=888312#post888312). (reported by BlindWanderer)
2) Wavpack decoder doesn't work with this file (http://rapidshare.com/files/1609252/SoC__XviD_WavPack_MP3_-007.mkv.html). (reported by clsid)

Reported but unconfirmed bugs:

3) image settings -> preset autoload conditions -> "on FOURCC match" doesn't work. (reported by juskixxx) (confirmed by clsid) (haruhiko could not reproduce it)
4) Automatic preset loading doesn't seems to be working with on "number of channel match" and AC3 audio on DVD (don't know if it happens with AC3 audio in MKV, AVI or not or any other audio format). I use "3;4;5;6" in "number of channel match" so this should load with audio track with more than 2 channels but with an AC3 2 channels track this is also loaded. (reported by thuan)
5) Instant crash when trying to play this MSS2 WMV file (http://ftp.mplayerhq.hu/MPlayer/samples/V-codecs/MSS2/mss2_speech.wmv). Happens on Windows 2000. No crash on drevil_xxl's XP system. (reported by clsid)
6) The following encoders do not work for me: MPEG 4, MPEG 1, MPEG 2, h.263, H.261 and DV. VirtualDub 1.16.16 gives the following error: "Cannot start video compression. An unknown error occurred (may be corrupt data). (error code -100)". I know that at least some of these encoders do work for others. My system specs: Windows 2000, AMD Athlon Thunderbird. (reported by clsid)
7) Resize filter alters colors. Details (http://forum.doom9.org/showthread.php?p=884778#post884778). (reported by Kador)

Other issues:

8) ICL9 builds of ffdshow.ax crash on files created by a specific old revision of x264 (don't know the rev number). Funny thing however is that the files play without crash if you first play a good file and then play a 'troublesome' file in the same player instance. Also no crash when using an unoptimized debug build. So this seems to be a compiler bug. Sample file (http://rapidshare.com/files/1609924/sample.mp4.html). (reported by clsid)

[Eragon4ever]

What about putting the List of known issues in todo.txt?

[clsid]

This way they are visible to everyone.

[Eragon4ever]

Of cause, I meant additionaly and form time to time you can copy&past it here.
And the developers would not have to search here for it.

[haruhiko_yamagata]

3) image settings -> preset autoload conditions -> "on FOURCC match" doesn't work. (reported by juskixxx)
I still can't reproduce this. Any suggestions how to reproduce is appreciated.

[Egh]

clsid: I notice you've changed your installer script in the rev457 build.

Now it offers to restart at the end of process instead of "Abort, Retry, Ignore" during it.

[clsid]

I still can't reproduce this. Any suggestions how to reproduce is appreciated.
Create two extra presets (besides default).
Enable 'automatic preset loading'.
Preset 1: on FourCC match = DX50;DIVX
Preset 2: on FourCC match = XVID

Now play some DivX and XviD files. The correct preset doesn't get chosen.

clsid: I notice you've changed your installer script in the rev457 build.

Now it offers to restart at the end of process instead of "Abort, Retry, Ignore" during it.
Haruhiko made most of those changes. But do you think it is good or bad?

[Egh]

Haruhiko made most of those changes. But do you think it is good or bad?

Dunno. For casual user it's prooly bettar.

Though for me it's a bit of inconvinience, since I used to kill tc when that dialog was shown :)

But of course I can close it once I've started ffdshow setup, so it's not a major problem. I just wanted to clarify things ;)

Btw it would be great if ppl who do changes would explain them in this thread. One single-line phrase in ffdshow svn is not quite enough to comprehend :)

Would be interested to know what exactly was done in the following revisions:

Revision 458 - Directory Listing
Modified Sat Oct 28 00:13:53 2006 UTC (39 hours, 31 minutes ago) by h_yamagata

restart replace for libmpeg2_ff.dll

Revision 447 - Directory Listing
Modified Wed Oct 25 09:13:04 2006 UTC (4 days, 6 hours ago) by h_yamagata

ANSI/MBCS more security fixes

Revision 444 - Directory Listing
Modified Tue Oct 24 13:54:30 2006 UTC (5 days, 1 hour ago) by h_yamagata

Bug fix (ANSI)
ANSI debug build often crashes when we click task tray icons. This affects release build too, and is security issue.


Revision 439 - Directory Listing
Modified Tue Oct 24 11:02:52 2006 UTC (5 days, 4 hours ago) by h_yamagata

Bug fix : Quality control of post processing. It has been depending on CPU usage(performance monitor). Now that I removed the performance monitor related code, it has to be fixed.

Revision 398 - Directory Listing
Modified Mon Oct 16 14:00:29 2006 UTC (13 days, 1 hour ago) by drevil_xxl

fixed(?) stereoscopic subtitles.

[_xxl]

Would be interested to know what exactly was done in the following revisions:
Revision 398 - Directory Listing
fixed(?) stereoscopic subtitles.

Bug Fix:ffdshow crashes when enabling stereoscopic option on subtitles page.
Stereoscopic Subtitle Guide:
http://www.3dtv.at/Knowhow/Subtitles_en.aspx

[Egh]

Bug Fix:ffdshow crashes when enabling stereoscopic option on subtitles page.
Stereoscopic Subtitle Guide:
http://www.3dtv.at/Knowhow/Subtitles_en.aspx

My confusion was caused by the fact that stereoscopic subtitles were due to be removed from ffdshow :)

[clsid]

That was because it crashed previously. So the option was disabled. Now the function works without crashing. However its usefulness is debatable.

[Jeremy Duncan]

I don't have nvidia cards and don't know what to answer.

"The best de-interlacing methods, yielding the highest quality, are complex. There are no simple ways to do this job to eliminate artifacts in all cases. Old de-interlacing methods, simple and non-adaptive to motion speed changes, are becoming a thing of the past, providing not the best quality. Modern video chips use complex de-interlacing, so called adaptive methods. Adaptive de-interlacing methods selectively cut pixels, based on information about motion in a frame. Before AVIVO, ATI products already used adaptive methods. But it's R520, RV530, RV515 video chips supporting AVIVO, where the company introduced the advanced method - vector adaptive de-interlacing. This improved algorithm resembles the new method in NVIDIA PureVideo - spatial-temporal. In brief, it works in the following way: the algorithm selects data to build a progressive frame from either the raw field data, when motion is detected to be low; in case of fragments with fast motion, it uses video data that is interpolated along several vectors, which provides the greatest amount of details to the progressive frame. Vector adaptive de-interlacing removes the comb effect very well even in traditionally difficult scenes (for example, diagonal lines at a small angle, or flying colors ) without much quality losses and blurring."

http://www.digit-life.com/articles2/video/avivo.html

How about you download a trial of Nvidia's video codec, set it to use hardware acceleration, and see if it's in hardware mode in this tab.

http://img230.imageshack.us/img230/73/nvidiakp7.jpg
Link to Picture (http://img230.imageshack.us/img230/73/nvidiakp7.jpg)

Here's the link to the download.
Link (http://www.nvidia.com/object/dvd_decoder_1.02-223-trial.html)

DXVA is Hardware Acceleration, which includes HW Deinterlacing.
You don't need a Nvidia video card to run Nvidia video decoder in DXVA mode.
See the link
Link (http://www.htpcnews.com/forums/index.php?showtopic=20763)

Using the Software I linked to,
Setting the Nvidia Decoder to use Hardware Acceleration,
and Setting FFdshow to use HW Deinterlacing.
The Screen I linked to will tell you if it's in hardware mode.
Meaning if it's in Software Mode, your HW Deinterlacing in the FFdshow output tab isn't working.

You can test this now, you don't need a Nvidia video card to test if dxva is used.

[haruhiko_yamagata]

Would be interested to know what exactly was done in the following revisions:Revision 458 - Directory Listing
Modified Sat Oct 28 00:13:53 2006 UTC (39 hours, 31 minutes ago) by h_yamagata

restart replace for libmpeg2_ff.dll

Revision 447 - Directory Listing
Modified Wed Oct 25 09:13:04 2006 UTC (4 days, 6 hours ago) by h_yamagata

ANSI/MBCS more security fixes

Revision 444 - Directory Listing
Modified Tue Oct 24 13:54:30 2006 UTC (5 days, 1 hour ago) by h_yamagata

Bug fix (ANSI)
ANSI debug build often crashes when we click task tray icons. This affects release build too, and is security issue.


Revision 439 - Directory Listing
Modified Tue Oct 24 11:02:52 2006 UTC (5 days, 4 hours ago) by h_yamagata

Bug fix : Quality control of post processing. It has been depending on CPU usage(performance monitor). Now that I removed the performance monitor related code, it has to be fixed.

Rev458
Supporting beginers have priority on supporting experts.

Rev 444, 447
Unless you use MBCS languages like Japanese, it's hard to reproduce. For more information, please look at the code.

Rev 439
Postprocessing was depending on CPU usage. Now it depends on IQualityControl (Not "Time on ffdshow"). CPU usage was broken, so this is better IMO. It may not be best though. If you are using queue, "Queued samples<8" may be a good try.

[haruhiko_yamagata]

Create two extra presets (besides default).
Enable 'automatic preset loading'.
Preset 1: on FourCC match = DX50;DIVX
Preset 2: on FourCC match = XVID

Now play some DivX and XviD files. The correct preset doesn't get chosen.
Yes. It works for me.

Windows XP sp2, MPC, Zoom Player, AVI, MKV...all settings I have tried is OK.

[haruhiko_yamagata]

Does this mean that if I enable HW Deinterlacing in FFdshow, that my Purevideo certified video card and purevideo codec will use "Motion adapative temporal deinterlacing" ?
If so, why is there a box to choose from bob or weave when I enable HW Deinterlacing in FFdshow ? What's that for ?
I read your links. ffdshow does not force anything to down stream. All is free for down stream's choice anyways.
Bob or Weave may be ignored by Pure video, but usefull in my GPU(i82865G). In my system hardware deinterlacing checed + Weave is same as hardware deinterlacing uncheckd. But it won't be understood by users. Showing Bob or Weave is better UI, I think.

[_xxl]

New bug, when parsing FLV1 (which seems to have no restrictions on resolution) with the OSD turned on, the osd color is overlayed in the wrong (vertical) position when the video resolution is not divisible by 4. This bug does not effect playback (read: ffdshow doesn't crash & no new artifacts).
So a video with a resolution 320x239, the osd color is rendered about 3 pixels higher then the the text.
http://mailerdaemon.home.comcast.net/6SK-bcWCU8w.flv
http://i13.tinypic.com/4d61744.jpg
http://i14.tinypic.com/2gspriq.jpg
YV12 is on.
http://i14.tinypic.com/2itmr9h.jpg
http://i14.tinypic.com/2qkl3py.jpg
YV12 is off.
EDIT:MPC is running in WMR9 (renderless) mode.

[haruhiko_yamagata]

http://i13.tinypic.com/4d61744.jpg
http://i14.tinypic.com/2gspriq.jpg
YV12 is on.

Many video cards says it supports YV12, but actually it does not. It's likely a bug of the video renderer. The problem is YV12 is set by default because it is often the fastest. Some media players test YV12 on install and ask user if it was played properly. Because ffdshow is not a player, there's no way to know if YV12 is actually supported.

Another problem is that the picture has odd number lines. Are picutures with even number lines played back properly?

Turn on post processing for the picture and you'll see another bug - green line at the bottom.

[BlindWanderer]

Wow cool bug drevil, but thats not the one I'm seeing, thought it does only happen for yv12

Also get a line of random pixels (the color is random) across the bottom row in mpc when using rgb15 but thats probably my computer.

http://mailerdaemon.home.comcast.net/snapshot-yv12.jpg

As you can see in the screen shot the the all of the color is higher then it should be (same frame as your clean frame). So you are probably right, suggesting it being my GC. Especial consider that when i resize up to the next multiple of 4 it aligns. (sorry for wasting time)

[cc979]

Many video cards says it supports YV12, but actually it does not. It's likely a bug of the video renderer. The problem is YV12 is set by default because it is often the fastest. Some media players test YV12 on install and ask user if it was played properly. Because ffdshow is not a player, there's no way to know if YV12 is actually supported.

Another problem is that the picture has odd number lines. Are picutures with even number lines played back properly?

Turn on post processing for the picture and you'll see another bug - green line at the bottom.

i've just tested the clip with mine, i get the colour corruption if yv12 is the only output, but plays fine with yuy2 or nv12

[Jeremy Duncan]

Showing Bob or Weave is better UI, I think.

Not everybody knows that weave is the same as film, and bob is the same as video.
I wasn't sure myself until you made it clear.

Maybe change the ui to this:
Film - Deinterlacing Off
Video - Deinterlacing On

[arfster]

Film is different - that means to use IVTC to extract the original 24 progressive frames from 60 interlaced "half-frames" (aka fields) each second.

Bob and weave are just two different methods of deinterlacing, and you only want to be using this on genuine interlaced video content, or on film content where the flags are so thoroughly messed up that the 24fps stream is not really readable.

Regardless of bob/weave in ffdshow, Purevideo will probably ignore it and do its own thing anyway. If it's in film mode, it's working fine and will be producing the correct 24fps.

[Jeremy Duncan]

"Film - Forces film mode and does not apply de-interlacing.

Video - Forces video mode and applies de-interlacing."

Link (http://www.htpcnews.com/forums/index.php?showtopic=20763)

This is how Nvidia catalogs Deinterlacing in the deinterlacing control. Weave is the same as Film, and Bob is the same as video.
See the screen.

http://img230.imageshack.us/img230/73/nvidiakp7.jpg

"DeInterlacing - Weave:
Weave is the default mode that should be used when viewing progressive DVD data (Movies for example). Using this mode you will see horizontal streaking for non-movie data (NTSC/PAL content such as movie trailers or content recorded using interlaced video cameras). If you plan on viewing DVD movies, you must set your decoding software to weave mode. Weave is the default DeInterlacing mode all decoding software use for Movie playback (unless set to some sort of detection mode).

DeInterlacing - BOB:
T.V. playback works a bit differently compared to a computer monitor. It has two fields, each playing in an interlaced form at either 30 or 25fps (NTSC/PAL). When NTSC/PAL content is played on a computer monitor using the standard Weave DeInterlacing mode, you get a lot of horizontal streaking when the camera pans or objects move quickly within a scene. To combat this, you can use the BOB DeInterlacing mode. What BOB does is play the content at twice it's frame rate and each frame is displayed in only one of the fields. This makes the image appear to BOB up and down a bit, especially when text is displayed, but doing so eliminates the streaking. Using the BOB mode is only useful for NTSC/PAL content such as Movie Trailers. On Progressively encoded Movie content BOB will cause the image to look slightly blurred."

Link (http://terms.inmatrix.com/)

"Weave works perfectly for progressive sourced1080i (from film). But for true interlaced 1080i, only bob is an option, and it only provides 540 lines of vertical resolution from 1080i video source."
Link (http://www.avsforum.com/avs-vb/showthread.php?p=6221665&highlight=weave+bob#post6221665)

Weave is for Film, Bob for Video/T.V.

I wasn't sure if setting FFdshow's HW Deinterlacer to Weave did anything until haruhiko_yamagata made it clear what it did.

I think a hint beside the bob and weave option would make it easier to use properly.

[Liisachan]

@arfster
just to make it clear... I think you are assuming NTSC, while european films (European R2 DVDs) are 25fps (PAL). Many of the ppl here should be europeans...

[arfster]

"Film - Forces film mode and does not apply de-interlacing.


This is the key quote. Weaving is a type of deinterlacing, and in film mode (as above) you don't de-interlace, you IVTC if at all possible.

Certainly you can apply deinterlacing, whether bob or weave, to interlaced content (1080i or DVD) with IVTC flags, but it won't look as good as setting film mode. Remember, the original content is 24fps, which film mode can retrieve losslessly. Deinterlacing will only result in 30 weaved frames, or 60 bobbed ones - neither are the original video, but a processed reconstruction of it with resultant artifacts.

See the telecine graphic here:

http://www.doom9.org/ivtc-tut.htm

Weaving will mix half of frame 2, with half of frame 3, and 3/4 in the same way. Messy if there's any movement in between, and juddery. Bob will scale the half-frames into separate full frames, and thus lower detail. True film mode IVTC will rebuild the original 4 frames perfectly.



Liisachan: yes, this was for NTSC. Obviously PAL is a lot simpler with 50>25fps, rather than 60>24.

[Jeremy Duncan]

In most cases Weave is same as unchecked hardware deinterlacing.

Weaving is a type of deinterlacing...


This is where I was confused.
Because I thought that weaving was deinterlacing, like Arfster said in the quote.
But when haruhiko_yamagata said weave was the same as no hardware deinterlacing, I took it that no hardware deinterlacing meant there was no software deinterlacing either, which meant it was film.
So I suggested that Weave, and Bob should have a hint or be called something else to show that weave was the same as no deinterlacing.

As I understand it, haruhiko_yamagata said that Weave and Bob sent hints that enabled or disabled hardware deinterlacing, that they were called weave and bob wasn't important.
If hardware deinterlacing was enabled by selecting Bob, the hardware deinterlacing wouldn't nessessarily be bob deinterlacing, it could be spatial-temporal deinterlacing.

[haruhiko_yamagata]

This is where I was confused.
Because I thought that weaving was deinterlacing, like Arfster said in the quote.
But when haruhiko_yamagata said weave was the same as no hardware deinterlacing, I took it that no hardware deinterlacing meant there was no software deinterlacing either, which meant it was film.
So I suggested that Weave, and Bob should have a hint or be called something else to show that weave was the same as no deinterlacing.

As I understand it, haruhiko_yamagata said that Weave and Bob sent hints that enabled or disabled hardware deinterlacing, that they were called weave and bob wasn't important.
If hardware deinterlacing was enabled by selecting Bob, the hardware deinterlacing wouldn't nessessarily be bob deinterlacing, it could be spatial-temporal deinterlacing.
Weave is a simple deinterlacing method.
If weave is selected, ffdshow say to the down stream "deinterlace this in Weave mode". But usually this is same as saying nothing(HW deinterlacing is unchecked). If ffdshow says nothing to down stream, I guess, down stream can find the samples are interlaced and try to deinterlace in weave mode. That's why the result is the same, if I'm not wrong.

[Egh]

This is where I was confused.
Because I thought that weaving was deinterlacing, like Arfster said in the quote.
But when haruhiko_yamagata said weave was the same as no hardware deinterlacing, I took it that no hardware deinterlacing meant there was no software deinterlacing either, which meant it was film.
So I suggested that Weave, and Bob should have a hint or be called something else to show that weave was the same as no deinterlacing.


It's just a bit of methodology confusion here :)


Deinterlacing is the process of converting interlaced video (a sequence of fields) into a non-interlaced form (a sequence of frames). This is a fundamentally impossible process that must always produce some image degradation, since it ideally requires "temporal interpolation" which involves guessing the movement of every object in the image and applying motion correction to every object.


Weave is a straightforward conversion from interlaced video stream (i.e. sequence of fiels=halfframes) to progressive one (sequence of full frames). Weave effectively pairs adjacent halfframes into full ones, thus if there's any fast movement you'll see combing artefacts (cause in *real* interlaced stream adjacent fields are taken at slightly different times). But in theoretical cases, for instance if you have 12fps progressive duplicated into 24fps, fastened to 25fps and then interlaced into
50 fields per sec, then weave would fully recover original stream.

To sum up, weave is deinterlacing, but just creates too much motion artefacts in practice.

[vlada]

I think here is a confusion which is caused because of PAL and NTSC differences.

If your movie is PAL, you have 2 possibilities:
25 progressive frames (uses Weave = do nothing) or 50 interlaced fields (deinterlace).

For NTSC you have 3 possible types:
30 frames progressive (probably not very common, Weave), 60 interlaced fields (deinterlace) and 60 telecined fields (inverse telecine -> output 24 fps).

Anyway BOB is not a very good method for deinterlacing. It creates a smooth video, but static objects loose resolution. The best solution is to sombine BOB and WEAVE in each frame. Use BOB for moving parts and WEAVE for static picture. Most good deinterlace filters are doing it this way.

If you're interested some time ago I did a test to compare different deinterlace algorithms. You can find it here (http://jech2.webz.cz/gallery/thumbnails.php?album=4). Have a look at the sign in bottom left corner. It perfectly shows the lost resolution when using BOB.

Also I wouldn't even call Weave deinterlacing. Any PC monitor/PDP/LCD/projector only displays video progressively. So you can't display interlaced video on it. Weave means that you just combine two fields into one frame. You can't separate them back into fields whenever you want. It is just a method of how the fields are stored or displayed. There is no processing of the video.

[FredThompson]

...at least it is for ffdshow_rev457_20061027_clsid...

Here's a short video and frame grab to show the problem. Yellow looks teal with ffdshow's decoder.

This was encoded with the GZip option at level 9 for maximum compression.

As a side note: I'm not sure if CamCodec has proper indexing or not. Loading its files into VirtualDub shows those created by CamStudio don't have indexing data. Sure would be nice if this were added, especially since CamStudio will allow ffdshow to be the encoder. As it is, CamCodec stuff really needs to be saved to another format for editing use.

[Wilbert]

Anyway BOB is not a very good method for deinterlacing. It creates a smooth video, but static objects loose resolution.
Why ...?

[haruhiko_yamagata]

http://i12.tinypic.com/2igg4lu.jpg
I'm trying to expand the dialong.
The upper sample is the original, the next is the new one.
What do you think about the size?

[MacAddict]

Personally I like the new dialog.

[Jeremy Duncan]

The new Dialong looks nice.

[haruhiko_yamagata]

Thank you. I commited resized dialog. Please see if it works.

[MatMaul]

I have made a little test to mesure the h264 decoding speed improvement.

ffdshow rev2546 : 104 fps
ffdshow-tryout rev494 : 130 fps (!!)

+25% speed-up !!

Great job and thanks to ffmpeg guys !