Parity - Revision history

Reel.Deal: add link to avs+ documentation

2022-09-17T07:50:42Z

add link to avs+ documentation

Raffriff42: formatting, links, phrasing

2016-02-27T22:55:47Z

formatting, links, phrasing

Raffriff42: added category

2015-11-08T15:09:20Z

added category

Admin: 1 revision

2013-05-09T15:02:24Z

1 revision

82.236.6.49: /* ComplementParity */ Mentioned only the parity flags are changed, not the field content

2012-03-03T21:49:10Z

‎ComplementParity: Mentioned only the parity flags are changed, not the field content

New page

__FORCETOC__

=== AssumeFieldBased / AssumeFrameBased ===

{{Template:Func2Def|AssumeFieldBased(clip ''clip'')|AssumeFrameBased(clip ''clip'')}}

AviSynth keeps track of whether a given clip is field-based or frame-based. If the clip is field-based it also keeps track of the parity of each field (that is, whether it's the top or the bottom field of a frame). If the clip is frame-based it keeps track of the dominant field in each frame (that is, which field in the frame comes first when they are separated).

However, this information isn't necessarily correct, because field information usually isn't stored in video files and AviSynth's source filters just guess at it. AssumeFrameBased and AssumeFieldBased let you tell AviSynth the correct type of a clip.

AssumeFrameBased throws away the existing information and assumes that the clip is frame-based, with the bottom (even) field dominant in each frame. (This happens to be what the source filters guess.) If you want the top field dominant, use ComplementParity afterwards.

AssumeFieldBased throws away the existing information and assumes that the clip is field-based, with the even-numbered fields being bottom fields and the odd-numbered fields being top fields. If you want it the other way around, use ComplementParity afterwards.

=== AssumeBFF / AssumeTFF ===

{{Template:Func2Def|AssumeTFF(clip ''clip'')|AssumeBFF(clip ''clip'')}}

Introduced in v2.0.4.

AviSynth keeps track of whether a given clip is field-based or frame-based. If the clip is field-based it also keeps track of the parity of each field (that is, whether it's the top or the bottom field of a frame). If the clip is frame-based it keeps track of the dominant field in each frame (that is, which field in the frame comes first when they're separated).

However, this information isn't necessarily correct, because field information usually isn't stored in video files and AviSynth's source filters just normally default to assuming bottom field first (with the exception of the MPEG2Source plugin which gets it right!). AssumeTFF and AssumeBFF let you explicity tell AviSynth what you believe the field order type a clip is.

AssumeTFF and AssumeBFF do not change the actual field order, just the internal state flags in AviSynth relating to the source clip used.

'''Examples:'''

[[AviSource]]("test.avi")
AssumeTFF()
[[SeparateFields]]()

will always return the top field of the first frame followed by the bottom field of the first frame and so on.

AviSource("test.avi")
AssumeBFF()
SeparateFields()

will always return the bottom field of the first frame followed by the top field of the first frame and so on.

=== ComplementParity ===

{{Template:FuncDef|ComplementParity(clip ''clip'')}}

If the input clip is field-based, ComplementParity changes top fields to bottom fields and vice-versa. If the input clip is frame-based, it changes each frame's dominant field (bottom-dominant to top-dominant and vice-versa).

Like AssumeBFF and AssumeTFF, ComplementParity does not change the actual field order, just the internal state flags in AviSynth relating to the source clip used.

[[Category:Internal filters]]

← Older revision		Revision as of 07:50, 17 September 2022
Line 1:		Line 1:
		+	<div {{BlueBox2\|40\|0\|3px solid purple}} >
		+	{{AvsPlusFullname}}<br>
		+	Up-to-date documentation: [https://avisynthplus.readthedocs.io/en/latest/avisynthdoc/corefilters/parity.html https://avisynthplus.readthedocs.io]
		+	</div>
		+
		+
	__TOC__		__TOC__

← Older revision		Revision as of 15:09, 8 November 2015
Line 51:		Line 51:

	[[Category:Internal filters]]		[[Category:Internal filters]]
		+	[[Category:Interlace_Filters]]

@@ Line 1: / Line 1: @@
-__FORCETOC__
+__TOC__
-{{Template:Func2Def|AssumeFieldBased(clip ''clip'')|AssumeFrameBased(clip ''clip'')}}
+<div style="max-width:62em" >
-AviSynth keeps track of whether a given clip is field-based or frame-based. If the clip is field-based it also keeps track of the parity of each field (that is, whether it's the top or the bottom field of a frame). If the clip is frame-based it keeps track of the dominant field in each frame (that is, which field in the frame comes first when they are separated).
+AviSynth keeps track of whether a given clip is ''field-based'' or ''frame-based''. If the clip is field-based it also keeps track of the ''parity'' of each field &ndash; that is, whether it's the top or the bottom field. If the clip is frame-based it keeps track of the ''dominant field'' in each frame &ndash; that is, which field in the frame comes first when they are separated.
-However, this information isn't necessarily correct, because field information usually isn't stored in video files and AviSynth's source filters just guess at it. AssumeFrameBased and AssumeFieldBased let you tell AviSynth the correct type of a clip.
+However, this information isn't necessarily correct, because field information usually isn't stored in video files and AviSynth's source filters just guess at it. '''AssumeFrameBased''' and '''AssumeFieldBased''' let you tell AviSynth the correct type of a clip.
-AssumeFrameBased throws away the existing information and assumes that the clip is frame-based, with the bottom (even) field dominant in each frame. (This happens to be what the source filters guess.) If you want the top field dominant, use ComplementParity afterwards.
+'''AssumeFrameBased''' throws away the existing information and assumes that the clip is frame-based, with the bottom (even) field dominant in each frame. This happens to be what the source filters guess. If you want the top field dominant, use '''ComplementParity''' afterwards.
-AssumeFieldBased throws away the existing information and assumes that the clip is field-based, with the even-numbered fields being bottom fields and the odd-numbered fields being top fields. If you want it the other way around, use ComplementParity afterwards.
+'''AssumeFieldBased''' throws away the existing information and assumes that the clip is field-based, with the even-numbered fields being bottom fields and the odd-numbered fields being top fields. If you want it the other way around, '''use ComplementParity''' afterwards.
-=== AssumeBFF / AssumeTFF ===
+{{FuncDefH4|AssumeTFF / AssumeBFF}}
-{{Template:Func2Def|AssumeTFF(clip ''clip'')|AssumeBFF(clip ''clip'')}}
+AviSynth keeps track of whether a given clip is ''field-based'' or ''frame-based''. If the clip is field-based it also keeps track of the ''parity'' of each field &ndash; that is, whether it's the top or the bottom field. If the clip is frame-based it keeps track of the ''dominant field'' in each frame &ndash; that is, which field in the frame comes first when they're separated.
-Introduced in v2.0.4.
+However, this information isn't necessarily correct, because field information usually isn't stored in video files and AviSynth's source filters just normally default to assuming bottom field first (with the exception of the [[DGDecode/MPEG2Source|MPEG2Source]] plugin, which gets it right!). '''AssumeTFF''' and '''AssumeBFF''' let you tell AviSynth what you believe the field order a clip has.
-AviSynth keeps track of whether a given clip is field-based or frame-based. If the clip is field-based it also keeps track of the parity of each field (that is, whether it's the top or the bottom field of a frame). If the clip is frame-based it keeps track of the dominant field in each frame (that is, which field in the frame comes first when they're separated).
+They do not change the actual field order, just the internal state flags in AviSynth relating to the source clip used.
-−
-However, this information isn't necessarily correct, because field information usually isn't stored in video files and AviSynth's source filters just normally default to assuming bottom field first (with the exception of the MPEG2Source plugin which gets it right!). AssumeTFF and AssumeBFF let you explicity tell AviSynth what you believe the field order type a clip is.
-−
-AssumeTFF and AssumeBFF do not change the actual field order, just the internal state flags in AviSynth relating to the source clip used.
 '''Examples:'''
+<div {{BoxWidthIndent|24|1}} >
   [[AviSource]]("test.avi")
-  AssumeTFF()
+  AssumeTFF
-  [[SeparateFields]]()
+  [[SeparateFields]]
+</div>
 will always return the top field of the first frame followed by the bottom field of the first frame and so on.
+<div {{BoxWidthIndent|24|1}} >
   AviSource("test.avi")
-  AssumeBFF()
+  AssumeBFF
-  SeparateFields()
+  [[SeparateFields]]
+</div>
 will always return the bottom field of the first frame followed by the top field of the first frame and so on.
-=== ComplementParity ===
+{{FuncDefH4|ComplementParity}}
 {{FuncDef
-{{Template:FuncDef|ComplementParity(clip ''clip'')}}
+|ComplementParity(clip ''clip'')
 }}
-If the input clip is field-based, ComplementParity changes top fields to bottom fields and vice-versa. If the input clip is frame-based, it changes each frame's dominant field (bottom-dominant to top-dominant and vice-versa).
-Like AssumeBFF and AssumeTFF, ComplementParity does not change the actual field order, just the internal state flags in AviSynth relating to the source clip used.
+If the input clip is field-based, '''ComplementParity''' changes top fields to bottom fields and vice-versa. If the input clip is frame-based, it changes each frame's dominant field: bottom-dominant to top-dominant and vice-versa.
 [[Category:Internal filters]]
 [[Category:Interlace_Filters]]