Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

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. Any camera input is available as a stream of JPG images for a web socket on port 11882. Any microphone input (raw WAV) is available directly for a web socket on port 11883.

Docker name: stream_audio, stream_video

Input

  • sensors: Microphone

  • actuators: None

  • raw: None

Output

  • sensors: None

  • actuators: Speaker

  • parameters: None

Initialisation

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

Example

No examples are available, but if one wishes to test whether their microphone and speakers function with the framework, you may refer to wizard-of-oz or the example section of Dialogflow.

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.

  • No labels