SoC 2009/Weighted P-frame Prediction - Revision history

Underground78: Vadalism Undo revision 15317 by Talk)

2010-01-12T06:23:07Z

Vadalism Undo revision 15317 by Talk)

← Older revision		Revision as of 06:23, 12 January 2010
Line 1:		Line 1:
	~~Penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis~~		{{SoCProject\|year=2009\|student=Dylan Yudaken\|mentor=Jason Garrett-Glaser}}

			== Abstract ==
			x264 is a highly popular h264 encoder. It currently does not implement the entire spec of h264. Currently weighted P-frames are not used to assist in prediction. If implemented this would give huge benefits in cases where the scene fades or where there are flashes. I am proposing to implement an implementation of this that is good enough and fast enough to warrant inclusion in most video encodings.

			== Code ==
			My patches (and codebase) are [http://repo.or.cz/w/x264/x264-p-frames.git?a=shortlog;h=refs/heads/gsoc here] for now, but they may soon move to videolan's server

			== Goals ==
			{\| class="wikitable"
			! No. !! Task Description !! Status !! Comment
			\|-
			\|1 \|\| Build weighting framework \|\| style="background: #00ff00"\|done \|\| .
			\|-
			\|2 \|\| Brute Force Optimal Weights\|\|style="background: #00ff00"\|done \|\|
			\|-
			\|3 \|\| Try use these new weights for some interesting things to improve quality\|\|style="background: #00ff00"\|done \|\|
			\|-
			\|4 \|\| Find Optimal Weights in a fast way (probably based on the findings in 3.) \|\|style="background: #00ff00"\|done \|\|
			\|-
			\|5 \|\| DSP Functions \|\|style="background: #00ff00"\|Done \|\|
			\|-
			\|6 \|\| Try duplicating reference frames \|\|style="background: #00ff00"\|Done\|\|
			\|-
			\|7 \|\| Other weird uses \|\|style="background: #00ff00"\|done \|\| Implemented a k-means cluster algorithm to find a number (k) of good weights and use them
			\|-
			\|8 \|\| Finish off small things \|\|style="background: #00aa00"\|Working \|\| Todo: Finish multipass, cleanup k-means a bit
			\|-
			\|9 \|\| Optimize algorithms and test like crazy \|\| Not started \|\|
			\|-
			\|10 \|\| Cleanup and code review \|\| Not started \|\|
			\|}

			===Current Issues===

			== Timeline ==
			This is an estimation.

			'''March 20th or so - April 3''' Qualifying task. Was a first attempt at goal 1.

			'''April 20''' Students announce

			'''April 21 - May''' Goal 1 redone better and acceptably.

			'''May 1 - May 20''' Work on goal 2

			''' May 23''' Program Starts

			''' May 26 - June 12 ''' Exams

			''' June 13 - July 13''' Code

			''' July 13''' Mid Term deadline. Goals for here have not been set but personally I would like to have goal 2 & 4 finished with goal 3 having a decent chunk of work done. This weird out of order thing is because goal 3 can be worked on continuously as it is not really set, more the trying of ideas.

			''' July 13 - August 17''' Code

			'''August 17''' Program end

Penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis: Replaced content with 'Penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis ...'

2010-01-12T02:08:34Z

Replaced content with 'Penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis ...'

← Older revision		Revision as of 02:08, 12 January 2010
Line 1:		Line 1:
	~~{{SoCProject\|year=2009\|student=Dylan Yudaken\|mentor=Jason Garrett-Glaser}}~~		Penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis penis

	~~== Abstract ==~~
	x264 is a highly popular h264 encoder. It currently does not implement the entire spec of h264. Currently weighted P-frames are not used to assist in prediction. If implemented this would give huge benefits in cases where the scene fades or where there are flashes. I am proposing to implement an implementation of this that is good enough and fast enough to warrant inclusion in most video encodings.

	~~== Code ==~~
	~~My patches (and codebase) are [http://repo.or.cz/w/x264/x264-p-frames.git?a=shortlog;h=refs/heads/gsoc here] for now, but they may soon move to videolan's server~~

	~~== Goals ==~~
	~~{\| class="wikitable"~~
	~~! No. !! Task Description !! Status !! Comment~~
	\|-
	~~\|1 \|\| Build weighting framework \|\| style="background: #00ff00"\|done \|\| .~~
	\|-
	~~\|2 \|\| Brute Force Optimal Weights\|\|style="background: #00ff00"\|done \|\|~~
	\|-
	~~\|3 \|\| Try use these new weights for some interesting things to improve quality\|\|style="background: #00ff00"\|done \|\|~~
	\|-
	~~\|4 \|\| Find Optimal Weights in a fast way (probably based on the findings in 3.) \|\|style="background: #00ff00"\|done \|\|~~
	\|-
	~~\|5 \|\| DSP Functions \|\|style="background: #00ff00"\|Done \|\|~~
	\|-
	~~\|6 \|\| Try duplicating reference frames \|\|style="background: #00ff00"\|Done\|\|~~
	\|-
	~~\|7 \|\| Other weird uses \|\|style="background: #00ff00"\|done \|\| Implemented a k-means cluster algorithm to find a number (k) of good weights and use them~~
	\|-
	~~\|8 \|\| Finish off small things \|\|style="background: #00aa00"\|Working \|\| Todo: Finish multipass, cleanup k-means a bit~~
	\|-
	~~\|9 \|\| Optimize algorithms and test like crazy \|\| Not started \|\|~~
	\|-
	~~\|10 \|\| Cleanup and code review \|\| Not started \|\|~~
	\|}

	~~===Current Issues===~~

	~~== Timeline ==~~
	~~This is an estimation.~~

	~~'''March 20th or so - April 3''' Qualifying task. Was a first attempt at goal 1.~~

	~~'''April 20''' Students announce~~

	~~'''April 21 - May''' Goal 1 redone better and acceptably.~~

	~~'''May 1 - May 20''' Work on goal 2~~

	~~''' May 23''' Program Starts~~

	~~''' May 26 - June 12 ''' Exams~~

	~~''' June 13 - July 13''' Code~~

	''' July 13''' Mid Term deadline. Goals for here have not been set but personally I would like to have goal 2 & 4 finished with goal 3 having a decent chunk of work done. This weird out of order thing is because goal 3 can be worked on continuously as it is not really set, more the trying of ideas.

	~~''' July 13 - August 17''' Code~~

	~~'''August 17''' Program end~~

Underground78: correct link for git repo

2009-08-22T21:23:51Z

correct link for git repo

← Older revision		Revision as of 21:23, 22 August 2009
Line 5:		Line 5:

	== Code ==		== Code ==
	My patches (and codebase) are [http://repo.or.cz/w/x264/x264-p-frames.git?a=~~search&~~h=refs~~%2Fheads%2Fgsoc&st=author&s=DylanZA&sr=1~~ here] for now, but they may soon move to videolan's server		My patches (and codebase) are [http://repo.or.cz/w/x264/x264-p-frames.git?a=shortlog;h=refs/heads/gsoc here] for now, but they may soon move to videolan's server

	== Goals ==		== Goals ==

Dylan: /* Goals */

2009-07-31T22:51:42Z

Goals

← Older revision		Revision as of 22:51, 31 July 2009
Line 15:		Line 15:
	\|2 \|\| Brute Force Optimal Weights\|\|style="background: #00ff00"\|done \|\|		\|2 \|\| Brute Force Optimal Weights\|\|style="background: #00ff00"\|done \|\|
	\|-		\|-
	\|3 \|\| Try use these new weights for some interesting things to improve quality\|\|~~Not started~~ \|\|		\|3 \|\| Try use these new weights for some interesting things to improve quality\|\|style="background: #00ff00"\|done \|\|
	\|-		\|-
	\|4 \|\| Find Optimal Weights in a fast way (probably based on the findings in 3.) \|\|style="background: #~~00aa00~~"\|~~Working~~ \|\| ~~This could probably be improved (for ever)~~		\|4 \|\| Find Optimal Weights in a fast way (probably based on the findings in 3.) \|\|style="background: #00ff00"\|done \|\|
	\|-		\|-
	\|5 \|\| DSP Functions \|\|style="background: #00ff00"\|Done \|\| ~~Assembler done~~		\|5 \|\| DSP Functions \|\|style="background: #00ff00"\|Done \|\|
	\|-		\|-
	\|6 \|\| Try duplicating reference frames \|\|~~Not Started~~\|\|		\|6 \|\| Try duplicating reference frames \|\|style="background: #00ff00"\|Done\|\|
	\|-		\|-
	\|7 \|\| Other weird uses \|\|Not ~~Started~~\|\|		\|7 \|\| Other weird uses \|\|style="background: #00ff00"\|done \|\| Implemented a k-means cluster algorithm to find a number (k) of good weights and use them
			\|-
			\|8 \|\| Finish off small things \|\|style="background: #00aa00"\|Working \|\| Todo: Finish multipass, cleanup k-means a bit
			\|-
			\|9 \|\| Optimize algorithms and test like crazy \|\| Not started \|\|
			\|-
			\|10 \|\| Cleanup and code review \|\| Not started \|\|
	\|}		\|}

Dylan: /* Goals */

2009-07-02T23:30:31Z

Goals

← Older revision		Revision as of 23:30, 2 July 2009
Line 11:		Line 11:
	! No. !! Task Description !! Status !! Comment		! No. !! Task Description !! Status !! Comment
	\|-		\|-
	\|1 \|\| Build weighting framework \|\| style="background: #00ff00"\|done \|\| ~~I have tested it to work~~.		\|1 \|\| Build weighting framework \|\| style="background: #00ff00"\|done \|\| .
	\|-		\|-
	\|2 \|\| Brute Force Optimal Weights\|\|style="background: #~~00aa00~~"\|~~Mostly Working~~ \|\| ~~Working well in hires, quite well in lowres. see below~~		\|2 \|\| Brute Force Optimal Weights\|\|style="background: #00ff00"\|done \|\|
	\|-		\|-
	\|3 \|\| Try use these new weights for some interesting things to improve quality\|\|Not started \|\|		\|3 \|\| Try use these new weights for some interesting things to improve quality\|\|Not started \|\|
	\|-		\|-
	\|4 \|\| Find Optimal Weights in a fast way (probably based on the findings in 3.) \|\|style="background: #~~ffff00~~"\|~~Started~~ \|\| ~~Lots of work to do here~~		\|4 \|\| Find Optimal Weights in a fast way (probably based on the findings in 3.) \|\|style="background: #00aa00"\|Working \|\| This could probably be improved (for ever)
	\|-		\|-
	\|5 \|\| ~~Optimize~~ \|\|style="background: #~~ffff00~~"\|~~Currently working on the weight assembler code.~~ \|\| ~~Currently mmx & sse2 functions work - but code needs to be~~ done ~~in a better way~~		\|5 \|\| DSP Functions \|\|style="background: #00ff00"\|Done \|\| Assembler done
	\|-		\|-
	\|6 \|\| ~~See if explicit B-frame weighting can do good things~~ \|\|Not Started\|\|		\|6 \|\| Try duplicating reference frames \|\|Not Started\|\|
	\|-		\|-
	\|7 \|\| Other weird uses \|\|Not Started\|\|		\|7 \|\| Other weird uses \|\|Not Started\|\|
Line 27:		Line 27:

	===Current Issues===		===Current Issues===

	~~- Currently the weighting doesnt work as well when looking at the lowres frame as the hires. This is the biggest issue currently and will be looked at after exams.~~

	== Timeline ==		== Timeline ==

Dylan: z

2009-05-24T14:40:47Z

← Older revision		Revision as of 14:40, 24 May 2009
Line 3:		Line 3:
	== Abstract ==		== Abstract ==
	x264 is a highly popular h264 encoder. It currently does not implement the entire spec of h264. Currently weighted P-frames are not used to assist in prediction. If implemented this would give huge benefits in cases where the scene fades or where there are flashes. I am proposing to implement an implementation of this that is good enough and fast enough to warrant inclusion in most video encodings.		x264 is a highly popular h264 encoder. It currently does not implement the entire spec of h264. Currently weighted P-frames are not used to assist in prediction. If implemented this would give huge benefits in cases where the scene fades or where there are flashes. I am proposing to implement an implementation of this that is good enough and fast enough to warrant inclusion in most video encodings.

			== Code ==
			My patches (and codebase) are [http://repo.or.cz/w/x264/x264-p-frames.git?a=search&h=refs%2Fheads%2Fgsoc&st=author&s=DylanZA&sr=1 here] for now, but they may soon move to videolan's server

	== Goals ==		== Goals ==

Dylan: /* Goals */

2009-05-24T13:58:33Z

Goals

← Older revision		Revision as of 13:58, 24 May 2009
Line 14:		Line 14:
	\|3 \|\| Try use these new weights for some interesting things to improve quality\|\|Not started \|\|		\|3 \|\| Try use these new weights for some interesting things to improve quality\|\|Not started \|\|
	\|-		\|-
	\|4 \|\| Find Optimal Weights in a fast way (probably based on the findings in 3.) \|\|~~Not started~~ \|\| ~~Actually I have got a lot of ideas, some~~ of ~~which I have tested. Just nothing using the current framework so it is possible that it is all useless.~~		\|4 \|\| Find Optimal Weights in a fast way (probably based on the findings in 3.) \|\|style="background: #ffff00"\|Started \|\| Lots of work to do here

	\|-		\|-
	\|5 \|\| Optimize \|\|style="background: #ffff00"\|Currently working on the weight assembler code. \|\| ~~Never~~ done ~~assembler before so this is going slooow.~~		\|5 \|\| Optimize \|\|style="background: #ffff00"\|Currently working on the weight assembler code. \|\| Currently mmx & sse2 functions work - but code needs to be done in a better way
	\|-		\|-
	\|6 \|\| See if explicit B-frame weighting can do good things \|\|Not Started\|\|		\|6 \|\| See if explicit B-frame weighting can do good things \|\|Not Started\|\|
Line 23:		Line 22:
	\|7 \|\| Other weird uses \|\|Not Started\|\|		\|7 \|\| Other weird uses \|\|Not Started\|\|
	\|}		\|}

			===Current Issues===

			- Currently the weighting doesnt work as well when looking at the lowres frame as the hires. This is the biggest issue currently and will be looked at after exams.

	== Timeline ==		== Timeline ==

Dylan at 13:56, 24 May 2009

2009-05-24T13:56:06Z

← Older revision		Revision as of 13:56, 24 May 2009
Line 10:		Line 10:
	\|1 \|\| Build weighting framework \|\| style="background: #00ff00"\|done \|\| I have tested it to work.		\|1 \|\| Build weighting framework \|\| style="background: #00ff00"\|done \|\| I have tested it to work.
	\|-		\|-
	\|2 \|\| Brute Force Optimal Weights\|\|style="background: #~~ffff00~~"\|~~In Progress~~ \|\| ~~Basic algorithm is there~~, ~~just not working optimally~~		\|2 \|\| Brute Force Optimal Weights\|\|style="background: #00aa00"\|Mostly Working \|\| Working well in hires, quite well in lowres. see below
	\|-		\|-
	\|3 \|\| Try use these new weights for some interesting things to improve quality\|\|Not started \|\|		\|3 \|\| Try use these new weights for some interesting things to improve quality\|\|Not started \|\|

Dylan at 21:41, 7 May 2009

2009-05-07T21:41:03Z

← Older revision		Revision as of 21:41, 7 May 2009
Line 1:		Line 1:
	{{SoCProject\|year=2009\|student=Dylan Yudaken\|mentor=~~ason~~ Garrett-Glaser}}		{{SoCProject\|year=2009\|student=Dylan Yudaken\|mentor=Jason Garrett-Glaser}}

	== Abstract ==		== Abstract ==

