X264 GCodeIn Ideas - Revision history

DoesItReallyMatter: +{{Lowercase}}

2019-03-09T20:22:50Z

+{{Lowercase}}

← Older revision		Revision as of 20:22, 9 March 2019
Line 1:		Line 1:
			{{Lowercase}}
	= Google Code In =		= Google Code In =

J-b at 13:57, 30 September 2013

2013-09-30T13:57:28Z

← Older revision		Revision as of 13:57, 30 September 2013
Line 73:		Line 73:

	IRC channel: #x264dev on irc://irc.freenode.net		IRC channel: #x264dev on irc://irc.freenode.net

			[[Category:x264]] {{GSoC}}

Dark Shikari: /* CLI Development */

2010-11-06T21:42:11Z

CLI Development

← Older revision		Revision as of 21:42, 6 November 2010
Line 51:		Line 51:

	'''Outcome''': Users can specify a specific device to x264.<br>		'''Outcome''': Users can specify a specific device to x264.<br>
	'''Difficulty''': ~~easy-~~medium<br>		'''Difficulty''': medium<br>
	'''Tools''': x264<br>		'''Tools''': x264<br>
	'''Time''': 1-2 days<br>		'''Time''': 3-5 days<br>
	'''Possible Mentors''': Jason Garrett-Glaser (Dark Shikari), James Darnley (J_Darnley), Steven Walters (kemuri-_9), Kieran Kunhya (kierank)<br>		'''Possible Mentors''': Jason Garrett-Glaser (Dark Shikari), James Darnley (J_Darnley), Steven Walters (kemuri-_9), Kieran Kunhya (kierank)<br>

Kieran at 21:40, 6 November 2010

2010-11-06T21:40:57Z

@@ Line 43: / Line 43: @@
 '''Time''': 7 days<br>
 '''Possible Mentors''': Jason Garrett-Glaser (Dark Shikari), James Darnley (J_Darnley), Steven Walters (kemuri-_9)<br>
 == libx264 Core Development ==

Dark Shikari: /* libx264 Core Development */

2010-11-06T19:59:50Z

libx264 Core Development

← Older revision		Revision as of 19:59, 6 November 2010
Line 50:		Line 50:
	'''Details''': x264 has boatloads of C functions with assembly versions that haven't been written yet. Assembly functions are really great for Google Code-In because they can be written without any knowledge of the overall program. Most functions are only a few lines long in C, making an assembly implementation relatively easy. In many cases, some (but not all) versions of a function are already written in assembly, providing good examples for future versions.<br>		'''Details''': x264 has boatloads of C functions with assembly versions that haven't been written yet. Assembly functions are really great for Google Code-In because they can be written without any knowledge of the overall program. Most functions are only a few lines long in C, making an assembly implementation relatively easy. In many cases, some (but not all) versions of a function are already written in assembly, providing good examples for future versions.<br>

	If you pick this task, it's highly recommended that you have some experience in assembly coding already. Writing a single function is not too difficult if you already have some experience, but if you've never done it before, it will take significantly more time. Of course, if you're interested in learning, we'd be happy to teach you~~, but it will take much longer~~.<br>		If you pick this task, it's highly recommended that you have some experience in assembly coding already. Writing a single function is not too difficult if you already have some experience, but if you've never done it before, it will take significantly more time. Of course, if you're interested in learning, we'd be happy to teach you--Jason has taught many many students before. It usually takes a couple hours to learn the basics.<br>
	'''Outcome''': A new assembly function in x264.<br>		'''Outcome''': A new assembly function in x264.<br>
	'''Difficulty''': hard<br>		'''Difficulty''': hard<br>

Dark Shikari: /* libx264 Core Development */

2010-11-06T19:56:01Z

libx264 Core Development

← Older revision		Revision as of 19:56, 6 November 2010
Line 50:		Line 50:
	'''Details''': x264 has boatloads of C functions with assembly versions that haven't been written yet. Assembly functions are really great for Google Code-In because they can be written without any knowledge of the overall program. Most functions are only a few lines long in C, making an assembly implementation relatively easy. In many cases, some (but not all) versions of a function are already written in assembly, providing good examples for future versions.<br>		'''Details''': x264 has boatloads of C functions with assembly versions that haven't been written yet. Assembly functions are really great for Google Code-In because they can be written without any knowledge of the overall program. Most functions are only a few lines long in C, making an assembly implementation relatively easy. In many cases, some (but not all) versions of a function are already written in assembly, providing good examples for future versions.<br>

	If you pick this task, it's highly recommended that you have some experience in assembly coding already. Writing a single function is not too difficult if you already have some experience, but if you've never done it before, it will take significantly more time. Of course, if you're interested in learning, we'd be happy to teach you, but ~~don't complain when~~ it~~'s harder than you expected!~~<br>		If you pick this task, it's highly recommended that you have some experience in assembly coding already. Writing a single function is not too difficult if you already have some experience, but if you've never done it before, it will take significantly more time. Of course, if you're interested in learning, we'd be happy to teach you, but it will take much longer.<br>
	'''Outcome''': A new assembly function in x264.<br>		'''Outcome''': A new assembly function in x264.<br>
	'''Difficulty''': hard<br>		'''Difficulty''': hard<br>

Dark Shikari: /* libx264 Core Development */

2010-11-06T19:55:25Z

libx264 Core Development

← Older revision		Revision as of 19:55, 6 November 2010
Line 48:		Line 48:
	'''Category''': Assembly Optimization<br>		'''Category''': Assembly Optimization<br>
	'''Description''': Write ''any'' assembly function: x86 (MMX/SSE), PowerPC (Altivec), or ARM (ARMv6/NEON)<br>		'''Description''': Write ''any'' assembly function: x86 (MMX/SSE), PowerPC (Altivec), or ARM (ARMv6/NEON)<br>
	'''Details''': x264 has boatloads of C functions with assembly versions that haven't been written yet. Assembly functions are really great for Google Code-In because they can be written without any knowledge of the overall program. Most functions are only a few lines long in C, making an assembly implementation relatively easy.<br>		'''Details''': x264 has boatloads of C functions with assembly versions that haven't been written yet. Assembly functions are really great for Google Code-In because they can be written without any knowledge of the overall program. Most functions are only a few lines long in C, making an assembly implementation relatively easy. In many cases, some (but not all) versions of a function are already written in assembly, providing good examples for future versions.<br>

	If you pick this task, it's highly recommended that you have some experience in assembly coding already. Writing a single function is not too difficult if you already have some experience, but if you've never done it before, it will take significantly more time. Of course, if you're interested in learning, we'd be happy to teach you, but don't complain when it's harder than you expected!<br>		If you pick this task, it's highly recommended that you have some experience in assembly coding already. Writing a single function is not too difficult if you already have some experience, but if you've never done it before, it will take significantly more time. Of course, if you're interested in learning, we'd be happy to teach you, but don't complain when it's harder than you expected!<br>

Dark Shikari: /* libx264 Core Development */

2010-11-06T19:50:24Z

libx264 Core Development

← Older revision		Revision as of 19:50, 6 November 2010
Line 48:		Line 48:
	'''Category''': Assembly Optimization<br>		'''Category''': Assembly Optimization<br>
	'''Description''': Write ''any'' assembly function: x86 (MMX/SSE), PowerPC (Altivec), or ARM (ARMv6/NEON)<br>		'''Description''': Write ''any'' assembly function: x86 (MMX/SSE), PowerPC (Altivec), or ARM (ARMv6/NEON)<br>
	'''Details''': x264 has boatloads of assembly ~~functions~~ that haven't been written yet. Assembly functions are really great for Google Code-In because they can be written without any knowledge of the overall program. Most functions are only a few lines long in C, making an assembly implementation relatively easy.<br>		'''Details''': x264 has boatloads of C functions with assembly versions that haven't been written yet. Assembly functions are really great for Google Code-In because they can be written without any knowledge of the overall program. Most functions are only a few lines long in C, making an assembly implementation relatively easy.<br>

	If you pick this task, it's highly recommended that you have some experience in assembly coding already. Writing a single function is not too difficult if you already have some experience, but if you've never done it before, it will take significantly more time. Of course, if you're interested in learning, we'd be happy to teach you, but don't complain when it's harder than you expected!<br>		If you pick this task, it's highly recommended that you have some experience in assembly coding already. Writing a single function is not too difficult if you already have some experience, but if you've never done it before, it will take significantly more time. Of course, if you're interested in learning, we'd be happy to teach you, but don't complain when it's harder than you expected!<br>

Dark Shikari: /* libx264 Core Development */

2010-11-06T19:49:58Z

libx264 Core Development

← Older revision		Revision as of 19:49, 6 November 2010
Line 53:		Line 53:
	'''Outcome''': A new assembly function in x264.<br>		'''Outcome''': A new assembly function in x264.<br>
	'''Difficulty''': hard<br>		'''Difficulty''': hard<br>
	'''Tools''': x264, yasm<br>		'''Tools''': x264, yasm (for x86) or gas (for ARM)<br>
	'''Time''': 0.5-7 days, depends heavily on function complexity<br>		'''Time''': 0.5-7 days, depends heavily on function complexity<br>
	'''Possible Mentors''': Jason Garrett-Glaser (Dark Shikari), Holger Lubitz (holger), Loren Merritt (pengvado)<br>		'''Possible Mentors''': Jason Garrett-Glaser (Dark Shikari), Holger Lubitz (holger), Loren Merritt (pengvado)<br>

Dark Shikari: /* libx264 Core Development */

2010-11-06T19:49:37Z

libx264 Core Development

← Older revision		Revision as of 19:49, 6 November 2010
Line 54:		Line 54:
	'''Difficulty''': hard<br>		'''Difficulty''': hard<br>
	'''Tools''': x264, yasm<br>		'''Tools''': x264, yasm<br>
	'''Time''': 1-7 days<br>		'''Time''': 0.5-7 days, depends heavily on function complexity<br>
	'''Possible Mentors''': Jason Garrett-Glaser (Dark Shikari), Holger Lubitz (holger), Loren Merritt (pengvado)<br>		'''Possible Mentors''': Jason Garrett-Glaser (Dark Shikari), Holger Lubitz (holger), Loren Merritt (pengvado)<br>