Telecide Settings

[bagheera1]

I have recently discovered that the post=0 option dose not seem to disable post processing (I am using ver 5.22 of decomb.dll), by that I mean Telecide(post=0) still deinterlaces.

Did I not understand the documentation correctly?

[Guest]

I have recently discovered that the post=0 option dose not seem to disable post processing (I am using ver 5.22 of decomb.dll), by that I mean Telecide(post=0) still deinterlaces. That's just not true. What makes you think that?

[bagheera1]

When I use this script:

aviSource("\\Jim-and-renee\d\Video\Capture\test.avi")
AssumetFF()
Telecide(post=0)

with and without the Telecide line commented, my output is interlaced respectivly.

[foxyshadis]

Well, you do know that the whole reason you use Telecide is to rematch fields, which looks like interlacing if you don't know the difference, right? If the fields are all matched correctly and precisely there should be no combs left. If it's a true interlaced source it'll attempt to match fields and thus remove some interlacing, but obviously not all and not very well.

[bagheera1]

Well, you do know that the whole reason you use Telecide is to rematch fields, which looks like interlacing if you don't know the difference, right? If the fields are all matched correctly and precisely there should be no combs left. If it's a true interlaced source it'll attempt to match fields and thus remove some interlacing, but obviously not all and not very well.


I'm not sure I understand your post. Perhaps I should have said "combed frames" instead of "interlaced". I will elaborate.

The frame sequence is (with Telecide commented out) 3 clean frames followed by 2 combed frames. With Telecide(post=0), 4 clean frames followed by 1 duplicate of the 4th frame.

My Question was reguarding the documentation:

DecombReferenceManual.html#telecide

"post (0-5, default 2) controls whether and how Telecide performs postprocessing to clean up frames that come through the field-matching still combed:

post=0: Use this to totally disable postprocessing.
post=1: Use this to enable the metrics calculation and to display the vmetric values but not perform deinterlacing.
post=2: Use this to enable deinterlacing. Note that in this mode, the field matching occurs normally and the best matched frame is deinterlaced and delivered.
post=3: This is the same as post=2 except that the deinterlacing motion map is displayed in white on the deinterlaced frames.
post=4: This is the same as post=2 except that instead of using the best field match for the frame, the original frame is deinterlaced. You would use this to pass video sequences through when you have a hybrid clip.
post=5: This is the same as post=4 except that the deinterlacing motion map is displayed in white on the deinterlaced frames. "


My interpretation of "post=0" was that no deinterlacing would occur.

[berrinam]

That's right. None did occur. Instead, the fields were rearranged so that the combing disappeared (this process is called field matching). Deinterlacing is different: it creates new fields which don't display combing.

If you still want the combing, then leave Telecide out altogether.

PS. There's a reason that Telecide is part of the Decomb package.

[bagheera1]

That's right. None did occur. Instead, the fields were rearranged so that the combing disappeared (this process is called field matching). Deinterlacing is different: it creates new fields which don't display combing.

If you still want the combing, then leave Telecide out altogether.

PS. There's a reason that Telecide is part of the Decomb package.
I believe I was assuming that deinterlacing was a procedure that occured as a result of the "field matching" analysis.

Your post clarifies things somewhat. The reason for this thread came from the documentation for LeakKernelDeint, and me playing with different settings.

Thank You, I believe things are making more sense now.

[Wilbert]

@bagheera1,

If you convert your attachments to jpeg i will approve them if it is still necessary.

[Guest]

Telecide does two things. First, it tries to match up the fields. If the material is cleanly pulled-down, this may remove all combing in the output, so that you would see no combed frames even with post=0. Second, you can apply a deinterlacer to the output of the field matching. That is designed to decomb any frames that were not able to be field matched properly. It is just this last process that is controlled by the post option.