Archive:GSoC - GPU Assisted Video Decoding - Revision history

Karellen: Karellen moved page GSoC - GPU Assisted Video Decoding to Archive:GSoC - GPU Assisted Video Decoding without leaving a redirect: Outdated

2020-08-28T01:47:49Z

Karellen moved page GSoC - GPU Assisted Video Decoding to Archive:GSoC - GPU Assisted Video Decoding without leaving a redirect: Outdated

← Older revision	Revision as of 01:47, 28 August 2020
(No difference)

Karellen at 01:46, 28 August 2020

2020-08-28T01:46:43Z

← Older revision		Revision as of 01:46, 28 August 2020
Line 1:		Line 1:
	~~{{mininav\|[[Development]]\|[[:Category:Google Summer of Code]]}}~~
	{{info\|This page describes a previous GSoC project. '''For the most recent GSoC pages please check [[:Category:Google Summer of Code]]'''.}}		{{info\|This page describes a previous GSoC project. '''For the most recent GSoC pages please check [[:Category:Google Summer of Code]]'''.}}

Line 13:		Line 12:

	= GSoC proposal for 2008 =		= GSoC proposal for 2008 =
	This is a discussion about a proposal for XBMC's [[Google Summer of Code 2008]]		This is a discussion about a proposal for XBMC's Google Summer of Code 2008

	== Current Draft ==		== Current Draft ==

NedBot: web link corrections for xbmc -> kodi

2015-05-13T00:43:50Z

web link corrections for xbmc -> kodi

