progressive looks like interlaced???

[DvdKhl]

I've read already some interlace-Guides, so I can say that I understand the most of it (I hope:D)

I had very long and hard time, working out what the best way to deinterlaced my Movie is.
After much testing I still couldn't get rid of all interlace artifacts. That was very annoying!

Then I noticed something that I couldn't explain but a very pleasuring thing.
After I played around with:
AssumeFieldBased()
SeparateFields()
Weave()

After I included this in my script (in that order) and put the deinterlacer from the script.
The Movie is progressive!!!
Why? :confused:
Because If I understand the 3 commands right it should
1. Tell Avisynth that the source is Fieldbased
2. Separate the Field (double the amount of Frames with half of the height)
3. Interleave the fields again to one Frame
So the last two commands are useless if nothing happens between them.
Then I deleted the last two commands (to look if I'm right)
It was interlaced again.

I'm now going to test the script without the AssumeFieldBased()
and look if it still works.
(Not I would bother :D, but I would like to know.)

[Wilbert]

Could you try

SwapFields()

does that also work? If yes then the fields are somehow swapped when using SeparateFields.Weave.

[DvdKhl]

Thx For your fast reply! :)

I tried SwapFields() it does work but only when I first put AssumeFieldBased() in it.
(So the fields were wrong)

But I noticed something else... (nothing to do with interlace)
I took a picture and zoomed in so I could see the pixels.
Then I noticed that I could reduce the height by 2 without any quality degradtion.
Example: (every digit is a pixel. A same digit is a same pixel)
12345...
12345...
67890...
67890...
So It might be possible to raise the encoding speed without any quality loss.

Sorry for to be a little off-topic but I didn't want to start a new one for it.