...
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 WebSockets. Any camera input is available as a stream of JPG images for a WebSocket on port 11882. Any microphone input (raw WAV) is available directly for a WebSocket on port 11883. web sockets.
Docker name: stream_audio, stream_video
Input
sensors: Microphonemicrophone
actuators: Nonenone
rawparameters: Nonenone
Output
sensors: Nonenone
actuators: Speakerparameters: Nonespeaker
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.
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 or 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, but they .
They only respond to the events. For instance, where when an audio input is required in by a particular application, stream_audio will stream the audio when an action such as playAudio(Path) is initiatedan 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
No There are no known issues.