@@ -15,7 +15,7 @@ The package can be installed by adding `membrane_webrtc_plugin` to your list of
1515``` elixir
1616def deps do
1717 [
18- {:membrane_webrtc_plugin , " ~> 0.25.3 " }
18+ {:membrane_webrtc_plugin , " ~> 0.26.0 " }
1919 ]
2020end
2121```
@@ -34,13 +34,13 @@ To run one of these demos, type: `elixir <script_name>` and visit `http://localh
3434
3535## Exchanging Signaling Messages
3636
37- To establish a WebRTC connection you have to exchange WebRTC signaling messages between peers.
38- In ` membrane_webrtc_plugin ` it can be done by the user, with ` Membrane.WebRTC.Signaling ` or by passing WebSocket address to
37+ To establish a WebRTC connection you have to exchange WebRTC signaling messages between peers.
38+ In ` membrane_webrtc_plugin ` it can be done by the user, with ` Membrane.WebRTC.Signaling ` or by passing WebSocket address to
3939` Membrane.WebRTC.Source ` or ` Membrane.WebRTC.Sink ` , but there are two additional ways of doing it, dedicated to be used within
4040` Phoenix ` projects:
4141 - The first one is to use ` Membrane.WebRTC.PhoenixSignaling ` along with ` Membrane.WebRTC.PhoenixSignaling.Socket `
4242 - The second one is to use ` Phoenix.LiveView ` ` Membrane.WebRTC.Live.Player ` or ` Membrane.WebRTC.Live.Capture ` . These modules expect
43- ` t:Membrane.WebRTC.Signaling.t/0 ` as an argument and take advantage of WebSocket used by ` Phoenix.LiveView ` to exchange WebRTC
43+ ` t:Membrane.WebRTC.Signaling.t/0 ` as an argument and take advantage of WebSocket used by ` Phoenix.LiveView ` to exchange WebRTC
4444 signaling messages, so there is no need to add any code to handle signaling messages.
4545
4646### How to use Membrane.WebRTC.PhoenixSignaling in your own Phoenix project?
@@ -109,17 +109,17 @@ Visit `examples/phoenix_signaling/assets/js/signaling.js` to see how WebRTC sign
109109
110110## Integrating Phoenix.LiveView with Membrane WebRTC Plugin
111111
112- `membrane_webrtc_plugin` comes with two `Phoenix.LiveView`s:
113- - `Membrane.WebRTC.Live.Capture` - exchanges WebRTC signaling messages between `Membrane.WebRTC.Source` and the browser. It
114- expects the same `Membrane.WebRTC.Signaling` that has been passed to the related `Membrane.WebRTC.Source`. As a result,
115- `Membrane.Webrtc.Source` will return the media stream captured from the browser, where `Membrane.WebRTC.Live.Capture` has been
112+ `membrane_webrtc_plugin` comes with two `Phoenix.LiveView`s:
113+ - `Membrane.WebRTC.Live.Capture` - exchanges WebRTC signaling messages between `Membrane.WebRTC.Source` and the browser. It
114+ expects the same `Membrane.WebRTC.Signaling` that has been passed to the related `Membrane.WebRTC.Source`. As a result,
115+ `Membrane.Webrtc.Source` will return the media stream captured from the browser, where `Membrane.WebRTC.Live.Capture` has been
116116 rendered.
117- - `Membrane.WebRTC.Live.Player` - exchanges WebRTC signaling messages between `Membrane.WebRTC.Sink` and the browser. It
118- expects the same `Membrane.WebRTC.Signaling` that has been passed to the related `Membrane.WebRTC.Sink`. As a result,
119- `Membrane.WebRTC.Live.Player` will play media streams passed to the related `Membrane.WebRTC.Sink`. Currently supports up
117+ - `Membrane.WebRTC.Live.Player` - exchanges WebRTC signaling messages between `Membrane.WebRTC.Sink` and the browser. It
118+ expects the same `Membrane.WebRTC.Signaling` that has been passed to the related `Membrane.WebRTC.Sink`. As a result,
119+ `Membrane.WebRTC.Live.Player` will play media streams passed to the related `Membrane.WebRTC.Sink`. Currently supports up
120120 to one video stream and up to one audio stream.
121121
122- ### Usage
122+ ### Usage
123123
124124To use `Phoenix.LiveView`s from this repository, you have to use related JS hooks. To do so, add the following code snippet to `assets/js/app.js`
125125
0 commit comments