WebRTC is clearly superior for this sort of application.
WebRTC is clearly superior for this sort of application.
(add-audio-track! {:keys [silent? media-stream-track]})sdp offer expects one audio track - we can use a silent track if a text only modality is requested, however infrequent
sdp offer expects one audio track - we can use a silent track if a text only modality is requested, however infrequent
(connect! client-secret)(connect! client-secret
{:keys [buffer xf-out ex-handler xf-in content-types
media-stream-track]
:or {buffer 10 content-types #{"input_text" "input_audio"}}})Return a channel backed by an RTCPeerConnection. puts are sent of the connection's data channel and takes are received on it. Closing the channel will close all audio tracks attached to the connection, as well as the connection itself
Return a channel backed by an RTCPeerConnection. puts are sent of the connection's data channel and takes are received on it. Closing the channel will close all audio tracks attached to the connection, as well as the connection itself
(rtc-chan in out peer-connection audio-elem)A bi-directional channel that stores a reference to the audio element audio playback occurs on
A bi-directional channel that stores a reference to the audio element audio playback occurs on
(stop-tracks! peer-connection)Stop all tracks attached to the peer connection
Stop all tracks attached to the peer connection
cljdoc builds & hosts documentation for Clojure/Script libraries
| Ctrl+k | Jump to recent docs |
| ← | Move to previous article |
| → | Move to next article |
| Ctrl+/ | Jump to the search field |