Avisynth Plugin Development in C - Revision history

Jmac698 at 11:57, 11 June 2016

2016-06-11T11:57:47Z

← Older revision		Revision as of 13:57, 11 June 2016
Line 1:		Line 1:
	Note: This guide is in development. Currently, only the section [[Avisynth_Plugin_Development_in_C#Compiling_Your_First_Plugin\|Compiling Your First Plugin]] has been tested. The rest contains some errors, so use at your own risk!		Note: This guide is in development. Currently, only the section [[Avisynth_Plugin_Development_in_C#Compiling_Your_First_Plugin\|Compiling Your First Plugin]] has been tested. The rest contains some errors, so use at your own risk!

			Note: for new development, it is recommended to develop in C++ using the Avisynth 2.6 API. Please refer to the guide, [[Avisynth Plugin Development in CPP]]

	Original written by jmac698 with corrections by the Avisynth community.		Original written by jmac698 with corrections by the Avisynth community.
Line 13:		Line 15:
	*It may be simpler to learn for a beginner		*It may be simpler to learn for a beginner
	*There is no download (with online code editor) or small download (with mingw)		*There is no download (with online code editor) or small download (with mingw)
			*You want to use any .NET language, PureBasic, or Delphi

	==Choosing a License==		==Choosing a License==

Jmac698 at 11:48, 11 June 2016

2016-06-11T11:48:12Z

← Older revision		Revision as of 13:48, 11 June 2016
Line 1:		Line 1:
	Note: This guide is in development. Currently, only the section [[Avisynth_Plugin_Development_in_C#Compiling_Your_First_Plugin\|Compiling Your First Plugin]] has been tested. The rest contains some errors, so use at your own risk!		Note: This guide is in development. Currently, only the section [[Avisynth_Plugin_Development_in_C#Compiling_Your_First_Plugin\|Compiling Your First Plugin]] has been tested. The rest contains some errors, so use at your own risk!

			Original written by jmac698 with corrections by the Avisynth community.

	==Introduction==		==Introduction==

Jmac698: /* Choosing a License */

2016-06-11T11:43:54Z

Choosing a License

← Older revision		Revision as of 13:43, 11 June 2016
Line 15:		Line 15:
	Before starting development, be aware of these license requirements:		Before starting development, be aware of these license requirements:

	*The 2.~~6a5~~ C API requires that your plugin uses the GPL license. The GPL license requires that you release the source code.		*The 2.6 C API requires that your plugin uses the GPL license. The GPL license requires that you release the source code.
	*The 2.5 C API can use your own license, but the complete source of AviSynth 2.5 and the C API header must be made available along with your plugin binary		*The 2.5 C API can use your own license, but the complete source of AviSynth 2.5 and the C API header must be made available along with your plugin binary

Jmac698: /* Why Develop a Plugin in C? */

2016-06-11T11:42:49Z

Why Develop a Plugin in C?

← Older revision		Revision as of 13:42, 11 June 2016
Line 7:		Line 7:
	Some reasons to use C based plugin development are that,		Some reasons to use C based plugin development are that,

	*Free compilers can be used, such as MingW; only Microsoft Visual C++ may be used to create AviSynth C++ plugins		*Free compilers can be used, such as MingW and online code editors such as https://codeanywhere.com/features/editor; only Microsoft Visual C++ or the free Community Edition may be used to create AviSynth C++ plugins
	*You are only familiar with C		*You are only familiar with C
	*It may be simpler to learn for a beginner		*It may be simpler to learn for a beginner
			*There is no download (with online code editor) or small download (with mingw)

	==Choosing a License==		==Choosing a License==

Jmac698: /* Writing the actual function */

2016-06-11T11:39:42Z

Writing the actual function

← Older revision		Revision as of 13:39, 11 June 2016
Line 209:		Line 209:
	==Writing the actual function==		==Writing the actual function==
	After all that work, finally we can write a few simple lines of code to actually merge our videos! However, there's still a few more things you need to know. The various video formats are stored in memory in different ways; although we've got a pointer to an area of memory which holds our video, it can be interpreted in different ways, even though it's the same size! This is where handling of YUY2 vs YV12 and RGB comes in. We'll start with YUY2 in our example. YUY2 is where every two luma pixels share a color. A color is stored as two values, U and V. We won't go into what U and V means, except to say that if you average two pixels together, everything works out. YUY2 is stored in this format in memory, from the initial pointer to increasing values in memory, a byte at a time: Y1 U Y2 V. If you access the memory 4 bytes at a time (that is, as a 32 bit unsigned int), due to the Intel assembly stored values as Least Significant Byte order, the int would look like this: 0xVVYYUUYY, where each doubled letter represents one HEX value. For example, if our pixels were Y1=35, Y2=40, U=V=128 (which I'll tell you represents no color or grey), we'd have a hex value of 0x80288023. I mention that only as a reminder for the optimizing section. For now we'll simply deal with them as bytes for clarity. New code:		After all that work, finally we can write a few simple lines of code to actually merge our videos! However, there's still a few more things you need to know. The various video formats are stored in memory in different ways; although we've got a pointer to an area of memory which holds our video, it can be interpreted in different ways, even though it's the same size! This is where handling of YUY2 vs YV12 and RGB comes in. We'll start with YUY2 in our example. YUY2 is where every two luma pixels share a color. A color is stored as two values, U and V. We won't go into what U and V means, except to say that if you average two pixels together, everything works out. YUY2 is stored in this format in memory, from the initial pointer to increasing values in memory, a byte at a time: Y1 U Y2 V. If you access the memory 4 bytes at a time (that is, as a 32 bit unsigned int), due to the Intel assembly stored values as Least Significant Byte order, the int would look like this: 0xVVYYUUYY, where each doubled letter represents one HEX value. For example, if our pixels were Y1=35, Y2=40, U=V=128 (which I'll tell you represents no color or grey), we'd have a hex value of 0x80288023. I mention that only as a reminder for the optimizing section. For now we'll simply deal with them as bytes for clarity. New code:
	aY1=src_data[x~~+Jitter*4~~];		aY1=src_data[x];
	bY1=clip2_data[x];		bY1=clip2_data[x];
	aU=src_data[x+1];		aU=src_data[x+1];
Line 224:		Line 224:
	dest_data[x+2] = (aY2/weight+bY2*weight);		dest_data[x+2] = (aY2/weight+bY2*weight);

	Just remember, again, that [x] is Y1, [x+1] is U, [x+2] is Y2, and [x+3] is V.		Just remember, again, that [x] is Y1, [x+1] is U, [x+2] is Y2, and [x+3] is V.

	==Putting it all together==		==Putting it all together==

Admin at 22:35, 13 December 2014

2014-12-13T22:35:29Z

← Older revision		Revision as of 00:35, 14 December 2014
Line 1:		Line 1:
	Note: This guide is in development. Currently, only the section [[Avisynth_Plugin_Development_in_C#~~Compiling_Your_First_Plugi~~\|Compiling Your First Plugin]] has been tested. The rest contains some errors, so use at your own risk!		Note: This guide is in development. Currently, only the section [[Avisynth_Plugin_Development_in_C#Compiling_Your_First_Plugin\|Compiling Your First Plugin]] has been tested. The rest contains some errors, so use at your own risk!

	==Introduction==		==Introduction==

Reel.Deal: /* Choosing a License */ typo

2014-11-12T03:31:29Z

Choosing a License: typo

← Older revision		Revision as of 05:31, 12 November 2014
Line 14:		Line 14:
	Before starting development, be aware of these license requirements:		Before starting development, be aware of these license requirements:

	*The 2.6a5 C API requires that your plugin ~~use~~ the GPL license. The GPL license requires that you release the source code.		*The 2.6a5 C API requires that your plugin uses the GPL license. The GPL license requires that you release the source code.
	*The 2.5 C API can use ~~you~~ own license, but the complete source of AviSynth 2.5 and the C API header must be made available along with your plugin binary		*The 2.5 C API can use your own license, but the complete source of AviSynth 2.5 and the C API header must be made available along with your plugin binary

	==Plugin Compatibility==		==Plugin Compatibility==

Reel.Deal: forgot something

2014-11-12T03:04:34Z

forgot something

← Older revision		Revision as of 05:04, 12 November 2014
Line 1:		Line 1:
			Note: This guide is in development. Currently, only the section [[Avisynth_Plugin_Development_in_C#Compiling_Your_First_Plugi\|Compiling Your First Plugin]] has been tested. The rest contains some errors, so use at your own risk!

	==Introduction==		==Introduction==
	This tutorial takes you step-by-step through the process of creating a new C plugin for AviSynth by modifying an existing example. By the end of this tutorial, you should be able a plugin which returns a normal value or which works on a single frame. The target audience is the beginning level C programmer.		This tutorial takes you step-by-step through the process of creating a new C plugin for AviSynth by modifying an existing example. By the end of this tutorial, you should be able a plugin which returns a normal value or which works on a single frame. The target audience is the beginning level C programmer.
Line 231:		Line 233:

	==External Links==		==External Links==
	*[http://forum.doom9.org/showthread.php?p=1465008#post1465008 Doom9 Forum] - ~~Basic Help with New Plugin Development (very informational)~~.		*[http://forum.doom9.org/showthread.php?p=1465008#post1465008 Doom9 Forum] - Includes corrections and additional information.
	*[http://forum.doom9.org/showthread.php?p=1688939#post1688939 Doom9 Forum] - Continued discussion.		*[http://forum.doom9.org/showthread.php?p=1688939#post1688939 Doom9 Forum] - Continued discussion.

	[[Category:AviSynth_Development]]		[[Category:AviSynth_Development]]
	[[Category:FilterSDK]]		[[Category:FilterSDK]]

Reel.Deal: copy paste from the original (fixed and updated some links) - http://forum.doom9.org/showpost.php?p=1688939&postcount=53

2014-11-12T03:00:31Z

copy paste from the original (fixed and updated some links) - http://forum.doom9.org/showpost.php?p=1688939&postcount=53

Show changes

Admin at 21:11, 4 August 2014

2014-08-04T21:11:14Z

← Older revision		Revision as of 23:11, 4 August 2014
Line 1:		Line 1:
	A guide is available at http://avisynthnew.wikinet.org/wiki/Avisynth_Plugin_Development_in_C		A guide is available at http://avisynthnew.wikinet.org/wiki/Avisynth_Plugin_Development_in_C

			http://forum.doom9.org/showthread.php?p=1465008#post1465008

	[[Category:AviSynth_Development]]		[[Category:AviSynth_Development]]