Intel® Collaboration Suite for WebRTC
Community support and discussions on the Intel® Collaboration Suite for WebRTC (Intel® CS for WebRTC).
Announcements
Welcome to the Intel Community. If you get an answer you like, please mark it as an Accepted Solution to help others. Thank you!
For the latest information on Intel’s response to the Log4j/Log4Shell vulnerability, please see Intel-SA-00646

Problems with Edge

Jesse_P_
Beginner
98 Views

Hello,

I've been having some problems that are related to the Edge browser and I was wondering if anyone knows what I can do to fix them.

There are 2 different problems:

1) I'm publishing from Edge, and subscribing to the feed on another browser (Chrome). The video feed takes a long time to start after subscribing.
I get a quick callback from the subscribe function, but the video track remains muted for 15-20 seconds before video playback starts. Is this something that is known behaviour for Edge? Is there any way that I can reduce how long it takes for the video feed to start playing?

2) I'm publishing from Chrome and subscribing in Edge. The video feed becomes heavily distorted in Edge. This seems to happen when I attach the video stream to multiple video elements. Is there any way that I can avoid this problem?

For all of these scenarios I'm joining with ConferenceClient, subscribing to the video stream, and attaching the stream to a video element. I'm running Intel CS 3.5.2.

0 Kudos
2 Replies
Chunbo_H_Intel1
Employee
98 Views

Hi Jesse,

The waiting time of video subscription is due to the feedback of key frame request is not ready in Edge browser. Video will be displayed at Edge side when the key frame arrives.

As for the second question, it seems to me that you subscribed the mixed stream from MCU? Or the forward stream only from Chrome?

Thanks!

Jesse_P_
Beginner
98 Views

I am subscribing with the forward stream in Chrome.

You can ignore my second problem as I've found evidence that it's an Edge bug: https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/13986833/

Reply