← Older revision		Revision as of 00:43, 13 May 2015
Line 10:		Line 10:

	* XBMC community forum discussion threads:		* XBMC community forum discussion threads:
	** [http://forum.~~xbmc~~.~~org~~/showthread.php?t=33802 GPU assisted H.264 Decoding (GSoC Project 2008)]		** [http://forum.kodi.tv/showthread.php?t=33802 GPU assisted H.264 Decoding (GSoC Project 2008)]

	= GSoC proposal for 2008 =		= GSoC proposal for 2008 =

NedBot: Robot: Substituting template: Name

2014-06-05T20:15:36Z

Robot: Substituting template: Name

NedBot: Bot: Automated text replacement (- XBMC + {{name}} )

2014-06-05T01:04:20Z

Bot: Automated text replacement (- XBMC + {{name}} )

Ned Scott at 23:31, 6 February 2014

2014-02-06T23:31:06Z

← Older revision		Revision as of 23:31, 6 February 2014
Line 1:		Line 1:
	{{mininav\|[[Development]]\|[[:Category:Google Summer of Code]]}}		{{mininav\|[[Development]]\|[[:Category:Google Summer of Code]]}}
			{{info\|This page describes a previous GSoC project. '''For the most recent GSoC pages please check [[:Category:Google Summer of Code]]'''.}}

	GPU Hardware Accelerated Video Decoding of H.264 (MPEG-4 part-10, a.k.a. MPEG-4 AVC) encoded video.		GPU Hardware Accelerated Video Decoding of H.264 (MPEG-4 part-10, a.k.a. MPEG-4 AVC) encoded video.

Martijn at 13:07, 4 September 2013

2013-09-04T13:07:17Z

← Older revision		Revision as of 13:07, 4 September 2013
Line 1:		Line 1:
			{{mininav\|[[Development]]\|[[:Category:Google Summer of Code]]}}

	GPU Hardware Accelerated Video Decoding of H.264 (MPEG-4 part-10, a.k.a. MPEG-4 AVC) encoded video.		GPU Hardware Accelerated Video Decoding of H.264 (MPEG-4 part-10, a.k.a. MPEG-4 AVC) encoded video.

Ned Scott: Protected "GSoC - GPU Assisted Video Decoding" ([edit=autoconfirmed] (indefinite) [move=autoconfirmed] (indefinite))

2011-12-09T01:16:37Z

Protected "GSoC - GPU Assisted Video Decoding" ([edit=autoconfirmed] (indefinite) [move=autoconfirmed] (indefinite))

← Older revision	Revision as of 01:16, 9 December 2011
(No difference)

Ned Scott: Reverted edits by Jeg260 (talk) to last revision by NedBot

2011-12-09T01:13:03Z

Reverted edits by Jeg260 (talk) to last revision by NedBot

← Older revision		Revision as of 01:13, 9 December 2011
Line 85:		Line 85:
	=== Personal Statement ===		=== Personal Statement ===
	I am currently a 21 year old senior at the Massachusetts Institute of Technology majoring in Computer Science and Engineering. In the fall of 2008, I will enter an MIT Master’s program in Electrical Engineering and Computer Science. Systems programming and signal processing have always been interests of mine. I feel that this project will offer me a unique chance to blend my interests in low level systems programming with my passion for signal processing.		I am currently a 21 year old senior at the Massachusetts Institute of Technology majoring in Computer Science and Engineering. In the fall of 2008, I will enter an MIT Master’s program in Electrical Engineering and Computer Science. Systems programming and signal processing have always been interests of mine. I feel that this project will offer me a unique chance to blend my interests in low level systems programming with my passion for signal processing.
	~~[http://hauthorn-it.dk wordpress hjemmeside]~~
	I have a lot of experience coding at all levels of complexity. From creation of Java Chess software to the implementation of an Operating System on the level of Unix-version 6 in C and x86 assembly. Working on this project will allow me to grow as a programmer as well as contribute to excellent open source software.		I have a lot of experience coding at all levels of complexity. From creation of Java Chess software to the implementation of an Operating System on the level of Unix-version 6 in C and x86 assembly. Working on this project will allow me to grow as a programmer as well as contribute to excellent open source software.

	[[Category:Google Summer of Code]]		[[Category:Google Summer of Code]]

>Jeg260: /* Personal Statement */

2011-12-08T21:34:36Z

Personal Statement

← Older revision		Revision as of 21:34, 8 December 2011
Line 85:		Line 85:
	=== Personal Statement ===		=== Personal Statement ===
	I am currently a 21 year old senior at the Massachusetts Institute of Technology majoring in Computer Science and Engineering. In the fall of 2008, I will enter an MIT Master’s program in Electrical Engineering and Computer Science. Systems programming and signal processing have always been interests of mine. I feel that this project will offer me a unique chance to blend my interests in low level systems programming with my passion for signal processing.		I am currently a 21 year old senior at the Massachusetts Institute of Technology majoring in Computer Science and Engineering. In the fall of 2008, I will enter an MIT Master’s program in Electrical Engineering and Computer Science. Systems programming and signal processing have always been interests of mine. I feel that this project will offer me a unique chance to blend my interests in low level systems programming with my passion for signal processing.
			[http://hauthorn-it.dk wordpress hjemmeside]
	I have a lot of experience coding at all levels of complexity. From creation of Java Chess software to the implementation of an Operating System on the level of Unix-version 6 in C and x86 assembly. Working on this project will allow me to grow as a programmer as well as contribute to excellent open source software.		I have a lot of experience coding at all levels of complexity. From creation of Java Chess software to the implementation of an Operating System on the level of Unix-version 6 in C and x86 assembly. Working on this project will allow me to grow as a programmer as well as contribute to excellent open source software.

	[[Category:Google Summer of Code]]		[[Category:Google Summer of Code]]

← Older revision		Revision as of 20:15, 5 June 2014
Line 9:		Line 9:


	* ~~{{name}}~~ community forum discussion threads:		* XBMC community forum discussion threads:
	** [http://forum.xbmc.org/showthread.php?t=33802 GPU assisted H.264 Decoding (GSoC Project 2008)]		** [http://forum.xbmc.org/showthread.php?t=33802 GPU assisted H.264 Decoding (GSoC Project 2008)]

Line 26:		Line 26:

	=== Benefits ===		=== Benefits ===
	# This project will improve the end-user experience tremendously. ~~{{name}}~~ is a prime choice for many users who have an HTPC. These Machines traditionally don't have excessive amounts of processing power. Any computations that could be offloaded to unused hardware would be ideal.		# This project will improve the end-user experience tremendously. XBMC is a prime choice for many users who have an HTPC. These Machines traditionally don't have excessive amounts of processing power. Any computations that could be offloaded to unused hardware would be ideal.
	# Exploring new territory: Much talk has been given to the use of GPUs for general purpose computation. An actual implementation of a video decoder in a non-GPU specific manner would be quite the achievement!		# Exploring new territory: Much talk has been given to the use of GPUs for general purpose computation. An actual implementation of a video decoder in a non-GPU specific manner would be quite the achievement!

Line 43:		Line 43:
	While, it pains me to include something as nebulous as "research" into my project proposal, I do feel that the time spent researching alternatives is necessary and will be well spent. Using a GPU for general purpose computing (the GPGPU movement) is a rather new field of inquiry. There are very few accepted standards, with each vendor proposing their own solutions. Thus far possible initiatives for GPU accelerated video coding/decoding include: Intel's VAAPI, Nvidia's CUDA/FreeVideo, and ATI’s Avivo/CTM. This is in addition to any video capabilities within the DirectX and OpenGL APIs and several GPGPU libraries such as Brook and lib sh.		While, it pains me to include something as nebulous as "research" into my project proposal, I do feel that the time spent researching alternatives is necessary and will be well spent. Using a GPU for general purpose computing (the GPGPU movement) is a rather new field of inquiry. There are very few accepted standards, with each vendor proposing their own solutions. Thus far possible initiatives for GPU accelerated video coding/decoding include: Intel's VAAPI, Nvidia's CUDA/FreeVideo, and ATI’s Avivo/CTM. This is in addition to any video capabilities within the DirectX and OpenGL APIs and several GPGPU libraries such as Brook and lib sh.

	At the time of this writing, I am strongly leaning towards an implementation done in OpenGL Shader Language (GLSL). While, unlike many of the other architectures, GLSL was not made with the intent purpose of allowing a GPU to perform general purpose calculations, it has the advantages of providing enough functionality to do video decoding calculations, while being part of an API that is almost universally supported by GPUs and Operating Systems. Since ~~{{name}}~~ strives to be as portable as possible, I feel that GLSL is the most advantageous. However, I will definitely not overlook other architectures. Specifically the GPGPU libraries look very promising.		At the time of this writing, I am strongly leaning towards an implementation done in OpenGL Shader Language (GLSL). While, unlike many of the other architectures, GLSL was not made with the intent purpose of allowing a GPU to perform general purpose calculations, it has the advantages of providing enough functionality to do video decoding calculations, while being part of an API that is almost universally supported by GPUs and Operating Systems. Since XBMC strives to be as portable as possible, I feel that GLSL is the most advantageous. However, I will definitely not overlook other architectures. Specifically the GPGPU libraries look very promising.


Line 79:		Line 79:
	This is only a very tentative outline. Any given module may be completed in a longer or shorter period. It simply serves as a guideline for what I hope to achieve and the order I plan to set about doing it. At the very least I am hoping I can get the two primary modules (motion compensation and IDCT) implemented and integrated with the SVN repository over the summer.		This is only a very tentative outline. Any given module may be completed in a longer or shorter period. It simply serves as a guideline for what I hope to achieve and the order I plan to set about doing it. At the very least I am hoping I can get the two primary modules (motion compensation and IDCT) implemented and integrated with the SVN repository over the summer.

	# Architecture Research - 2 Weeks- Researching and choosing the architecture of the hardware decoder. At the end of this period I will have code running from within ~~{{name}}~~ that uses the given architecture.		# Architecture Research - 2 Weeks- Researching and choosing the architecture of the hardware decoder. At the end of this period I will have code running from within XBMC that uses the given architecture.
	# H.264 decoder Skeleton – 1 Week – A skeleton of my H.264 decoder will be written. Will be compromised of mostly the software implementation currently within ~~{{name}}~~ (which I believe is handled by FFmpeg at the moment), and will be replaced with the hardware components as they are written.		# H.264 decoder Skeleton – 1 Week – A skeleton of my H.264 decoder will be written. Will be compromised of mostly the software implementation currently within XBMC (which I believe is handled by FFmpeg at the moment), and will be replaced with the hardware components as they are written.
	# Motion Compensation - 3 weeks - Implementation of Motion Compensation using the chosen architecture		# Motion Compensation - 3 weeks - Implementation of Motion Compensation using the chosen architecture
	# Inverse Transformation - 3 Weeks - Implementation of inverse Transformation . Success will be judged by successfully lowering the amount of CPU cycles required to decode a given H.264 video over the initial software implementation		# Inverse Transformation - 3 Weeks - Implementation of inverse Transformation . Success will be judged by successfully lowering the amount of CPU cycles required to decode a given H.264 video over the initial software implementation
	# Testing and Final Commit – 2 week - - Extensive testing as well as modifying the code to fit within the ~~{{name}}~~ repository. Any left over time will be spent researching other areas to accelerate with hardware.		# Testing and Final Commit – 2 week - - Extensive testing as well as modifying the code to fit within the XBMC repository. Any left over time will be spent researching other areas to accelerate with hardware.

← Older revision		Revision as of 01:04, 5 June 2014
Line 9:		Line 9:


	* ~~XBMC~~ community forum discussion threads:		* {{name}} community forum discussion threads:
	** [http://forum.xbmc.org/showthread.php?t=33802 GPU assisted H.264 Decoding (GSoC Project 2008)]		** [http://forum.xbmc.org/showthread.php?t=33802 GPU assisted H.264 Decoding (GSoC Project 2008)]

Line 26:		Line 26:

	=== Benefits ===		=== Benefits ===
	# This project will improve the end-user experience tremendously. ~~XBMC~~ is a prime choice for many users who have an HTPC. These Machines traditionally don't have excessive amounts of processing power. Any computations that could be offloaded to unused hardware would be ideal.		# This project will improve the end-user experience tremendously. {{name}} is a prime choice for many users who have an HTPC. These Machines traditionally don't have excessive amounts of processing power. Any computations that could be offloaded to unused hardware would be ideal.
	# Exploring new territory: Much talk has been given to the use of GPUs for general purpose computation. An actual implementation of a video decoder in a non-GPU specific manner would be quite the achievement!		# Exploring new territory: Much talk has been given to the use of GPUs for general purpose computation. An actual implementation of a video decoder in a non-GPU specific manner would be quite the achievement!

Line 43:		Line 43:
	While, it pains me to include something as nebulous as "research" into my project proposal, I do feel that the time spent researching alternatives is necessary and will be well spent. Using a GPU for general purpose computing (the GPGPU movement) is a rather new field of inquiry. There are very few accepted standards, with each vendor proposing their own solutions. Thus far possible initiatives for GPU accelerated video coding/decoding include: Intel's VAAPI, Nvidia's CUDA/FreeVideo, and ATI’s Avivo/CTM. This is in addition to any video capabilities within the DirectX and OpenGL APIs and several GPGPU libraries such as Brook and lib sh.		While, it pains me to include something as nebulous as "research" into my project proposal, I do feel that the time spent researching alternatives is necessary and will be well spent. Using a GPU for general purpose computing (the GPGPU movement) is a rather new field of inquiry. There are very few accepted standards, with each vendor proposing their own solutions. Thus far possible initiatives for GPU accelerated video coding/decoding include: Intel's VAAPI, Nvidia's CUDA/FreeVideo, and ATI’s Avivo/CTM. This is in addition to any video capabilities within the DirectX and OpenGL APIs and several GPGPU libraries such as Brook and lib sh.

	At the time of this writing, I am strongly leaning towards an implementation done in OpenGL Shader Language (GLSL). While, unlike many of the other architectures, GLSL was not made with the intent purpose of allowing a GPU to perform general purpose calculations, it has the advantages of providing enough functionality to do video decoding calculations, while being part of an API that is almost universally supported by GPUs and Operating Systems. Since ~~XBMC~~ strives to be as portable as possible, I feel that GLSL is the most advantageous. However, I will definitely not overlook other architectures. Specifically the GPGPU libraries look very promising.		At the time of this writing, I am strongly leaning towards an implementation done in OpenGL Shader Language (GLSL). While, unlike many of the other architectures, GLSL was not made with the intent purpose of allowing a GPU to perform general purpose calculations, it has the advantages of providing enough functionality to do video decoding calculations, while being part of an API that is almost universally supported by GPUs and Operating Systems. Since {{name}} strives to be as portable as possible, I feel that GLSL is the most advantageous. However, I will definitely not overlook other architectures. Specifically the GPGPU libraries look very promising.


Line 79:		Line 79:
	This is only a very tentative outline. Any given module may be completed in a longer or shorter period. It simply serves as a guideline for what I hope to achieve and the order I plan to set about doing it. At the very least I am hoping I can get the two primary modules (motion compensation and IDCT) implemented and integrated with the SVN repository over the summer.		This is only a very tentative outline. Any given module may be completed in a longer or shorter period. It simply serves as a guideline for what I hope to achieve and the order I plan to set about doing it. At the very least I am hoping I can get the two primary modules (motion compensation and IDCT) implemented and integrated with the SVN repository over the summer.

	# Architecture Research - 2 Weeks- Researching and choosing the architecture of the hardware decoder. At the end of this period I will have code running from within ~~XBMC~~ that uses the given architecture.		# Architecture Research - 2 Weeks- Researching and choosing the architecture of the hardware decoder. At the end of this period I will have code running from within {{name}} that uses the given architecture.
	# H.264 decoder Skeleton – 1 Week – A skeleton of my H.264 decoder will be written. Will be compromised of mostly the software implementation currently within ~~XBMC~~ (which I believe is handled by FFmpeg at the moment), and will be replaced with the hardware components as they are written.		# H.264 decoder Skeleton – 1 Week – A skeleton of my H.264 decoder will be written. Will be compromised of mostly the software implementation currently within {{name}} (which I believe is handled by FFmpeg at the moment), and will be replaced with the hardware components as they are written.
	# Motion Compensation - 3 weeks - Implementation of Motion Compensation using the chosen architecture		# Motion Compensation - 3 weeks - Implementation of Motion Compensation using the chosen architecture
	# Inverse Transformation - 3 Weeks - Implementation of inverse Transformation . Success will be judged by successfully lowering the amount of CPU cycles required to decode a given H.264 video over the initial software implementation		# Inverse Transformation - 3 Weeks - Implementation of inverse Transformation . Success will be judged by successfully lowering the amount of CPU cycles required to decode a given H.264 video over the initial software implementation
	# Testing and Final Commit – 2 week - - Extensive testing as well as modifying the code to fit within the ~~XBMC~~ repository. Any left over time will be spent researching other areas to accelerate with hardware.		# Testing and Final Commit – 2 week - - Extensive testing as well as modifying the code to fit within the {{name}} repository. Any left over time will be spent researching other areas to accelerate with hardware.