-
Notifications
You must be signed in to change notification settings - Fork 905
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
[screensharing] // Google meet screen share is laggy #1848
Comments
Try to also open this one Upstream in the Hyprland Repo. Try to run Check if it improves anything. Screen sharing is a bit buggy on Hyprland. https://wiki.hyprland.org/Useful-Utilities/Screen-Sharing/ This should help |
This Should Also Help https://gist.github.com/brunoanc/2dea6ddf6974ba4e5d26c3139ffb7580 |
I have gone thought these disscusions.Solutions given here discusses about if the screenshare is not woking completely. |
I tried screensharing on this with thorium with wayland enabled and it works smoothly but on meet its lags like hell and is only 1-2 fps at max https://www.webrtc-experiment.com/Pluginfree-Screen-Sharing/ a last resort solution that works for meet is using a virtual camera to screenshare through obs it works and is better than native meet sharing |
Did anyone figure out a fix or a solution? |
Make sure your screensharing app is on wayland |
does meet work on your end ? on my laptop(non nvidia) its still doesnt at all |
Firefox is running on wayland! Idk how else to describe this, the framerate is literally 2 fps |
Google meet screen share is laggy
Description
Google meet screen share is laggy on both Firefox and brave. But when i use other service like jitsi meet ( jitsi.org ) it works smoothly.
Also some time it fails to screenshare after accepting the prompt form the browser.
Steps to Reproduce
Expected Behavior
A smooth almost realtime screen share
Actual Behavior
On starting screen share it was giving very low fps on the viewers side, the problem is not with the network.
Screenshots
On terminal I got the below errors
Environment
Date: Sun Sep 8 16:48:21 2024
Tag: v0.43.0,
Code from the terminal
#1560 has the same issue
The text was updated successfully, but these errors were encountered: