M1900: Implement missing WebAudio node support - Revision history

Masable: /* Completed Work */

2019-05-03T11:42:24Z

Completed Work

← Older revision		Revision as of 11:42, 3 May 2019
Line 122:		Line 122:
	[https://github.com/servo/media/pull/243 Final Project Step 3 - StereoPannerNode backend]		[https://github.com/servo/media/pull/243 Final Project Step 3 - StereoPannerNode backend]

	For our third pull request, we had to implement the backend for the StereoPannerNode in servo/media. Then we had to create a runnable example that utilizes the StereoPannerNode. We designed our example so that we would initialize a StereoPannerNode with the default pan value of 0. Then, we would set the pan value to -1. Next, we would linearly ramp up the pan value to 0 and then to 1. ~~Ideally, someone would be able to~~ run this example and listen to the StereoPannerNode through speakers as its pan value changed over time, causing the sound to move from left to right.		For our third pull request, we had to implement the backend for the StereoPannerNode in servo/media. Then we had to create a runnable example that utilizes the StereoPannerNode. We designed our example so that we would initialize a StereoPannerNode with the default pan value of 0. Then, we would set the pan value to -1. Next, we would linearly ramp up the pan value to 0 and then to 1. A user could run this example and listen to the StereoPannerNode through speakers as its pan value changed over time, causing the sound to move from left to right.

	[https://github.com/servo/servo/pull/23281 Final Project Step 4 - StereoPannerNode DOM]		[https://github.com/servo/servo/pull/23281 Final Project Step 4 - StereoPannerNode DOM]

Masable: /* Introduction */

2019-05-03T11:30:05Z

Introduction

← Older revision		Revision as of 11:30, 3 May 2019
Line 2:		Line 2:
	Major browsers support the WebAudio standard which can be used to create complex media playback applications from low-level building blocks. [https://github.com/servo/servo Servo] is a new, experimental browser that supports some of these building blocks (called audio nodes); the goal of [https://github.com/servo/servo/wiki/WebAudio-JS-interfaces-student-project this project] is to improve compatibility with web content that relies on the WebAudio API by implementing missing pieces of incomplete node types (OscillatorNode) along with entire missing nodes (ConstantSourceNode and StereoPannerNode).		Major browsers support the WebAudio standard which can be used to create complex media playback applications from low-level building blocks. [https://github.com/servo/servo Servo] is a new, experimental browser that supports some of these building blocks (called audio nodes); the goal of [https://github.com/servo/servo/wiki/WebAudio-JS-interfaces-student-project this project] is to improve compatibility with web content that relies on the WebAudio API by implementing missing pieces of incomplete node types (OscillatorNode) along with entire missing nodes (ConstantSourceNode and StereoPannerNode).

	Although the GitHub description for our project is titled "Implement JS support for several missing WebAudio node types", we ~~are~~ not actually ~~programming~~ in JavaScript for this project. This project ~~involves~~ writing Rust code to implement the backend functionality of the WebAudio API, which the end user can then write JavaScript code to utilize. Therefore, the code snippets on this page are entirely in the Rust language. The only portion of our project written in JavaScript/HTML are the tests; however, the tests are not the main focus of this project (feature implementation is).		Although the GitHub description for our project is titled "Implement JS support for several missing WebAudio node types", we did not actually program in JavaScript for this project. This project involved writing Rust code to implement the backend functionality of the WebAudio API, which the end user can then write JavaScript code to utilize. Therefore, the code snippets on this page are entirely in the Rust language. The only portion of our project written in JavaScript/HTML are the tests; however, the tests are not the main focus of this project (feature implementation is).

	=== Tracking Issues ===		=== Tracking Issues ===

Masable at 11:28, 3 May 2019

2019-05-03T11:28:44Z

← Older revision		Revision as of 11:28, 3 May 2019
Line 4:		Line 4:
	Although the GitHub description for our project is titled "Implement JS support for several missing WebAudio node types", we are not actually programming in JavaScript for this project. This project involves writing Rust code to implement the backend functionality of the WebAudio API, which the end user can then write JavaScript code to utilize. Therefore, the code snippets on this page are entirely in the Rust language. The only portion of our project written in JavaScript/HTML are the tests; however, the tests are not the main focus of this project (feature implementation is).		Although the GitHub description for our project is titled "Implement JS support for several missing WebAudio node types", we are not actually programming in JavaScript for this project. This project involves writing Rust code to implement the backend functionality of the WebAudio API, which the end user can then write JavaScript code to utilize. Therefore, the code snippets on this page are entirely in the Rust language. The only portion of our project written in JavaScript/HTML are the tests; however, the tests are not the main focus of this project (feature implementation is).

	== Tracking Issues ==		=== Tracking Issues ===

	[https://github.com/servo/servo/issues/21803 ConstantSourceNode]		[https://github.com/servo/servo/issues/21803 ConstantSourceNode]
Line 10:		Line 10:
	[https://github.com/servo/servo/issues/21797 StereoPannerNode]		[https://github.com/servo/servo/issues/21797 StereoPannerNode]

	== Useful Resources ==		=== Useful Resources ===

	* [https://github.com/servo/media#servo-media Setup] for modifying the standalone media backend implementation		* [https://github.com/servo/media#servo-media Setup] for modifying the standalone media backend implementation

Masable at 11:28, 3 May 2019

2019-05-03T11:28:10Z

← Older revision		Revision as of 11:28, 3 May 2019
Line 21:		Line 21:
	* [https://doc.rust-lang.org/cargo/reference/specifying-dependencies.html#overriding-dependencies Documentation] for integrating a version of servo-media that contains your local changes into your local Servo build		* [https://doc.rust-lang.org/cargo/reference/specifying-dependencies.html#overriding-dependencies Documentation] for integrating a version of servo-media that contains your local changes into your local Servo build

	== Initial Steps (OSS Project) ==		== Project Steps ==

			=== Initial Steps (OSS Project) ===
	* Email the mozilla.dev.servo mailing list (be sure to subscribe to it first!) introducing your group and asking any necessary questions.		* Email the mozilla.dev.servo mailing list (be sure to subscribe to it first!) introducing your group and asking any necessary questions.
	* Create the DOM interface for ConstantSourceNode and implement the createConstantSource API for BaseAudioContext.		* Create the DOM interface for ConstantSourceNode and implement the createConstantSource API for BaseAudioContext.
Line 27:		Line 29:
	* Update the expected test results for the relevant tests.		* Update the expected test results for the relevant tests.

	== Subsequent Steps (Final Project) ==		=== Subsequent Steps (Final Project) ===

	* Implement an audio node message that is specific to OscillatorNode (use BiquadFilterNode as a model) which updates the node's oscillator type.		* Implement an audio node message that is specific to OscillatorNode (use BiquadFilterNode as a model) which updates the node's oscillator type.

Masable: /* Design Choices */

2019-05-03T11:26:19Z

Design Choices

← Older revision		Revision as of 11:26, 3 May 2019
Line 99:		Line 99:

	Our final version of the StereoPannerNode example involved linearly ramping the pan value from -1 to 0 and then from 0 to 1. This meant the sound moved from left to right over time.		Our final version of the StereoPannerNode example involved linearly ramping the pan value from -1 to 0 and then from 0 to 1. This meant the sound moved from left to right over time.

			The rest of our final project just involved implementing methods and therefore did not involve any design choices.

	== Completed Work ==		== Completed Work ==

Masable: /* Final Project */

2019-05-03T11:24:57Z

Final Project

← Older revision		Revision as of 11:24, 3 May 2019
Line 98:		Line 98:
	</pre>		</pre>

	Our final version of the StereoPannerNode example involved linearly ramping the pan value from -1 to 0 and then from 0 to 1. This meant ~~that~~ the sound ~~would move~~ from left to right over time.		Our final version of the StereoPannerNode example involved linearly ramping the pan value from -1 to 0 and then from 0 to 1. This meant the sound moved from left to right over time.

	== Completed Work ==		== Completed Work ==

Masable: /* Final Project */

2019-05-03T11:24:40Z

Final Project

← Older revision		Revision as of 11:24, 3 May 2019
Line 98:		Line 98:
	</pre>		</pre>

	Our final version of the StereoPannerNode example involved linearly ramping the pan value from -1 to 0 and then from 0 to 1.		Our final version of the StereoPannerNode example involved linearly ramping the pan value from -1 to 0 and then from 0 to 1. This meant that the sound would move from left to right over time.

	== Completed Work ==		== Completed Work ==

Masable: /* Final Project */

2019-05-03T11:23:44Z

Final Project

← Older revision		Revision as of 11:23, 3 May 2019
Line 73:		Line 73:
	For our final project, we had a lot of freedom to design our runnable StereoPannerNode example. For the example, we could have set the pan value to anything between -1 (full left pan) and 1 (full right pan) and then changed it any way we wished. At first, we considered setting the pan value to different values at different times, like this:		For our final project, we had a lot of freedom to design our runnable StereoPannerNode example. For the example, we could have set the pan value to anything between -1 (full left pan) and 1 (full right pan) and then changed it any way we wished. At first, we considered setting the pan value to different values at different times, like this:

	<pre		<pre>
	context.message_node(		context.message_node(
	osc,		osc,

Masable: /* Design Choices */

2019-05-03T11:23:23Z

Design Choices

@@ Line 38: / Line 38: @@
 === OSS Project ===
-Our project did not involve any design patterns since we were just implementing methods.
+Our OSS project did not involve any design patterns since we were just implementing methods.
 However, we faced multiple options of how to create and implement the ConstantSourceNode. Initially, we tried to model it on the OscillatorNode implementation, but faced a build error.
@@ Line 68: / Line 68: @@
 use servo_media::audio::constant_source_node::ConstantSourceNodeOptions as ServoMediaConstantSourceOptions;
 </pre>
 == Completed Work ==

Masable: /* OSS Project */

2019-05-03T11:16:17Z

OSS Project

← Older revision		Revision as of 11:16, 3 May 2019
Line 36:		Line 36:
	== Design Choices ==		== Design Choices ==

	= OSS Project =		=== OSS Project ===

	Our project did not involve any design patterns since we were just implementing methods.		Our project did not involve any design patterns since we were just implementing methods.