![]() ![]() So RTCP feedback stream seems to be broken in this case. When camera is not activated before screen sharing RTCP PLI feedback send by receiving part cause a Chrome error "unprotect RTCP packet" in the sender user. I have continued to do some tests and what I notice is : Thank you for response and information about simulcast future implementation for screensharing. As a result, when packet loss is detected we will disable the video stream and you’ll see the “Video was disabled to save bandwidth” message.Ĭhrome is implementing simulcast for screen sharing streams too, so once it lands we should be able to take advantage of it. When using video we can lower the simulcast layer so you get a lower resolution video stream in case there is packet loss, but screen sharing doesn’t (yet) use simulcast, so there is no layer we can drop. I’m afraid there is nothing we can do at the moment, AFAIK. User A receive Nack and PLI and we don't have error.Īfter stopping packet loss simulation : screensharing stream restart after a few time.ĭo someone have some ideas or videobridge settings to have a more stable solution for screensharing ? Failed to unprotect video RTCP packet: size=26, type=206Īfter stopping packet loss simulation : unprotect Error continue and no PLI are received by A the screensharing stream never restart on user B Failed to unprotect audio RTCP packet: size=26, type=206 User A receive only nack request and every time a PLI is send by B we have this error on Chrome : In the 2 tests when packet loss start, User B send nack and PLI request. 2 users with P2P disabled ( ) and camera allowed to be used by jitsi-meet Simulate some packet loss on user A network (using "sudo tc qdisc add dev eth1 root netem loss 10%" on linux) ![]() 2 users with P2P disabled ( ) and camera sharing previously blocked ![]() I made some test with the and Chrome 60 on these test cases : Many of our user use JItsi-meet for screensharing only. User deny camera use before starting screensharing and network had some few packet lost (for example in WiFi network) The screensharing stream work for few times and suddenly block on the received part, turning into gray mode.Īfter studying error conferences we found that instabilities appear more often when : Many users report us screensharing issues with Chrome. And, you can very nicely use it for central discoverability of available sessions, simply by users (automatically or manually) joining rooms.We've recently upgrade our Jitsi-meet platform from an old to the last stable one ().Īll seems to be good and users are happy with the new version excepting the screensharing feature. Jitsi integration isn't as mature as MS Teams' Video call, but it has way less hardware problems. Element is a Slack-equivalent chat client (minus the Giphy integration) for Matrix, sooooo much better than MS Teams. If you want more, something like a MS Teams system for your own company completely hosted within the confines of your own network, with the option to integrate your own or an external video/screen/voicecall server: Matrix is the way to go there. It looks like the 1990s had a lovechild with questionable UX choices, though. ![]() Personally, I've run mumble as voice chat client (with its on-premise murmur server), and it works nicely. That would also solve the discoverability issue: a user in need of assistance would connect to the server, you'd see them and call them (or they'd call you) and then instruct them to start the desktop sharing (probably a good idea to have some inter-personal protocol in place for that – I hear windows "hotline" scams are a big thing right now "my admin guy says I mustn't open remote desktop if the other side cannot do XYZ" is a good thing). I'd like to point out that a few kilobit/s of audio probably won't hurt too much if they go to a central server, within or outside your own network. Windows comes with the server, and there's multiply RDP clients for Linux (remmina is probably a good choice), and it really works smoothly.įor the audio call thing: there's nothing peer-to-peer built into Windows, so you need to install something, and it needs to open a network socket, and then you need to find each other.Ĭonsidering that, some run-of-the-mill voicechat option is probably a good idea. Windows remote desktop for the screen share it's actually really good, in many ways. If you want a self-hosted jitsi, go for it: not impossible to set up, essentially a single docker container. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |