SoC x264 2010 - Revision history

DoesItReallyMatter: +:Category:SoC

2019-02-05T08:47:08Z

← Older revision		Revision as of 08:47, 5 February 2019
Line 189:		Line 189:
	You should also contact the admin [[User:J-b\|jb]].		You should also contact the admin [[User:J-b\|jb]].

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

			[[Category:SoC]]
			[[Category:x264]]

J-b at 14:04, 30 September 2013

2013-09-30T14:04:33Z

← Older revision		Revision as of 14:04, 30 September 2013
Line 189:		Line 189:
	You should also contact the admin [[User:J-b\|jb]].		You should also contact the admin [[User:J-b\|jb]].

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

J-b at 13:45, 30 September 2013

2013-09-30T13:45:57Z

← Older revision		Revision as of 13:45, 30 September 2013
Line 188:		Line 188:

	You should also contact the admin [[User:J-b\|jb]].		You should also contact the admin [[User:J-b\|jb]].

			{{GSoC}}

Dark Shikari: /* Introduction to x264 and Summer of Code */

2010-04-06T10:46:21Z

Introduction to x264 and Summer of Code

← Older revision		Revision as of 10:46, 6 April 2010
Line 11:		Line 11:
	An overview of x264's structure and algorithms can be found [http://akuvian.org/src/x264/overview_x264_v8_5.pdf here]. It is somewhat outdated, but still mostly accurate. Do note that understanding this is not necessary for all projects.		An overview of x264's structure and algorithms can be found [http://akuvian.org/src/x264/overview_x264_v8_5.pdf here]. It is somewhat outdated, but still mostly accurate. Do note that understanding this is not necessary for all projects.

	On a lighter note, feel free to check out the [~~x264 developer quotes page~~ http://mirror05.x264.nl/Dark/loren.html].		On a lighter note, feel free to check out the [http://mirror05.x264.nl/Dark/loren.html x264 developer quotes page].

	==Guide to getting involved==		==Guide to getting involved==

Dark Shikari: /* Introduction to x264 and Summer of Code */

2010-04-06T10:46:09Z

Introduction to x264 and Summer of Code

← Older revision		Revision as of 10:46, 6 April 2010
Line 10:		Line 10:

	An overview of x264's structure and algorithms can be found [http://akuvian.org/src/x264/overview_x264_v8_5.pdf here]. It is somewhat outdated, but still mostly accurate. Do note that understanding this is not necessary for all projects.		An overview of x264's structure and algorithms can be found [http://akuvian.org/src/x264/overview_x264_v8_5.pdf here]. It is somewhat outdated, but still mostly accurate. Do note that understanding this is not necessary for all projects.

			On a lighter note, feel free to check out the [x264 developer quotes page http://mirror05.x264.nl/Dark/loren.html].

	==Guide to getting involved==		==Guide to getting involved==

Dark Shikari: /* Audio encoding */

2010-03-22T23:59:50Z

Audio encoding

← Older revision		Revision as of 23:59, 22 March 2010
Line 94:		Line 94:
	One of x264's current projects is to create a more powerful, general-purpose frontend that is user-friendly and Just Works. In short, you'll be able to run 'x264 input -o output' and generate a perfectly good output file with high-quality video and audio, without messing with any settings. We've got the video down pat, but audio will be whole separate matter. This project will involve the following steps:		One of x264's current projects is to create a more powerful, general-purpose frontend that is user-friendly and Just Works. In short, you'll be able to run 'x264 input -o output' and generate a perfectly good output file with high-quality video and audio, without messing with any settings. We've got the video down pat, but audio will be whole separate matter. This project will involve the following steps:

	*Add some audio handling framework to the main x264 ~~CLI app~~.		*Add some audio handling framework to the main x264 application. It should probably work not too differently from video.
	*Add audio input support to the FFMS, LAVF, and Avisynth input modules.		*Add audio input support to the FFMS, LAVF, and Avisynth input modules.
	*Add audio encoding support using libavcodec (or, if preferred, libvorbis directly). We plan to support Vorbis and AAC.		*Add audio encoding support using libavcodec (or, if preferred, libvorbis directly). We plan to support Vorbis and AAC.

Dark Shikari at 10:59, 21 March 2010

2010-03-21T10:59:46Z

← Older revision		Revision as of 10:59, 21 March 2010
Line 44:		Line 44:
	Not recommended for anyone other than hardcore assembly gurus.		Not recommended for anyone other than hardcore assembly gurus.

	'''Difficulty: High'''		*'''Difficulty: High'''
	'''Amount of work: Medium'''		*'''Amount of work: Medium'''
	'''Skill required: High'''		*'''Skill required: High'''

	===4:4:4 and 4:2:2 colorspaces===		===4:4:4 and 4:2:2 colorspaces===
Line 55:		Line 55:
	This project will involve a lot of coding and a lot of debugging, but none of it should be particularly complex.		This project will involve a lot of coding and a lot of debugging, but none of it should be particularly complex.

	'''Difficulty: Medium'''		*'''Difficulty: Medium'''
	'''Amount of work: High'''		*'''Amount of work: High'''
	'''Skill required: Medium'''		*'''Skill required: Medium'''

	===GPU motion estimation===		===GPU motion estimation===
Line 70:		Line 70:
	This project is not recommended unless you have a very significant amount of experience with CUDA or OpenCL.		This project is not recommended unless you have a very significant amount of experience with CUDA or OpenCL.

	'''Difficulty: Very High'''		*'''Difficulty: Very High'''
	'''Amount of work: Medium'''		*'''Amount of work: Medium'''
	'''Skill required: Very High'''		*'''Skill required: Very High'''

	===10-bit encoding support===		===10-bit encoding support===
Line 87:		Line 87:
	*Start writing assembly code.		*Start writing assembly code.

	'''Difficulty: Medium'''		*'''Difficulty: Medium'''
	'''Amount of work: Low'''		*'''Amount of work: Low'''
	'''Skill required: Medium'''		*'''Skill required: Medium'''

	===Audio encoding===		===Audio encoding===
Line 103:		Line 103:
	This is not nearly as hard as it looks, but will involve touching a whole lot of the main frontend code and learning a lot about how applications such as ffmpeg and VLC work. It's a great project for anyone who wants to get involved in x264 but doesn't think they have the skills to work on the encoder core.		This is not nearly as hard as it looks, but will involve touching a whole lot of the main frontend code and learning a lot about how applications such as ffmpeg and VLC work. It's a great project for anyone who wants to get involved in x264 but doesn't think they have the skills to work on the encoder core.

	'''Difficulty: Low'''		*'''Difficulty: Low'''
	'''Amount of work: Medium'''		*'''Amount of work: Medium'''
	'''Skill required: Medium'''		*'''Skill required: Medium'''

	===Non-local RD optimization===		===Non-local RD optimization===
Line 112:		Line 112:
	This is probably not very difficult from a coding standpoint and is really more of an algorithmic problem. Since we haven't done it already, that of course means it's a ''hard'' algorithmic problem.		This is probably not very difficult from a coding standpoint and is really more of an algorithmic problem. Since we haven't done it already, that of course means it's a ''hard'' algorithmic problem.

	'''Difficulty: High'''		*'''Difficulty: High'''
	'''Amount of work: Low'''		*'''Amount of work: Low'''
	'''Skill required: High'''		*'''Skill required: High'''

	===Adaptive MBAFF support===		===Adaptive MBAFF support===
Line 140:		Line 140:
	And now for the final bonus: there are a lot of companies who want this feature. They are willing to pay a lot of money for it. There are various outstanding bounties of quite significant size (potentially over $10k total) to whoever can complete adaptive MBAFF and get it committed to the x264 trunk.		And now for the final bonus: there are a lot of companies who want this feature. They are willing to pay a lot of money for it. There are various outstanding bounties of quite significant size (potentially over $10k total) to whoever can complete adaptive MBAFF and get it committed to the x264 trunk.

	'''Difficulty: Medium'''		*'''Difficulty: Medium'''
	'''Amount of work: High'''		*'''Amount of work: High'''
	'''Skill required: High'''		*'''Skill required: High'''

	==Qualification tasks==		==Qualification tasks==

Dark Shikari at 10:59, 21 March 2010

2010-03-21T10:59:08Z

← Older revision		Revision as of 10:59, 21 March 2010
Line 27:		Line 27:
	==Projects==		==Projects==
	We are probably only accepting 3-4 students this year. Thus, you will have to prove that you are absolutely able to do your project over the summer--see the qualification tasks. Do remember that the project ideas listed here are merely suggestions; other ideas are always possible if they fit the time and difficulty constraints of SoC. For example, if you have an idea to improve compression (e.g. implementing a new algorithm) that you think we can benefit from, feel free to bring it up.		We are probably only accepting 3-4 students this year. Thus, you will have to prove that you are absolutely able to do your project over the summer--see the qualification tasks. Do remember that the project ideas listed here are merely suggestions; other ideas are always possible if they fit the time and difficulty constraints of SoC. For example, if you have an idea to improve compression (e.g. implementing a new algorithm) that you think we can benefit from, feel free to bring it up.

			These projects are ranked in three categories:
			*'''Difficulty''': how hard a problem the project represents.
			*'''Amount of work''': the amount of raw effort required to complete a project.
			*'''Skill required''': the amount of skill required of the student.

	===Optimization (x86 and/or ARM)===		===Optimization (x86 and/or ARM)===
Line 38:		Line 43:

	Not recommended for anyone other than hardcore assembly gurus.		Not recommended for anyone other than hardcore assembly gurus.

			'''Difficulty: High'''
			'''Amount of work: Medium'''
			'''Skill required: High'''

	===4:4:4 and 4:2:2 colorspaces===		===4:4:4 and 4:2:2 colorspaces===
Line 45:		Line 54:

	This project will involve a lot of coding and a lot of debugging, but none of it should be particularly complex.		This project will involve a lot of coding and a lot of debugging, but none of it should be particularly complex.

			'''Difficulty: Medium'''
			'''Amount of work: High'''
			'''Skill required: Medium'''

	===GPU motion estimation===		===GPU motion estimation===
Line 56:		Line 69:

	This project is not recommended unless you have a very significant amount of experience with CUDA or OpenCL.		This project is not recommended unless you have a very significant amount of experience with CUDA or OpenCL.

			'''Difficulty: Very High'''
			'''Amount of work: Medium'''
			'''Skill required: Very High'''

	===10-bit encoding support===		===10-bit encoding support===
Line 69:		Line 86:
	*Perform motion estimation on an 8-bit version of the frame, but encoding on a full-res version of the frame (motion estimation is vastly faster, much more than 2x faster, on 8-bit).		*Perform motion estimation on an 8-bit version of the frame, but encoding on a full-res version of the frame (motion estimation is vastly faster, much more than 2x faster, on 8-bit).
	*Start writing assembly code.		*Start writing assembly code.

			'''Difficulty: Medium'''
			'''Amount of work: Low'''
			'''Skill required: Medium'''

	===Audio encoding===		===Audio encoding===
Line 81:		Line 102:

	This is not nearly as hard as it looks, but will involve touching a whole lot of the main frontend code and learning a lot about how applications such as ffmpeg and VLC work. It's a great project for anyone who wants to get involved in x264 but doesn't think they have the skills to work on the encoder core.		This is not nearly as hard as it looks, but will involve touching a whole lot of the main frontend code and learning a lot about how applications such as ffmpeg and VLC work. It's a great project for anyone who wants to get involved in x264 but doesn't think they have the skills to work on the encoder core.

			'''Difficulty: Low'''
			'''Amount of work: Medium'''
			'''Skill required: Medium'''

	===Non-local RD optimization===		===Non-local RD optimization===
Line 86:		Line 111:

	This is probably not very difficult from a coding standpoint and is really more of an algorithmic problem. Since we haven't done it already, that of course means it's a ''hard'' algorithmic problem.		This is probably not very difficult from a coding standpoint and is really more of an algorithmic problem. Since we haven't done it already, that of course means it's a ''hard'' algorithmic problem.

			'''Difficulty: High'''
			'''Amount of work: Low'''
			'''Skill required: High'''

	===Adaptive MBAFF support===		===Adaptive MBAFF support===
Line 110:		Line 139:

	And now for the final bonus: there are a lot of companies who want this feature. They are willing to pay a lot of money for it. There are various outstanding bounties of quite significant size (potentially over $10k total) to whoever can complete adaptive MBAFF and get it committed to the x264 trunk.		And now for the final bonus: there are a lot of companies who want this feature. They are willing to pay a lot of money for it. There are various outstanding bounties of quite significant size (potentially over $10k total) to whoever can complete adaptive MBAFF and get it committed to the x264 trunk.

			'''Difficulty: Medium'''
			'''Amount of work: High'''
			'''Skill required: High'''

	==Qualification tasks==		==Qualification tasks==

Dark Shikari: /* Introduction to x264 and Summer of Code */

2010-03-19T05:23:09Z

Introduction to x264 and Summer of Code

← Older revision		Revision as of 05:23, 19 March 2010
Line 1:		Line 1:
	==Introduction to x264 and Summer of Code==		==Introduction to x264 and Summer of Code==
	[[x264]] is the most popular ~~open source~~ video compression ~~library~~ in the world, used worldwide for applications such as web video, television broadcast, and Blu-ray authoring. It outclasses practically all commercial implementations both speed and compression-wise. While not actually part of VLC or ffmpeg, it is a major library used by both, licensed under the GPL. Due to its popularity in the commercial world (for example, Youtube and Facebook rely on it), many companies have offered bounties in the past for features and improvements that they found useful.		[[x264]] is one of the most popular video compression libraries in the world, used worldwide for applications such as web video, television broadcast, and Blu-ray authoring. It outclasses practically all commercial implementations both speed and compression-wise. While not actually part of VLC or ffmpeg, it is a major library used by both, licensed under the GPL. Due to its popularity in the commercial world (for example, Youtube and Facebook rely on it), many companies have offered bounties in the past for features and improvements that they found useful.

	But don't let that all scare you. There's still plenty of projects that a student can effectively get involved in.		But don't let that all scare you. There's still plenty of projects that a student can effectively get involved in.

Dark Shikari: /* Introduction to x264 and Summer of Code */

2010-03-18T05:24:25Z

Introduction to x264 and Summer of Code

← Older revision		Revision as of 05:24, 18 March 2010
Line 1:		Line 1:
	==Introduction to x264 and Summer of Code==		==Introduction to x264 and Summer of Code==
	[[x264]] is the most popular open source video compression ~~software~~ in the world, used worldwide for applications such as web video, television broadcast, and Blu-ray authoring. It outclasses practically all commercial implementations both speed and compression-wise. While not actually part of VLC or ffmpeg, it is a major library used by both, licensed under the GPL. Due to its popularity in the commercial world (for example, Youtube and Facebook rely on it), many companies have offered bounties in the past for features and improvements that they found useful.		[[x264]] is the most popular open source video compression library in the world, used worldwide for applications such as web video, television broadcast, and Blu-ray authoring. It outclasses practically all commercial implementations both speed and compression-wise. While not actually part of VLC or ffmpeg, it is a major library used by both, licensed under the GPL. Due to its popularity in the commercial world (for example, Youtube and Facebook rely on it), many companies have offered bounties in the past for features and improvements that they found useful.

	But don't let that all scare you. There's still plenty of projects that a student can effectively get involved in.		But don't let that all scare you. There's still plenty of projects that a student can effectively get involved in.