rougher edges than in the original...

[Weef]

o.O looks now far more like the original ...but it's already too late - I could be wrong - my eyes are tired will check this tomorrow

[jagabo]

o.O looks now far more like the original ...but it's already too late - I could be wrong - my eyes are tired will check this tomorrow

That's why VirtualDub has the zoom feature on the input and output panes.

[Weef]

I dunno...perhaps I'm just too critical with the output I'm generating... but what I will try is to deinterlace to not mess the lines

As reply...can't use the zoom feature cuz I only have a normal 1280x1024 screen - had to open two times Vdub to make comparisons - and that's not the best way

[Weef]

I take everything back! It is Premiere that is causing this!!

Look at these two pictures

The first one is the uncompressed first output of Vdub!

The second one is the uncompressed output of Premiere!!!

But what now - no more cutting in Premiere?? o.O

[poisondeathray]

As mentioned earlier, Premiere has a crappy deinterlacer and resizer

But your comments still don't add up.

If the original was interlaced, the 1st shot should out of vdub show combing (aliasing) if it was unprocessed in vdub (no filters) . If the orignal was progressive content encoded as interlaced, then it was likely a setting mismatch in premiere. Eitherway, there are ways to make everything work properly

[Weef]

Well as said the only one filter was the resizing in the 1st step in Vdub

I will try it out right away^^

[poisondeathray]

I asked earlier a few times if the left side was the export from premiere and you said "yup"

You've made several errors in this thread in conveying information . Nobody can help you if you can't report what's happening properly or can't keep things in order.

And I don't mean to be rude, but that is the reason why earlier I said I didn't believe you - because there were so many inconsistencies. You're just wasting everyone's time.

I'll give you another big hint: you won't be able to do anything properly, until you determine the nature of the original source first. ie. is it progressive or interlaced content .

[Weef]

Guess it was just too late already...

Didn't mediainfo say it was Interlaced Top Field first?

[poisondeathray]

mediainfo only reports the header information . It doesn't tell you about the actual content. It can be progressive encoded as interlaced for example, or interlaced encoded as interlaced. For example, if it's progressive, encoded as interlaced, then premiere will wrongly think it's interlaced and try to deinterlace or separate fields.

here is a guide for determining the nature of the content
http://neuron2.net/faq.html#analysis

[Weef]

Well is that the whole code there? Seems to be missing something.
The only thing I've found in this direction is this : http://avisynth.org/mediawiki/Interlace_detection#AviSynth_field-order_script

Are u fit in this? I'm not

[poisondeathray]

Those are all the steps, did you follow them ? Is the original interlaced or progressive content ? That determines what steps you take next , what settings to use in premiere, everything. If you get the 1st step wrong, everything else will be wrong.

[jagabo]

The jagged edges come from (poorly) deinterlacing a video that is not interlaced. If your source is 23.976 fps progressive MPEG2 with 3:2 pulldown flags use DgIndex in Forced Film mode to produce an index file, then Mpeg2Source() in AviSynth to open that index. If the video is a 23.976 fps film source with hard pulldown use Honor Pulldown Flags in DgIndex, Mpeg2Source() followed by your favorite IVTC filter (I recommend TFM().TDecimate()). That will restore the original progressive film frames. If your video is true 29.97 fps interlaced (and you really need to deinterlace) use whatever detinerlacer you want. Most don't work really well with animated sources. TempGaussMC_beta1mod() is one of the best deinterlacers but it is very slow. Yadif() is often adequate.

[Weef]

Well, it's PAL...

[jagabo]

Then you can rule out the 3:2 pulldown options. You have three main source types:

1) progressive frames encoded as progressive
2) progressive frames encoded as interlaced (including out-of-phase fields)
3) interlaced frames encoded as interlaced

Situations 1 and 2 don't require deinterlacing.

Situation 2 does require special handling of the chroma channels. Out of phase caps (individual fields come from two consecutive progressive frames rather than both from the same frame) can be fixed by re-aligning the fields.

Situation 3 may require deinterlacing depending on your intended viewing device. As you have seen, Premiere has a very poor deinterlacer. It looks like it simply throws out one field (reducing a 720x576 frame to 720x288) then resizes the remaining field back to the original size. This results in the jaggie edges in your sample. There are better deinterlacers in AviSynth. TempGaussMC_beta1mod() is very good but also very slow. Yadif() is pretty fast and usually pretty acceptable.

Situation 3 also includes NTSC-to-PAL conversions that have field blending. The field blending can be removed with filters like RePal() or SRestore().

[Weef]

I got now two versions

this is the one with ignored pulldown

It was corrected, because of a wrong order

D2V Fix Output
Field order transition: 3 -> 2
900 5 2 716355584 0 1 7 92 b2 b2 a2 b2 b2 a2 b2 b2 a2 b2 b2 a2
900 5 2 716695552 0 1 7 92 b2 b2 a2 b2 b2 a2 b2 bcorrected...
900 5 2 716355584 0 1 7 92 b2 b2 a2 b2 b2 a2 b2 b2 a2 b2 b2 a2
900 5 2 716695552 0 1 7 92 b2 b2 a2 b2 b2 a2 b2 b2 a2 b2 b2 a2

Uhm, so... by the links I can't interprete this...

[jagabo]

That doesn't really tell you whether the source needs deinterlacing. Use DgIndex to demux a short sample of the MPG/VOB file (a sample with a moderate amount of motion) and upload it.

[Weef]

Long enough? DGIndex doesn't seem to be happy if I simply cut out things.

[jagabo]

That clip is encoded interlaced but it's hard to say if the frames are progressive or interlaced since there's hardly any motion and the clip is too short. But it looks to be progressive frames.

What you should understand: interlaced frames contain two separate half pictures, called fields. One field in all the odd numbered scanlines, the other in all the even numbered scanline. When a video is encoded interlaced the encoder essentially separates the two half pictures and encodes them as separate pictures. Of course, progressive frames also contain two fields, they are just complimentary portions of the same frame. But these can be encoded progressive (each frame is encoded as a single picture) or as if they were interlaced (again, the encoder separates the two fields and encodes them as two separate pictures).

[Weef]

Okay, now a bigger sequence but I can't extract it directly since DGIndex is refusing it. So this is the extract of the already demuxed file.

The first rar file holds the option with honor pulldown.

The other one with ignored option.

[Weef]

http://rapidshare.com/files/413438071/VTS_01_1o.demuxed.demuxed.m2v

this is the one with the ignored option

[jagabo]

That clip had all progressive frames, encoded interlaced. It doesn't need to be deinterlaced.

By the way, the pulldown flags option has no effect on the demuxed m2v file. The m2v file is a direct copy of the original MPEG data.

[Weef]

Hmm, sounds like you can encode not only the frames interlaced - but what ?.?

[manono]

Hmm, sounds like you can encode not only the frames interlaced - but what ?.?

That sentence makes no sense. It's typical of PAL stuff - a progressive source encoded as interlaced. You already saw what's likely to happen if you deinterlace something like that. So, don't deinterlace it and when reencoding it, encode it as progressive.

[Weef]

I did not deinterlace... at least not willingly

Far more intersting now - when it's progressive material can I use the simple resize filter for a new size since it are no lines I have to take care of?

[poisondeathray]

Yes, you can resize it normally. Likely what happened is you used premiere incorrectly (wrong sequence settings, or export settings)

[Weef]

I agree^^ thanks or your patience help xP
Couldn't have a better place for my encoding questions^^