Known Issues - Revision history

Admin at 12:14, 21 June 2016

2016-06-21T12:14:17Z

← Older revision		Revision as of 14:14, 21 June 2016
Line 1:		Line 1:
	The page contains a list of bugs in 2.60. They are fixed in 2.61 unless stated otherwise.		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 ===		=== Improper YV12<->YUY2 Conversions ===
Line 95:		Line 95:
	ConvertToYV12(interlaced=true, chromaoutplacement="dv")		ConvertToYV12(interlaced=true, chromaoutplacement="dv")

	== API bugs ===		== API bugs ==

	=== 32 bytes aligned frames not allowed ===		=== 32 bytes aligned frames not allowed ===
Line 104:		Line 104:
	=== c-api ===		=== 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]]		[[Category:AviSynth_Usage]]

Admin at 12:13, 21 June 2016

2016-06-21T12:13:53Z

← Older revision		Revision as of 14:13, 21 June 2016
Line 1:		Line 1:
	The page contains a list of bugs in 2.60. They are fixed in 2.61 unless stated otherwise.		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 ===

			=== Improper YV12<->YUY2 Conversions ===
	Please see [http://forum.doom9.org/showthread.php?t=147629]. The built-in YUY2<->YV12 conversions introduce a chroma shift. Use this replacement instead:		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.		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.		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.		[[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.		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.		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		[[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?		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.		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:		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:
	1) 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>		1) 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[x2]-subtract can get negative, and p[x2] won't be zero in that case. <br>		p[x2]-subtract can get negative, and p[x2] won't be zero in that case. <br>
	2) It results in a crash if intercept > height of the image. It either should throw an error or use min(height, intercept) instead.		2) It results in a crash if intercept > height of the image. It either should throw an error or use min(height, intercept) instead.

			=== Convert to planar YUV and chromaoutplacement="dv" ===

			The ConvertToYVxx do the dv-pal chroma with reverse u and v in shifting: http://forum.doom9.org/showpost.php?p=1736293&postcount=55
			Script:

			ColorBars(width=640, height=480, pixel_type="RGB32")
			ConvertToYV12(interlaced=true, chromaoutplacement="dv")

			== API bugs ===

			=== 32 bytes aligned frames not allowed ===
			Some plugin filters require 32bytes aligned pointer and pitch to support AVX2: https://github.com/chikuzen/YV12To422

			However, even if I call env->NewVideoFrame(vi, 32), AviAynth returns 16 bytes aligned frame. Because it uses hard coded FRAME_ALIGN value to calculate offset. This issue still exists in v2.61a1.

			=== c-api ===

			Fix avisynth_c plane=0. Default params are not allowed in plain C.

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

Admin at 22:12, 17 January 2016

2016-01-17T22:12:09Z

← Older revision		Revision as of 00:12, 18 January 2016
Line 81:		Line 81:
	===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.		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===
			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:
			1) 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>
			p[x2] = max(0, BYTE(p[x2]-subtract)); <br>
			p[x2]-subtract can get negative, and p[x2] won't be zero in that case. <br>
			2) 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]]		[[Category:AviSynth_Usage]]

Admin: added ShowSMPTE framerate bug

2016-01-16T16:25:46Z

added ShowSMPTE framerate bug

← Older revision		Revision as of 18: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]]

Admin at 13:48, 23 August 2015

2015-08-23T13:48:52Z

← Older revision		Revision as of 15:48, 23 August 2015
Line 37:		Line 37:
	===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.		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===

Admin: /* Resizers: Chroma Positioning Bugs */

2015-08-23T13:48:22Z

Resizers: Chroma Positioning Bugs

← Older revision		Revision as of 15:48, 23 August 2015
Line 36:		Line 36:

	===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).		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===

Admin at 13:47, 23 August 2015

2015-08-23T13:47:57Z

@@ 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.
 ===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.
 ===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).
 ===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.
@@ Line 133: / Line 79: @@
 todo: is this still an issue?
 [[Category:AviSynth_Usage]]

Reel.Deal: space

2015-06-01T00:14:42Z

space

← Older revision		Revision as of 02: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===

Admin at 21:02, 16 May 2015

2015-05-16T21:02:39Z

← Older revision		Revision as of 23:02, 16 May 2015
Line 1:		Line 1:
	The page contains a list of bugs in 2.58. ~~Most of them~~ are fixed in 2.60 unless stated otherwise.		The page contains a list of bugs in 2.58. They are fixed in 2.60 unless stated otherwise.

	===Crop Bug===		===Crop Bug===
Line 66:		Line 66:
	}		}

	This issue ~~also~~ 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===
Line 81:		Line 81:

	===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]~~. This issue also exists in v2.60~~. It affects all horizontally subsampled YUV formats (YUY2, YV16, YV411 and YV12, but not YV24).		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.


	===Horizontal Shift in RGB->YUY2===		===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]~~. This issue is fixed in 2.60a3~~.		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: 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 ~~also~~ 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.60.


Line 104:		Line 104:
	pointresize(width,height/2)		pointresize(width,height/2)

	This issue exists in ~~v2.58 and~~ v2.60. It will likely remain that way to ensure compatibility.		This issue still exists in v2.60. It will likely remain that way to ensure compatibility.


Line 129:		Line 129:
	c.sincresize(c.width*20,c.height,x,0,c.width,c.height)		c.sincresize(c.width*20,c.height,x,0,c.width,c.height)
	}		}

			todo: is this still an issue?


	===BlankClip and Last Bug===		===BlankClip and Last Bug===
	[[BlankClip]] without brackets will be taken as BlankClip(last) if last has a defined clip value, instead of being taken as BlankClip()~~. Fixed in 2.6a3~~. Discussion http://forum.doom9.org/showthread.php?t=163976 .		[[BlankClip]] without brackets will be taken as BlankClip(last) if last has a defined clip value, instead of being taken as BlankClip(). Discussion http://forum.doom9.org/showthread.php?t=163976 .


	===Audio cache bug===		===Audio cache bug===
	http://forum.doom9.org/showthread.php?t=164833 and http://forum.doom9.org/showthread.php?t=149457 ~~. Fixed in 2.6ax~~.		http://forum.doom9.org/showthread.php?t=164833 and http://forum.doom9.org/showthread.php?t=149457 .

Admin: /* Improper YV12YUY2 Conversions */

2015-05-16T20:58:35Z

Improper YV12YUY2 Conversions

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

			This issue also exists in v2.60.

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