Jitsi screen sharing12/7/2023 ![]() We added this option since turning on the camera forces the browser to produce the desktopshare+camera stream at 30 fps which can be very cpu intensive and not all machines have that capability degrading the quality of the stream. We do have an option to resize the desktop share always to 720 when the camera is enabled while screenshare is in progress. if you are sharing your entire 1080p display, this will produce a 1080p desktop track.įor higher fps, please make sure you have testing.capScreenshareBitrate=0 along with the desktopSharingFrameRate.max value in your config.js. The resolution of the desktop stream depends on the resolution of the screen you are sharing, i.e. Those options will be used only for camera capture, not for screenshare. I just wasn't sure if it was a bug or Please note that the video constraints config has no effect on the resolution of the desktop share. I tried using a few browsers, Firefox, Chrome, Edge, and the electron client. ![]() The call quality slider doesn't seem to affect the screen share at all :( did we add settings to try to do high fps? It's not really designed for high fps shares. That's somewhat expected, browsers use flower fps and prefer a higher quality of picture. Note that not all browsers use the DPi multiplier. ![]() Please ask what information you need and I will gladly provide it!ĭo you use the manage call quality slider? What browser are you using? Browser / app version: firefox/edge/chrome/electron.But since the issue happens all the way up to the newest nightly version, I doubt it's that important. I can get an exact version tomorrow if it's necessary. Jitsi Meet version: I tried the current stable versions of the jitsi components as well as the unstable. Smooth 720p screen sharing Actual behavior:Ĭhoppy low frame rate 1080p screen sharing. Please if someone could help me I would be so grateful! Expected behavior: I have tried both the stable version of jitsi meet and the unstable version, it didn't make a difference. That's why I've thought my internet isn't really an issue here.Įnabling p2p seemed to help a bit, but I like raising the opus to around 128 kbps so I disable p2p. My connection is about 20-30 MBps down and about half that up. I thought that maybe it could be not enough resources from the VPS, but I even purchased a more expensive VPS with 4g of ram and 2 cpu from OVH cloud and the issue still persisted. One thing I noticed was that when the bitrate is about ~2500-2700 it's fine, but the bitrate frequently drops to below 1k and that's when the stuttering starts. Using VP8 seems to have the best result but there's still periods of intense low frames and lag. It seems to work best when I open two tabs and connect to the same call on the same machine, but when I try it with two different machines it's horribly laggy, the fps is set to 60 max and 15 min in the config. I'm testing it with a video of a video game (csgo). I've tried, over the course of hours, just about every config.js combination imaginable. It's the correct config not the example one.Īll my screen shares show up at 1920x1080 no matter what browser I try it with.įor the second issue the screen sharing itself sometimes runs at very low FPS. For the first, I set the constraints to 720 and I think Jitsi is totally ignoring it. $ConnectionException: The following addresses failed: 'localhost:5222' failed because: localhost/12ħ.0.0.1 exception: : Connection refused (Connection refused)Īt $om(SmackException.java:278)Īt .nnectUsingConfiguration(XMPPTCPConnection.java:618)Īt .nnectInternal(XMPPTCPConnection.java:890)Īt .connect(AbstractXMPPConnection.java:379)Īt .(XmppProtocolProvider.java:248)Īt .$000(XmppProtocolProvider.java:57)Īt .xmpp.XmppProtocolProvider$1.call(XmppProtocolProvider.java:229)Īt .xmpp.XmppProtocolProvider$1.call(XmppProtocolProvider.java:224)Īt $n(RetryStrategy.java:193)Īt $RunnableAdapter.call(Executors.java:511)Īt .run(FutureTask.java:266)Īt $ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)Īt $n(ScheduledThreadPoolExecutor.java:293)Īt .runWorker(ThreadPoolExecutor.java:1149)Īt $n(ThreadPoolExecutor.It's two issues really. Ng addresses failed: 'localhost:5222' failed because: localhost/127.0.0.1 exception: : Connection refused (Conn Jicofo 20:51:58.472 SEVERE: .() Failed to connect/login: The followi ![]() I am seeing errors similar to the logs below in the jicofo container in my kubernetes service: However, screensharing is still not working after getting the ports enabled on the security group. I was able to get rid of the red error messages in the network console. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |