SoC 2021 - Revision history

J-b: /* GPU motion interpolation (mvtools) */

2021-03-01T09:11:59Z

GPU motion interpolation (mvtools)

← Older revision		Revision as of 09:11, 1 March 2021
Line 467:		Line 467:

	'''Requirements:'''		'''Requirements:'''
	- Good knowledge of both C and GLSL, especially compute shaders and other GPGPU techniques. (CUDA or OpenCL skills also transfer, though the shader will have to be GLSL)		* Good knowledge of both C and GLSL, especially compute shaders and other GPGPU techniques. (CUDA or OpenCL skills also transfer, though the shader will have to be GLSL)
	- Ideally, general knowledge of video processing techniques (e.g. motion vector search) - at least enough to be able to understand what mvtools code is doing.		* Ideally, general knowledge of video processing techniques (e.g. motion vector search) - at least enough to be able to understand what mvtools code is doing.

	Contact 'haasn'		Contact 'haasn'

J-b: /* Dolby Vision Profile 5 (IPT-PQ) */

2021-03-01T09:11:40Z

Dolby Vision Profile 5 (IPT-PQ)

← Older revision		Revision as of 09:11, 1 March 2021
Line 444:		Line 444:
	'''Requirements:'''		'''Requirements:'''

	- Knowledge of GLSL and C. Knowledge of colorspaces in general is an obvious plus, but the theory here is not important - only the implementation.		* Knowledge of '''GLSL''' and '''C'''. Knowledge of colorspaces in general is an obvious plus, but the theory here is not important - only the implementation.
	- (Possibly) Ability to reverse engineer any still-unknown or differing-from-patents parts of the stream headers.		* (Possibly) Ability to reverse engineer any still-unknown or differing-from-patents parts of the stream headers.

	Knowledge of libplacebo internals is not required, since the skeleton code for		Knowledge of libplacebo internals is not required, since the skeleton code for

J-b: /* Direct3D 11 backend */

2021-03-01T09:11:11Z

Direct3D 11 backend

