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. |
13th August 2002, 12:52 | #1 | Link | |
Registered User
Join Date: Apr 2002
Posts: 272
|
assumetff() assumebff()
Quote:
are they just short hand for separatefields / complementparity? or do they do something else? |
|
13th August 2002, 14:49 | #2 | Link |
C64
Join Date: Apr 2002
Location: Austria
Posts: 830
|
The actual docu can be seen at sourceforge (of course work is still in progress!)
CVS-DOCU and of course at The AviSynth Homepage Those two commands SET the fieldorder rather than change it and don't separate fields. Last edited by WarpEnterprises; 13th August 2002 at 15:32. |
16th October 2019, 18:27 | #4 | Link | |
Join Date: Mar 2006
Location: Barcelona
Posts: 5,034
|
Quote:
__________________
Groucho's Avisynth Stuff |
|
16th October 2019, 20:28 | #5 | Link |
Registered User
Join Date: Feb 2002
Location: California
Posts: 2,695
|
I don't quite understand what problem you are having.
All the AsssumeBFF/AssumeTFF statements do is to override whatever assumption AVISynth makes about field order. Some video provides this information to the video program, and some does not. Sometimes the information provided is wrong. So, what the Assume functions do is to force AVISynth to read the fields in the order specified, regardless of what AVISynth is told by the video header. To test whether you have the Assume function set correctly, I recommend opening your video in this script: AssumeTFF() Separatefields() Open this script in VirtualDub and walk through the video one field at a time (you are looking at fields, not frames). If the motion looks normal, you have got the right Assume function. However, if the video goes back and forth, you have it set the wrong way. The back and forth motion gives you some idea of how screwed up your script can get if you don't have this set correctly. I perform this test on every single interlaced video that anyone gives to me, because field orders are ALWAYS getting screwed up by people who don't know what they're doing. Last edited by johnmeyer; 16th October 2019 at 21:49. Reason: clarity |
17th October 2019, 17:23 | #7 | Link |
Registered User
Join Date: Feb 2002
Location: California
Posts: 2,695
|
You're in the broadcast business and what amazes me, fifteen years after the HD switchover, is how often I see massive field reversal artifacts on SD material incorporated into a program. It appears that engineers at local stations don't know how to handle field dominance changes.
|
19th October 2019, 12:32 | #8 | Link |
Registered User
Join Date: Sep 2004
Posts: 217
|
Try AssumeTFF() first and scrub the video through parts with motion. If the video jerks back and forward have bff video and should use AsuumeBFF(). In any case to confirm that you are right try the opposite function and look for jerky video in parts with motion.
__________________
Specs: Intel Core 2 Quad Q6600(4*2.4GHz), Win XP Pro SP2, 2 Gb DDR2, 1*120Gb HDD, 1*500Gb HDD |
19th October 2019, 13:09 | #9 | Link | |
Join Date: Mar 2006
Location: Barcelona
Posts: 5,034
|
Quote:
__________________
Groucho's Avisynth Stuff |
|
Thread Tools | Search this Thread |
Display Modes | |
|
|