Dylan: /* Timeline */

2009-05-07T21:40:26Z

Timeline

← Older revision		Revision as of 21:40, 7 May 2009
Line 28:		Line 28:

	'''March 20th or so - April 3''' Qualifying task. Was a first attempt at goal 1.		'''March 20th or so - April 3''' Qualifying task. Was a first attempt at goal 1.

	'''April 20''' Students announce		'''April 20''' Students announce

	'''April 21 - May''' Goal 1 redone better and acceptably.		'''April 21 - May''' Goal 1 redone better and acceptably.

	'''May 1 - May 20''' Work on goal 2		'''May 1 - May 20''' Work on goal 2

	''' May 23''' Program Starts		''' May 23''' Program Starts

	''' May 26 - June 12 ''' Exams		''' May 26 - June 12 ''' Exams

	''' June 13 - July 13''' Code		''' June 13 - July 13''' Code

	''' July 13''' Mid Term deadline. Goals for here have not been set but personally I would like to have goal 2 & 4 finished with goal 3 having a decent chunk of work done. This weird out of order thing is because goal 3 can be worked on continuously as it is not really set, more the trying of ideas.		''' July 13''' Mid Term deadline. Goals for here have not been set but personally I would like to have goal 2 & 4 finished with goal 3 having a decent chunk of work done. This weird out of order thing is because goal 3 can be worked on continuously as it is not really set, more the trying of ideas.

	''' July 13 - August 17''' Code		''' July 13 - August 17''' Code

	'''August 17''' Program end		'''August 17''' Program end