electron VS Screenshare-with-audio-on-Discord-with-Linux

Still trash support on Linux too. We still cannot stream without frame rate issues and cannot stream audio with our video without piping through our mics. (the community fixed this for you: link)

SteamDeck and Linux users cannot stream properly (constant frame rate issues and absolutely no audio streaming). Its been FIXED by the community for years now (https://github.com/discord/electron/pull/22) but they just don't want to do it I guess?? If you are going to support the platform, SUPPORT THE PLATFORM. I'm not going to give you money for a product that doesn't work.

There is this https://github.com/discord/electron/tree/17-x-y from over half a year ago

But my golly gosh goodness me would I throw them a party in their honor if they would just update their 2 year out of date builtin shipped electron version that prevents all the progress we've made in the past few years from being at all relevant to their client.

You can see Discord's version of Electron on GitHub: This branch is 14 commits ahead, 2140 commits behind electron:main

The article from your quick google share says that you should use getUserMedia to capture the screen using Electron. Not only does Discord's client not use this, they even go as far as to disable it from their electron fork https://github.com/discord/electron/commit/e763956140aa6bf78f02202ab4df1e942ce672ae

They even forcefully disabled support for it in their version of electron, so there isn't even a way to use it via a betterdiscord plugin

The Discord Desktop app uses Electron and their Electron fork's source code is available on Github. If you take a look at their repo you'll see that one of the patches they apply is this one https://github.com/discord/electron/commit/ca8c921ed35c741acae57ea32c340f1eaf150044 that disables getUserMedia.

We can create virtual microphones, cameras, etc., e.g., and capture those devices using Web API's; see https://github.com/guest271314/SpeechSynthesisRecorder/issues/17, https://github.com/edisionnano/Screenshare-with-audio-on-Discord-with-Linux. See also --use-fake-device-for-media-stream, --use-file-for-fake-video-capture flags on Chromium-based browsers

Chromium and Chrome refuses to capture monitor devices on Linux. Read this https://github.com/edisionnano/Screenshare-with-audio-on-Discord-with-Linux README and the README at https://github.com/guest271314/captureSystemAudio very carefully. At best you can capture tab audio, not whatever is output to speakears and headphones, in spite of the systemAudio constraints, which is poorly named, and actually misleading.

Screen sharing with audio in Discord works fine.

If you are actually trying to record output to speakers and headphones, not just microphone input see https://github.com/edisionnano/Screenshare-with-audio-on-Discord-with-Linux, https://github.com/guest271314/captureSystemAudio.

This github project does a great job of explaining the problems with discord screensharing on linux (as well as a solution). It also mentions to a standalone project that functions as a temporary replacement for discord screen sharing if you install the dependencies (e.g. Pipewire).

Also I see all this work put in to seemingly unify the development processes between two different operating systems that somewhat undoes features that android already had, so i have to assume that this was done so android and ios could be updated with the same features simultaneously, but we already see what that looks like - a bunch of bugs on different android hardware and versions. And in all this time that this process to unify the development of the mobile app was worked on, there's a feature in the voice & video recommendations on the discord feedback website that has by far surpassed every other request in that section as something the community actually wants, a feature that has gotten daily comments for over 2 years, which is to fix the sound when sharing an application in linux - a process with a pretty thoroughly documented solution here