Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. |
|
|
Thread Tools | Search this Thread | Display Modes |
11th March 2006, 22:05 | #1 | Link | |
Registered User
Join Date: May 2004
Posts: 128
|
New Avisynth Telecide Procedures To Determine Shifted Fields or Interlacing
Hi there.
Manano had a brilliant method to determine whether your video source has the shifted field problem or if it is indeed truly interlaced. Quote:
try using Telecide(Post=false) and opening in Virtualdub I get: Script error: the named argument "Post" to Telecide had the wrong type. When I try using Telecide() and opening in virtualdub : Telecide : you must specify the order parameter (0=bff, 1=tff). An incorrect setting will result in incorrect decombing. Basically what I am asking, is what is the New Avisynth procedure to determine whether your video source has the shifted fields problem or it is interlaced. Thanks Heaps |
|
12th March 2006, 01:00 | #2 | Link | |
Registered User
Join Date: Dec 2004
Location: Melbourne, AU
Posts: 1,963
|
The post option is no longer true or false, it's a numerical value. So the equivalent to post=false would be post=0.
Additionally telecide has a new paramter: order. This parameter MUST always be given. Order=0 means the material is bottom field first, while order=1 means top field first. For determining which is correct for your clip, try this (taken from telecide's tutorial): Quote:
|
|
15th March 2006, 11:26 | #5 | Link |
Registered User
Join Date: May 2004
Posts: 128
|
Thanks for your reply guys!
When viewing a PAL possibly Field Shifted DVD Frame by frame, what does it look like? I have no idea if I am seeing Interlacing or otherwise Is this right? (I write two separate scripts) If I write AssumeTFF() Telecide() on one script and AssumeBFF() Telecide() on the other. If in both cases I still see interlacing when I preview in virtualdub, does that mean I have a pure interlaced source? And if one of those scripts does appear to remove interlacing, then it is a case of shifted fields? Thanks Again! Last edited by Staz; 15th March 2006 at 11:31. |
23rd March 2006, 11:08 | #6 | Link | |
Registered User
Join Date: May 2004
Posts: 128
|
On my quest to finally get my head around all of this I found this from manono:
Quote:
In this bit: "2. Make a .d2v with Field Operation-Swap Field Order." In DGIndex I don't see "Swap field order" as one of the field operation options. (just honor, ignore and force film). Where can I swap field order in DGIndex? I like this method: "But you can actually skip steps 2 and 3 by adding Telecide() to the script if it doesn't look good after step 1." If it looks ok after adding Telecide() to my script then does it mean I had a case of shifted fields and there is no need to deinterlace?? Also do I have to add AssumeTTF() or AssumeBBF() first? I have no idea how these work, can anybody explain? It would be great if I could get my head around this once and for all. Thanks heaps! Would be great to hear from you Manono as you seem to have an amazing knowledge in this area |
|
24th March 2006, 02:34 | #7 | Link | |
Guest
Join Date: Jan 2002
Posts: 21,901
|
Quote:
Here's how to tell if you have field shifting or real interlacing: Make your project as "Honor pulldown flags". Then make an AVS to step through the fields. mpeg2source("file.d2v") assumeTFF() # or assumeBFF(). Get the field order from DGIndex's Tools/Parse D2V. separatefields() Serve this into VirtualDub and step through the fields in a high motion section. Denote a new picture with a new letter. If you see a repeating field sequence like this: ... a a b b c c ... then it is progressive video. If you see this: ... a b c d e f ... then it is pure interlaced video. If you see this: ... a a a b b c c c d d ... Then it is hard 3:2 pulled-down progressive video. Make sure that you always apply this test in a scene with continuous movement, e.g., an object moving steadily across the screen. There is no more reliable way. It also allows you to spot field blending very easily. If you see any blended pictures, then you have field blending. I don't like the idea of resizing to full height for this process, because we can forget that we are looking at fields, and any extra processing is superfluous in any case. OK, the fields jump up and down but so what? It lets us directly know the field polarity. Last edited by Guest; 24th March 2006 at 02:56. |
|
30th March 2006, 02:04 | #8 | Link |
Registered User
Join Date: May 2004
Posts: 128
|
Wow Neuron2!
That guide is brilliant thanks. When following your method of SeparateFields each frame of my test video contained a new picture (eg: a car progressively moving further left across the video), implying that it was interlaced. The method you wrote works fine for PAL sources right? NTSC too? Does anybody have any examples as to what field blending looks like? Thanks heaps! Last edited by Staz; 30th March 2006 at 02:15. |
25th March 2009, 20:10 | #10 | Link |
Derek Prestegard IRL
Join Date: Nov 2003
Location: Los Angeles
Posts: 5,988
|
@Staz:
Field Blending will be quite obvious if you do SeparateFields() and step through the video. Some (or all) pictures/fields will have blended motion in them. It will look like two images blended together no simpler way to explain it! ~MiSfit
__________________
These are all my personal statements, not those of my employer :) |
Thread Tools | Search this Thread |
Display Modes | |
|
|