Web Server

Introduction

A webpage does not have direct access to the data streams within our framework. The stream_audio and stream_video services open up the microphone and camera streams respectively by publishing these on secure web sockets.

Docker name: stream_audio, stream_video

Input

• sensors: microphone

• actuators: none

• parameters: none

Output

• sensors: none

• actuators: speaker

The output audio is a raw WAV file available on the secure web socket on port 11883.

The output video is a bytestream file available on the secure web socket on port 11882.

Initialization

There are no other prerequisites to run this service, simply running the services via Docker ought to start the services.

Example

To ensure stream_video and stream_audio work as intended, run the services via docker, and run the file testing_speakers_video.

Events

Both of the services do not create any events on their own.

They only respond to events. For instance, when an audio input is required by a particular application, an event ListeningAudioStart will trigger the audio stream to start. An example of an action triggering this event is start_recording. stream_video follows a similar mechanism with a different set of actions. A complete list of actions can be found at Actions.

Known Issues

There are no known issues.