← Older revision		Revision as of 09:11, 1 March 2021
Line 410:		Line 410:
	Windows are often of limited quality, especially for older hardware.		Windows are often of limited quality, especially for older hardware.

	Lots of example code for how this implementation would look can be found [as		Lots of example code for how this implementation would look can be found [https://github.com/mpv-player/mpv/blob/master/video/out/d3d11/ra_d3d11.c as part of the mpv project ].
	~~part of the mpv project](~~https://github.com/mpv-player/mpv/blob/master/video/out/d3d11/ra_d3d11.c).

	Large parts can be copy/pasted and adapted to the libplacebo API.		Large parts can be copy/pasted and adapted to the libplacebo API.
Line 422:		Line 421:
	'''Requirements:'''		'''Requirements:'''

	- Knowledge of C as well as, ideally, graphics API fundamentals. (But the latter can be learned as part of the project)		* Knowledge of '''C''' as well as, ideally, graphics API fundamentals. (But the latter can be learned as part of the project)
	- Ability to develop and test on Windows		* Ability to develop and test on Windows

	Contact 'haasn'		Contact 'haasn'

J-b: /* GPU motion interpolation (mvtools) */

2021-02-28T18:36:09Z

GPU motion interpolation (mvtools)

← Older revision		Revision as of 18:36, 28 February 2021
Line 467:		Line 467:
	These can be tackled and complete out-of-order.		These can be tackled and complete out-of-order.

	Requirements:		'''Requirements:'''
	- Good knowledge of both C and GLSL, especially compute shaders and other GPGPU		- Good knowledge of both C and GLSL, especially compute shaders and other GPGPU techniques. (CUDA or OpenCL skills also transfer, though the shader will have to be GLSL)
	techniques. (CUDA or OpenCL skills also transfer, though the shader will		- Ideally, general knowledge of video processing techniques (e.g. motion vector search) - at least enough to be able to understand what mvtools code is doing.
	have to be GLSL)
	- Ideally, general knowledge of video processing techniques (e.g. motion
	vector search) - at least enough to be able to understand what mvtools code
	is doing.

	Contact 'haasn'		Contact 'haasn'

J-b: /* GPU motion interpolation (mvtools) */

2021-02-28T18:35:44Z

GPU motion interpolation (mvtools)

← Older revision		Revision as of 18:35, 28 February 2021
Line 455:		Line 455:
	== GPU motion interpolation (mvtools) ==		== GPU motion interpolation (mvtools) ==

	Project Description:		'''Project Description'''
	~~Your goal is to develop GPU shaders for motion-adaptive frame interpolation in~~
	~~the style of [mvtools](https://github.com/dubhater/vapoursynth-mvtools).~~

	~~This~~ is ~~an open~~-~~ended project~~. ~~If not completed, any progress towards this~~		Your goal is to develop GPU shaders for motion-adaptive frame interpolation in the style of [mvtools](https://github.com/dubhater/vapoursynth-mvtools).
	~~goal is good enough~~.

	Sub-goals:		This is an open-ended project. If not completed, any progress towards this goal is good enough.
	1. Recreate the motion vector search algorithms from MAnalyze
	2. Implement the pixel masking and pixel flow algorithms from MFlowFps		'''Sub-goals:'''
			# Recreate the motion vector search algorithms from MAnalyze
			# Implement the pixel masking and pixel flow algorithms from MFlowFps

	These can be tackled and complete out-of-order.		These can be tackled and complete out-of-order.

J-b: /* Dolby Vision Profile 5 (IPT-PQ) */

2021-02-28T18:35:05Z

Dolby Vision Profile 5 (IPT-PQ)

← Older revision		Revision as of 18:35, 28 February 2021
Line 438:		Line 438:
	'''Tasks to do:'''		'''Tasks to do:'''

	1. Figure out, and (if necessary) reverse engineer the stream format for the		# Figure out, and (if necessary) reverse engineer the stream format for the Dolby reshaping algorithm described in several of their patents.
	Dolby reshaping algorithm described in several of their patents.		# Implement this algorithm in GLSL
	2. Implement this algorithm in GLSL		# Integration into libplacebo (optional)
	3. Integration into libplacebo (optional)		# Test against reference implementations of Dolby Vision profile 5
	4. Test against reference implementations of Dolby Vision profile 5

	'''Requirements:'''		'''Requirements:'''

	- Knowledge of GLSL and C. Knowledge of colorspaces in general is an		- Knowledge of GLSL and C. Knowledge of colorspaces in general is an obvious plus, but the theory here is not important - only the implementation.
	obvious plus, but the theory here is not important - only the		- (Possibly) Ability to reverse engineer any still-unknown or differing-from-patents parts of the stream headers.
	implementation.
	- (Possibly) Ability to reverse engineer any still-unknown or
	differing-from-patents parts of the stream headers.

	Knowledge of libplacebo internals is not required, since the skeleton code for		Knowledge of libplacebo internals is not required, since the skeleton code for

J-b: /* Direct3D 11 backend */

2021-02-28T18:34:27Z

Direct3D 11 backend

← Older revision		Revision as of 18:34, 28 February 2021
Line 417:		Line 417:
	'''Tasks to do:'''		'''Tasks to do:'''

	1. Add a new `pl_gpu` backend based on Direct3D 11		# Add a new `pl_gpu` backend based on Direct3D 11
	2. Integration into the build system, test framework and CI infrastructure		# Integration into the build system, test framework and CI infrastructure

	'''Requirements:'''		'''Requirements:'''

J-b: /* Ideas for libplacebo */

2021-02-28T18:34:00Z

Ideas for libplacebo

← Older revision		Revision as of 18:34, 28 February 2021
Line 405:		Line 405:

	'''Project Description:'''		'''Project Description:'''

	libplacebo uses a GPU abstraction with a number of backends. The goal would be		libplacebo uses a GPU abstraction with a number of backends. The goal would be
	to add a new backend based on Direct3D 11, since Vulkan and OpenGL support on		to add a new backend based on Direct3D 11, since Vulkan and OpenGL support on
Line 415:		Line 416:

	'''Tasks to do:'''		'''Tasks to do:'''

	1. Add a new `pl_gpu` backend based on Direct3D 11		1. Add a new `pl_gpu` backend based on Direct3D 11
	2. Integration into the build system, test framework and CI infrastructure		2. Integration into the build system, test framework and CI infrastructure

	'''Requirements:'''		'''Requirements:'''

	- Knowledge of C as well as, ideally, graphics API fundamentals. (But the latter can be learned as part of the project)		- Knowledge of C as well as, ideally, graphics API fundamentals. (But the latter can be learned as part of the project)
	- Ability to develop and test on Windows		- Ability to develop and test on Windows
Line 427:		Line 430:

	'''Project Description:'''		'''Project Description:'''

	Dolby IPT-PQ is a HDR color space similar to ITU-R ICtCp, but with proprietary		Dolby IPT-PQ is a HDR color space similar to ITU-R ICtCp, but with proprietary
	Dolby modifications (reshaping algorithm). Your goal is to implement this		Dolby modifications (reshaping algorithm). Your goal is to implement this
Line 432:		Line 436:
	patents and dumped headers.		patents and dumped headers.

	Tasks to do:		'''Tasks to do:'''

	1. Figure out, and (if necessary) reverse engineer the stream format for the		1. Figure out, and (if necessary) reverse engineer the stream format for the
	Dolby reshaping algorithm described in several of their patents.		Dolby reshaping algorithm described in several of their patents.
Line 439:		Line 444:
	4. Test against reference implementations of Dolby Vision profile 5		4. Test against reference implementations of Dolby Vision profile 5

	Requirements:		'''Requirements:'''

	- Knowledge of GLSL and C. Knowledge of colorspaces in general is an		- Knowledge of GLSL and C. Knowledge of colorspaces in general is an
	obvious plus, but the theory here is not important - only the		obvious plus, but the theory here is not important - only the

J-b: /* Dolby Vision Profile 5 (IPT-PQ) */

2021-02-28T18:33:24Z

Dolby Vision Profile 5 (IPT-PQ)

← Older revision		Revision as of 18:33, 28 February 2021
Line 426:		Line 426:
	== Dolby Vision Profile 5 (IPT-PQ) ==		== Dolby Vision Profile 5 (IPT-PQ) ==

	Project Description:		'''Project Description:'''
	Dolby IPT-PQ is a HDR color space similar to ITU-R ICtCp, but with proprietary		Dolby IPT-PQ is a HDR color space similar to ITU-R ICtCp, but with proprietary
	Dolby modifications (reshaping algorithm). Your goal is to implement this		Dolby modifications (reshaping algorithm). Your goal is to implement this

J-b: /* Ideas for libplacebo */

2021-02-28T18:28:18Z

Ideas for libplacebo

← Older revision		Revision as of 18:28, 28 February 2021
Line 404:		Line 404:
	== Direct3D 11 backend ==		== Direct3D 11 backend ==

	Project Description:		'''Project Description:'''
	libplacebo uses a GPU abstraction with a number of backends. The goal would be		libplacebo uses a GPU abstraction with a number of backends. The goal would be
	to add a new backend based on Direct3D 11, since Vulkan and OpenGL support on		to add a new backend based on Direct3D 11, since Vulkan and OpenGL support on
Line 410:		Line 410:

	Lots of example code for how this implementation would look can be found [as		Lots of example code for how this implementation would look can be found [as
	part of the mpv		part of the mpv project](https://github.com/mpv-player/mpv/blob/master/video/out/d3d11/ra_d3d11.c).
	project](https://github.com/mpv-player/mpv/blob/master/video/out/d3d11/ra_d3d11.c).
	Large parts can be copy/pasted and adapted to the libplacebo API.		Large parts can be copy/pasted and adapted to the libplacebo API.

	Tasks to do:		'''Tasks to do:'''
	1. Add a new `pl_gpu` backend based on Direct3D 11		1. Add a new `pl_gpu` backend based on Direct3D 11
	2. Integration into the build system, test framework and CI infrastructure		2. Integration into the build system, test framework and CI infrastructure

	Requirements:		'''Requirements:'''
	- Knowledge of C as well as, ideally, graphics API fundamentals. (But the		- Knowledge of C as well as, ideally, graphics API fundamentals. (But the latter can be learned as part of the project)
	latter can be learned as part of the project)
	- Ability to develop and test on Windows		- Ability to develop and test on Windows