Known Issues - Revision history

Admin at 12:14, 21 June 2016

2016-06-21T12:14:17Z

Admin at 12:13, 21 June 2016

2016-06-21T12:13:53Z

Admin at 22:12, 17 January 2016

2016-01-17T22:12:09Z

Admin: added ShowSMPTE framerate bug

2016-01-16T16:25:46Z

added ShowSMPTE framerate bug

Admin at 13:48, 23 August 2015

2015-08-23T13:48:52Z

Admin: /* Resizers: Chroma Positioning Bugs */

2015-08-23T13:48:22Z

‎Resizers: Chroma Positioning Bugs

Admin at 13:47, 23 August 2015

2015-08-23T13:47:57Z

Reel.Deal: space

2015-06-01T00:14:42Z

space

Admin at 21:02, 16 May 2015

2015-05-16T21:02:39Z

Admin: /* Improper YV12YUY2 Conversions */

2015-05-16T20:58:35Z

‎Improper YV12YUY2 Conversions

@@ Line 1: / Line 1: @@
 The page contains a list of bugs in 2.60. They are fixed in 2.61 unless stated otherwise.
-== Usage bugs ===
+== Usage bugs ==
 === Improper YV12<->YUY2 Conversions ===
@@ Line 95: / Line 95: @@
   ConvertToYV12(interlaced=true, chromaoutplacement="dv")
-== API bugs ===
+== API bugs ==
 === 32 bytes aligned frames not allowed ===
@@ Line 104: / Line 104: @@
 === c-api ===
-Fix avisynth_c plane=0. Default params are not allowed in plain C.
+Fix avisynth_c plane=0. Default parameters are not allowed in plain C.
 [[Category:AviSynth_Usage]]

@@ Line 1: / Line 1: @@
 The page contains a list of bugs in 2.60. They are fixed in 2.61 unless stated otherwise.
-===Improper YV12<->YUY2 Conversions===
+== Usage bugs ===
 Please see [http://forum.doom9.org/showthread.php?t=147629].  The built-in YUY2<->YV12 conversions introduce a chroma shift.  Use this replacement instead:
@@ Line 34: / Line 36: @@
 Use the YV12<->YV16 conversions instead. They use a different code path and don't have this problem. This issue still exists in v2.61.
 === Resizers: Chroma Positioning Bugs ===
 ===Resizers: Chroma Positioning Bugs===
 All [[Resize|resizers]] contain (hardly noticeable) horizontal chroma positioning bugs. At first glance it seems to me the code dumbly assumes the chroma is positioned top left of the macrocell, not MPEG1. More can be found [http://forum.doom9.org/showthread.php?p=1505975#post1505975 here] and [http://forum.doom9.org/showthread.php?p=1543729#post1543729 here]. It affects all horizontally subsampled YUV formats (YUY2, YV16, YV411 and YV12, but not YV24). This issue still exists in v2.61.
 === Bob: Chroma Positioning Bugs ===
 ===Bob: Chroma Positioning Bugs===
 [[Bob]] also contains a chroma positioning bug. More can be found [http://forum.doom9.org/showthread.php?p=1172038#post1172038 here]. This issue still exists in v2.61.
 === PointResize Issue ===
 ===PointResize Issue===
 In YUV, [[PointResize]] will delete the first of every two lines when resizing. In RGB, the video is processed upside down and thus every 2nd line will be deleted. The result in this example is a screen of blue in RGB and a screen of black in YUY2.
@@ Line 57: / Line 56: @@
 This issue still exists in v2.61 and it will likely remain that way to ensure compatibility.
 === SincResize Bug ===
 ===SincResize Bug===
 [[SincResize]] produces incorrect results.  This bug exists in AviSynth 2.6a3, but has been corrected in 2.6MT.  Demonstration:  http://screenshotcomparison.com/comparison/91203
@@ Line 79: / Line 77: @@
 todo: is this still an issue?
-===ShowSMPTE framerate check===
+=== ShowSMPTE framerate check ===
 ShowSMPTE framerate must be an integer (24, 25, 30, 31,...) or a standard drop-frame rate as listed in the table below. If that's the case an error should be thrown, but that didn't happen. Not sure whether this bug also exists in v2.58.
-===FixLuminance===
+=== FixLuminance ===
 This filter is broken. I think the idea of the filter is that it progressively darkens the top of the image. So the luma should go from black (at the top) to the luma of the image (at the bottom). It has two defects though:
 ) It is broken when you apply it to an image with height larger than 255 pixels. You will see a repetitive gradient, because of the line <br>
@@ Line 88: / Line 86: @@
 p[x*2]-subtract can get negative, and p[x*2] won't be zero in that case. <br>
 ) It results in a crash if intercept > height of the image. It either should throw an error or use min(height, intercept) instead.
 [[Category:AviSynth_Usage]]

@@ Line 81: / Line 81: @@
 ===ShowSMPTE framerate check===
 ShowSMPTE framerate must be an integer (24, 25, 30, 31,...) or a standard drop-frame rate as listed in the table below. If that's the case an error should be thrown, but that didn't happen. Not sure whether this bug also exists in v2.58.
 [[Category:AviSynth_Usage]]

← Older revision		Revision as of 16:25, 16 January 2016
Line 79:		Line 79:
	todo: is this still an issue?		todo: is this still an issue?

		+	===ShowSMPTE framerate check===
		+	ShowSMPTE framerate must be an integer (24, 25, 30, 31,...) or a standard drop-frame rate as listed in the table below. If that's the case an error should be thrown, but that didn't happen. Not sure whether this bug also exists in v2.58.

	[[Category:AviSynth_Usage]]		[[Category:AviSynth_Usage]]

@@ Line 37: / Line 37: @@
 ===Resizers: Chroma Positioning Bugs===
 All [[Resize|resizers]] contain (hardly noticeable) horizontal chroma positioning bugs. At first glance it seems to me the code dumbly assumes the chroma is positioned top left of the macrocell, not MPEG1. More can be found [http://forum.doom9.org/showthread.php?p=1505975#post1505975 here] and [http://forum.doom9.org/showthread.php?p=1543729#post1543729 here]. It affects all horizontally subsampled YUV formats (YUY2, YV16, YV411 and YV12, but not YV24). This issue still exists in v2.61.
 ===Bob: Chroma Positioning Bugs===

@@ Line 1: / Line 1: @@
-The page contains a list of bugs in 2.58. They are fixed in 2.60 unless stated otherwise.
+The page contains a list of bugs in 2.60. They are fixed in 2.61 unless stated otherwise.
-−
-===Crop Bug===
-The [[crop]] bug exists when cropping RGB including an area outside the screen. There will be a crash instead of an error message.
-−
- # crop Bug
- exposebug = false # set to true to crash
- n = exposebug ? 241 : 240
- colorbars
- crop(0,n,0,n)
- #~ File "pyavs.pyo", line 310, in _GetFrame
- #~ File "avisynth.pyo", line 139, in BitBlt
- #~ WindowsError: exception: access violation reading 0x02DDFFE0
-−
-−
-===Overlay Bug===
-[[Overlay]] gives a yellow tint on videos if used repeatedly on the same RGB video. All inputs to overlay are converted internally to a YUV 4:4:4 format, even if both are RGB.
-−
- # Overlay converts internally to a YUV 4:4:4 format. This will cause
- # an increasing yellowish color at the top of the screen.
- # The script also uses a large amount of memory since each instance of Overlay will use up to 3 full frames of this format.
- # If that bothers you, use Layer instead.
- base = blankclip.trim(0,9)
- over = colorbars.trim(0,9)
- showissue = true # Be careful with overlayissue, large values of n cause excessive memory use leading to a crash
- showissue ? overlayissue(base,over,25) : layernonissue(base.resetmask,over.resetmask,25)
-   function overlayissue(clip base, clip over, int n) {
-     n<2?overlay(base,over.crop(0,n-1,0,1),y=n-1):overlay(overlayissue(base,over,n-1),over.crop(0,n-1,0,1),y=n-1)
-−
-   function layernonissue(clip base, clip over, int n) {
-     n<2?layer(base,over.crop(0,n-1,0,1),y=n-1):layer(layernonissue(base,over,n-1),over.crop(0,n-1,0,1),y=n-1)
-−
-−
-The yellow tint is caused by incorrect rounding: [http://forum.doom9.org/showthread.php?p=1471072#post1471072].
-−
 ===Improper YV12<->YUY2 Conversions===
@@ Line 66: / Line 32: @@
+  }
-Use the YV12<->YV16 conversions instead. They use a different code path and don't have this problem. This issue still exists in v2.60.
+Use the YV12<->YV16 conversions instead. They use a different code path and don't have this problem. This issue still exists in v2.61.
-−
-−
-===ImageSource/ImageReader Bug===
-Reading a tga image results in a flipped (upside down) output. This can be 'corrected' by using [[FlipVertical]] afterwards.
-−
-−
-===SeparateFields: Parity Bug===
-The separation of the fields is done wrong if the parity of the clip is not constant (thus if an earlier filter has introduced a non-standard parity function, where the parity depends on the frame number). However, frame-based clips (the usual source material) usually have the same parity for every frame, since the entire clip is usually TFF or BFF. Hence the problem doesn't show up. More can be found [http://forum.doom9.org/showthread.php?t=153313 here].
-−
-−
-===MergeChroma/MergeLuma Documentation Bug===
-There is no "weight" argument. It should be "LumaWeight" for [[MergeLuma]]() and "ChromaWeight" for [[MergeChroma]](). Since v2.60 you can also use the "weight" argument.
 ===Resizers: Chroma Positioning Bugs===
-All [[Resize|resizers]] contain (hardly noticeable) horizontal chroma positioning bugs. At first glance it seems to me the code dumbly assumes the chroma is positioned top left of the macrocell, not MPEG1. More can be found [http://forum.doom9.org/showthread.php?p=1505975#post1505975 here] and [http://forum.doom9.org/showthread.php?p=1543729#post1543729 here]. It affects all horizontally subsampled YUV formats (YUY2, YV16, YV411 and YV12, but not YV24). This issue still exists in v2.60.
+All [[Resize|resizers]] contain (hardly noticeable) horizontal chroma positioning bugs. At first glance it seems to me the code dumbly assumes the chroma is positioned top left of the macrocell, not MPEG1. More can be found [http://forum.doom9.org/showthread.php?p=1505975#post1505975 here] and [http://forum.doom9.org/showthread.php?p=1543729#post1543729 here]. It affects all horizontally subsampled YUV formats (YUY2, YV16, YV411 and YV12, but not YV24).
-−
-−
-===Horizontal Shift in RGB->YUY2===
-There is a horizontal shift when doing a RGB->YUY2 conversion as described [http://forum.doom9.org/showthread.php?p=1038027#post1038027 here].
 ===Bob: Chroma Positioning Bugs===
-[[Bob]] also contains a chroma positioning bug. More can be found [http://forum.doom9.org/showthread.php?p=1172038#post1172038 here]. This issue still exists in v2.60.
+[[Bob]] also contains a chroma positioning bug. More can be found [http://forum.doom9.org/showthread.php?p=1172038#post1172038 here]. This issue still exists in v2.61.
@@ Line 105: / Line 55: @@
   pointresize(width,height/2)
-This issue still exists in v2.60. It will likely remain that way to ensure compatibility.
+This issue still exists in v2.61 and it will likely remain that way to ensure compatibility.
-−
-−
-===Histogram Bug===
-The display shown in [[Histogram]] looks different whether in YV12 or YUY2.  The marked areas are wrong; the midpoint is off-center and the upper range is too large.
@@ Line 133: / Line 79: @@
 todo: is this still an issue?
 [[Category:AviSynth_Usage]]

← Older revision		Revision as of 00:14, 1 June 2015
Line 67:		Line 67:

	Use the YV12<->YV16 conversions instead. They use a different code path and don't have this problem. This issue still exists in v2.60.		Use the YV12<->YV16 conversions instead. They use a different code path and don't have this problem. This issue still exists in v2.60.
		+

	===ImageSource/ImageReader Bug===		===ImageSource/ImageReader Bug===

← Older revision		Revision as of 20:58, 16 May 2015
Line 66:		Line 66:
	}		}

		+	This issue also exists in v2.60.

	===ImageSource/ImageReader Bug===		===ImageSource/ImageReader Bug===