-
Notifications
You must be signed in to change notification settings - Fork 1.1k
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Screen Sharing Issue #1821
Comments
Could be related? #1798 |
Hi @DanielMcAssey and @damencho As you may be wondering too: I have checked that when video/desktop track is created on participant sharing side, track.isMuted() is false, which is good. Also at the room level, when doing the initJitsiConference() I have not set any option like startVideoMuted to true (I tried to force it to false to see if it was fixing the issue but it does not). I feel grateful you guys are helping on that |
This issue just disappeared when fixing another wss connection issue between Client and Jitis platform. Closing the issue then. |
Hi, I upgraded to a recent version of lib-jitsi-meet (e9e3709) and screen sharing stopped working. The video of desktop being shared is not showing up on other participant screens. My code is very similar to default example.js file.
There are no warning or error showing up when switching from cam to desktop in
switchVideo()
or fromonRemoteTrack()
when receiving the updated track, it just look like the new stream of video/desktop received by participants is kind of empty.By looking in more details into
track
object in console, we can see that 1rst time we receive it theMediaStreamTrack.muted
is false, but when user switches, the new track received has such field set to true. Could it be the reason why nothing is being shown up and stream is empty? See below a screenshot of such difference from one same user receiving a remoteTrack for video/cam and then for video/desktop (from same part.):Thank you
Fabrice
The text was updated successfully, but these errors were encountered: