We have faced issues after upgrading to Web Video SDK version 1.2.0.
As soon as we start a session, the video gets frozen immediately.
Audio cracks hardly or is not working at all.
Browser Console Error
Which Web Video SDK version?
To Reproduce(If applicable)
Steps to reproduce the behavior:
- Upgrade from 1.1.7 to 1.2.0
- Join a session
- Video freeze happens and audio is not working / cracking hardly
Device (please complete the following information):
- Device: HP Laptop
- OS: Windows 10
- Browser: Chrome
- Browser Version: 99.0.4844.82
Assets: self hosted, updated and copied from NPM module
We switched from self hosted assets to the global CDN.
Shared Array Buffer: enabled using Cross-Origin-Embedder-Policy: require-corp and
Cross-Origin-Opener-Policy: same-origin configuration
Thanks for your feedback.
Could you test with our sample-app, will the same problem occur?
no i did not.
I already updated to SDK version 1.2.3 after I have seen your changelog.
The issues are fixed with that version.
- Audio and video not reconnecting properly on failover
- Known issue with the video stops playing and goes black when resolution changes to or from 720p
Now I am facing another issue.
User 1 joins a session and switches on the camera.
User 2 joins the session.
Everything is rendered correctly.
User 2 leaves the session and re-joins.
The dimensions are calculated correctly. But the video of User 1 takes the whole size of the canvas with the video. The avatar dimensions are correct.
When I resize the window, the video is adjusted to the correct dimensions.
I made the very same experience in the sample app.
Seams like a bug.
User 1 joins and switch on camera
User 2 joins and everything is fine so far.
user 2 refreshs the browser.
user 2 joins again.
There are some issues with the sample-app, we left out the logic to reset the
mediaState when leaving the session, so next time when joining the session, the
isVideoDecodeReady is falsely treated as
true, but actually, it is
false. We have updated the sample app, you can check the change.
Good morning @vic.yang
yes, this change fixed it.
We will battle test it with our QA team.
Thanks a lot for your support!
Also to you @tommy !
Happy to help @muellseb !
Thanks @vic.yang !
I have tested it. It working when we did the setting just like mentioned in the upper replies.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.