ReverseFieldDominance

[Coqrogue]

Ok, ran in to some confusion again when encoding a sitcom episode captured from a TV broadcast.
It seems like it was aired progressive and I still had the occasional ghosting in the picture (though it only happened a few times) and the subtitles flickered everytime they changed so they seemed to be aired interlaced.
When using the ReverseFieldDominance() filter should I have that first in order after the AVISource("clip.avi")?
I had the ReverseFieldDominance() filter last in the chain...
When I load the ReverseFieldDominance plugin should I do that by using LoadPlugin or can I skip that?
It looks okay in the script editor in VirtualDubMod and it seems to be working alright without me doing it...

Can I assume that my capture card always captures with the top-field first or can it change from capture to capture?
And if I have to check every capture if it's top or bottom field dominant, how do I do that correctly?

I use this method to determine the field dominance:

AssumeFrameBased
SeparateFields
#complementparity #bottomfield first

AssumeFrameBased
Separatefields
complementparity #top-field first

But sometimes I can't see any difference, which I think is strange.

I hope I make sense :)
/C

[stickboy]

Ok, ran in to some confusion again when encoding a sitcom episode captured from a TV broadcast.
It seems like it was aired progressive and I still had the occasional ghosting in the picture (though it only happened a few times) and the subtitles flickered everytime they changed so they seemed to be aired interlaced.You can easily check that by inspecting the frames with the subtitles.
When using the ReverseFieldDominance() filter should I have that first in order after the AVISource("clip.avi")?
I had the ReverseFieldDominance() filter last in the chain...It shouldn't really matter.
When I load the ReverseFieldDominance plugin should I do that by using LoadPlugin or can I skip that?Either you can load the plugin via AviSynth's autoloading mechanism or you can load it manually with LoadPlugin. You don't need both.
Can I assume that my capture card always captures with the top-field first or can it change from capture to capture?AFAIK, it should be consistent.

(Why did you start a new thread instead of updating your earlier one (http://forum.doom9.org/showthread.php?t=108709)?)

[Guest]

It shouldn't really matter. It could matter if a downstream filter needs a certain field order to work properly.

[stickboy]

It could matter if a downstream filter needs a certain field order to work properly.Theoretically, sure, but filters shouldn't behave that way, right?

[Guest]

Theoretically, sure, but filters shouldn't behave that way, right? TDeint, KernelDeint(), Telecide()... Need I go on? :)

Anyway, as long as you allow for the field dominance reversal by giving proper parameters to the filters, it doesn't really matter, as you say.

[stickboy]

TDeint, KernelDeint(), Telecide()... Need I go on? :)

Anyway, as long as you allow for the field dominance reversal by giving proper parameters to the filters, it doesn't really matter, as you say.Right, none of those filters should require BFF (or TFF) input; they should care only that the field-order is set properly. Inverting the field dominance (as opposed to using ComplementParity) won't fix anything; if the field order is initially wrong, it'll still be wrong.

[Coqrogue]

You can easily check that by inspecting the frames with the subtitles.
It shouldn't really matter.
Either you can load the plugin via AviSynth's autoloading mechanism or you can load it manually with LoadPlugin. You don't need both.
AFAIK, it should be consistent.

(Why did you start a new thread instead of updating your earlier one (http://forum.doom9.org/showthread.php?t=108709)?)
Good point...:o

----------------

Thank you all for your input and in the future I'll be more careful about how I handle my threads, I understand it's annoying having multiple threads about the same issue.:)

I wrote a new script and now things are looking good again, though the subtitles are still flickering a little bit, or maybe I should describe it as jumping slightly up and down in a very fast rapid movement, almost as if the interlaced fields are actually visible.
But I have seen this behaviour on TV broadcasts too so not event they are perfect.
Anyway, is there anything I can do about this in the post-processing?

/C

[Boulder]

Have you tried something like FieldDeinterlace(full=false,threshold=100)? I use that on my progressive TV captures that have interlaced subtitles on them.

[Coqrogue]

Have you tried something like FieldDeinterlace(full=false,threshold=100)? I use that on my progressive TV captures that have interlaced subtitles on them.

No, I haven't, but I'm gonna give it a try.
Thanks.:)

[Coqrogue]

Ok, sat down and edited the whole hockey game and the fields where messed up again, even though I used ReverseFieldDominance.
When I tried both the Avisynth and VirtualDub versions on short clips from the hockey game a few days ago everything worked perfectly.
Does the lenght of the clip matter?
The test clips were only about 30 seconds long and the whole game edited where about 1 hour and 45 minutes.
Also, when I captured the hockey game I used PicVideo MJPEG codec, since I was short of disc space, and when I edited the game I used Huffyuv to preserve quality as much as I could. Can this be the cause?
I used LoadPlugin to load the ReverseFieldDominance filter.

---------------

On another note: Can I move my other thread to this one since they deal with the same issues?