Cropped WebRTC Screenshare when consuming from Edge
Hi, I am not fully sure this is the place for this issue, let me know otherwise and apologies in advance if it is not. I work with WebRTC and have recent reports that people consuming screen share produced by Chrome (in any platform) causes Edge (114) in Windows to consume the stream as cropped (only a portion of the original stream is consumed). I don't have much information yet since I wasn't able to reproduce myself by any means, the only thing that I could say is that Edge is 114, the codec stream involved is AV1, I've deployed another version to force these users to to publish using H264 and will update this thread as soon as I got more information. Could you help me with any clue about what could be the issue? Didn't find anything on the internet. [UPDATE] Edge Beta (115.0.1901.157 (Official build) beta (64-bit)): repro the issue Edge Dev (116.0.1938.10 (Official build) dev (64-bit)): works fine Edge Canary (117.0.1963.0 (Official build) canary (64-bit)): works fine [UPDATE] It does only happen when Edge Hardware Acceleration is turned on, if you turned off the issue is no longer reproducible. It also seems to happen most likely on high end machines. Bellow there are samples about how it looks and how it should look. Any help is highly appreciated!Video Constraints API to Control Call Quality
Azure Communication Services has unveiled a new capability for developers to control video quality during calls. Previously, video quality dynamically changed based on the device or network quality. With the Video Constraints API, developers can set constraints on the video resolution to ensure that a call is optimized for (1) user device and/or (2) network conditions. Examples of constraints include setting the max video resolution. For device optimization, if a user is using an older device with limited processing power for example, developers can set constraints on the video resolution to ensure that the video call runs smoothly on that device. For network optimization, there may be cases where pushing the highest video quality isn't a top priority and developers may want to limit the video bandwidth usage in the application to allow for processing of other capabilities. Learn how to implement call constraints in this documentation: Azure Communication Services Video constraints - An Azure Communication Services concept document | Microsoft Learn
Bug: Unplugging a camera in capturing breaks device enumeration
Camera device may not be removed from navigator.mediaDevices.enumerateDevices() after being unplugged. We tested several PCs with Windows 10 installed. I modified a sample of WebRTC a bit, which could help reproduce this issue. Here is the https://github.com/shaqi86/webrtc-samples/tree/gh-pages/src/content/devices/input-output Steps to Reproduce: 1) Open the demo in Edge (build and run the web server first). 2) Select an external camera and approve the access. 3) After capturing started, unplug the camera. Expected Result: Unplugged camera device should be removed from enumerateDevices(). Actual Result: Unplugged camera device is not removed from enumerateDevices(). It's not reproducible always, and possibility varies with different machines.
