-
-
Notifications
You must be signed in to change notification settings - Fork 189
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
overhaul & improve Linux screenshare #489
Conversation
FINALLY |
Seem having issues with these things i compile with your pull request and i start and it crash i tried too to start on terminal and i have an error "SIGSEGV (Address boundary error)" with terminal it loading and when it loads two second and crash again :/ i only merged your pull on the fork i do oh and i found another issue:
update: i fucked my electron installation now is working |
Okay, I'm testing this, the original theory I had on #191 (comment) seems to be correct. So, what this MR does is remove the artificial limit to 2500kbps. The workaround (moving the cursor) to temporarily prompt updates still gives some result but it's not needed anymore on my system, at 1080p. The next step would be figuring out why the resolution selector is not working properly as setting the resolution to one that can be handled and supported by most clients, especially when not using nitro, would totally solve this on sufficiently powerful connections. |
perhaps because it can only keep up with that much bitrate? iirc hardware encoding may not work with nvidia gpus, so you may be stuck with software encoding and thus have a bottleneck |
Also, on a secondary note, there seems to be something off about multimonitor setups on Wayland. Still, once this is ready, it will be a nice step in the right direction. |
I've just been able to recreate the same problem. I don't exactly know what's caused it, but it's definitely not limited to one client. |
The cursor issue isn't present when streaming an individual app. |
…that the bitrate is no longer limited to ~4620kbps
I still want to try and raise the bitrate, as its somehow locked at 4696kbps right now. and during one of my tests it randomly jumped to 8000kbps |
this has since been resolved, everything looks good to me |
This would probably require additional routing through BlackHole, or is there a system API for this? I vaguely remember something |
Thank you!
I use loopback, but that's the plan! |
Can you build this PR as a Flatpak (https://github.com/flathub/dev.vencord.Vesktop) and validate it works? We have a decent amount of users using it via Flatpak now so it needs to be tested |
I also use it as a flatpak, and I just confirmed that I am able to build and run it as a flatpak, with the streaming modifications. I didn't do any sort of rigorous testing, but I did confirm that it works. |
thanks all for working on this!! |
Thank you all for work and help ^-^ |
When will this reach the flathub version? |
When a new release is pushed for Vesktop itself, which needs to happen first, you can check the updates on the flathub repo |
expect a release some time in the next few days. still want to land a few things in vesktop before making it, and maybe experiment with electron 30 if you want new changes earlier, you can always build from source following the instructions in the readme |
How do i build the flatpak from source |
@TheRsKing https://github.com/Vencord/Vesktop?tab=readme-ov-file#building-from-source For others who want this ASAP please follow this link above and refrain from more offtopic conversations. Lots of people who follow this PR and if possible lets not spam everyone's inboxes. If you run into issues there's the Discord and GitHub issues |
basically what the title says. streaming is now smooth on linux. finally.
TODO before merge:
contentHint
and allow the user to choose between "motion" and "detail"