av1
2 TopicsCropped 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!570Views0likes0Commentsplease enable AV1 playback like Chrome
could you please enable AV1 playback in .webm (edit: playback via dragging the file into the browser) like Chrome has? it also utilizes dav1d 0.9.0+ which beats the pants off the Windows Store AV1 decoder for Movies & TV which i assume nobody on these MS forums is associated with or can directly communicate with... attached is good ole Big Buck Bunny from one of the r/AV1 Discord's 8MB challenges (stuff various resolution/length videos into 8MB, which is Discord's free tier file attachment limit) @ https://hav1t.com/8MB_Challenge.html. it is AV1 video codec + Opus audio codec in webm (subset of the mkv spec).6KViews0likes5Comments