...
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 WebSocketsweb sockets. Any camera input is available as a stream of JPG images for a WebSocket web socket on port 11882. Any microphone input (raw WAV) is available directly for a WebSocket web socket on port 11883.
Docker name: stream_audio, stream_video
Input
sensors: Microphone
actuators: None
raw: None
...
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 .
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.