You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- This feature improves the user experience for rendering remote video streams.
510
512
- You can display a loading spinner over the remote video stream when isReceiving flag changes to false. You don't have to do a loading spinner, you can do anything you desire, but a loading spinner is the most common usage for better user experience.
-`size`: The stream size. The higher the stream size, the better the video quality.
516
513
517
514
```js
518
515
const size:StreamSize=remoteVideoStream.size;
519
516
```
520
517
518
+
-`size`: The stream size. The higher the stream size, the better the video quality.
519
+
521
520
## VideoStreamRenderer methods and properties
522
-
Create a `VideoStreamRendererView` instance that can be attached in the application UI to render the remote video stream, use asynchronous `createView()` method, it resolves when stream is ready to render and returns an object with `target` property that represents `video` element that can be appended anywhere in the DOM tree
523
521
524
522
```js
525
523
awaitvideoStreamRenderer.createView();
526
524
```
527
525
528
-
Dispose of `videoStreamRenderer` and all associated `VideoStreamRendererView` instances:
526
+
Create a `VideoStreamRendererView` instance that can be attached in the application UI to render the remote video stream,
527
+
use asynchronous `createView()` method, it resolves when stream is ready to render and returns an object with `target`
528
+
property that represents `video` element that can be inserted anywhere in the DOM tree
529
+
529
530
```js
530
531
videoStreamRenderer.dispose();
531
532
```
533
+
Dispose of `videoStreamRenderer` and all associated `VideoStreamRendererView` instances
- This must be done with two different call agents with different identities, hence the code snippet shows two call agents being used, each with its own Call object.
582
+
- This must be done with two different `CallAgent` instances using different identities, hence the code snippet shows two call agents being used, each with its own Call object.
581
583
- In the code example, both CallAgents are joining the same call (same call Ids). You can also join different calls with each agent and send one video on one call and a different video on the other call.
582
584
- Sending the same camera in both CallAgent, isn't supported. They must be two different cameras.
583
585
- Sending two different cameras with one CallAgent is currently not supported.
0 commit comments