Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
sudo in Windows.Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.
Meanwhile, the huge improvements that Proton has gone through since 2018 have made Windows damn near obsolete for myself and many other Linux users. I really only keep it around on my gaming machine for VR titles and if I want to use Discord screen sharing (since they still haven't fixed the lack of audio on Linux) at this point, and my main laptop has been Windows-free for years now.
since they still havenβt fixed the lack of audio on Linux
Huh, never heard of this. Do you mean that it's impossible to stream desktop audio through discord? As a workaround, you can try switching to Pipewire and patching your audio output's monitor into Discord through helvum. Or write a script that does that automatically.
Yeah, when you stream your desktop from Linux over Discord, your desktop's audio doesn't come through. It's been a known issue for years but it's a very low priority fix for Discord's developers.
Does the method you're describing play well with speaking at the same time, or do you have to decide whether you want speech or audio?
Does the method youβre describing play well with speaking at the same time
Yes.
With pipewire, it is possible to patch two sources (i.e. your microphone and an application's audio) into a single input, and it will mix them together into one stream. I just tested this with Audacity (didn't feel like booting up Discord, but it should work the same). I could hear my voice and the application's audio at the same time. This is what it looked like for me in Helvum:
The gray PortAudio block is Audacity (would be Discord in your case). "ALC3232 Analog" is my microphone (on the left) and my headphones (on the right). Music Player Daemon is the application whose audio I wanted to stream. The connection between the microphone and Audacity was made automatically as soon as I started the recording. I had to manually make the connections from Music Player Daemon to Audacity for both left and right channels. After that I could see both the mic sound and the music player daemon sound in the recording, mixed into one stream. It should work the same way with Discord. If you wanted to, for example, make your voice louder or quiter compared to the application audio, you could just adjust your mic's gain (or the application's volume) with Pavucontrol (it's an app made for Pulseaudio, but it works flawlessly under pipewire as well).
In my original comment, I said that you could patch your output's monitor back into Discord. This is a bad idea, since if anyone speaks to you in the call, that audio will also be echoed back to them. So it's better to connect the individual applications' audio into Discord as opposed to the output monitor.
Now, this could get a little tedious, making those connections by hand every time you want to screen share. So you could try to make a script that does something like that automatically. Pipewire also has the concept of a "session manager", which is basically a daemon that decides which connections are made by default, when new sources or sinks register with Pipewire. For example, wireplumber, the default session manager, was responsible for connection audacity to my microphone automatically. Maybe you could try to configure your session manager to also automatically make connection between Discord and any app that outputs audio (idk tho, never done it before).
Huh, this is all very informative. Thanks for the breakdown. I'll have to see if I can get Pipewire going on my gaming setup.
No problem! I'm just happy to spread the good word of Pipewire! Good luck with the setup!
There's also discord-screenaudio on Flathub if you don't feel like doing the work yourself. It works out of the box for me.
Oh, that's good to know. I just hope it isn't a ban risk. Well, worst case scenario, I can use my alternate account for video streaming, since i have one for using unofficial clients.
Combines the power of a really half-arsed Linux distro with the pure speed of the Windows file system.
I mean, it's slightly better than nothing, but installing a real Linux distro on Windows through eg. VirtualBox absolutely fucks it into the bin. I don't see who WSL is for. People in really locked-down corporate environments?
I stopped using virtualbox after I discovered my compiles were way faster in WSL2. It was pretty close to native Linux speed, not that I had a great way to compare it.
I don't see who WSL is for. People in really locked-down corporate environments?
That's me pretty much. Locked down low spec Windows 10 laptop that would probably suffocate under the weight of a full VM anyway, so I'm happy to have access to a proper Linux shell with a nice-ish terminal that's a lot less clunky than "git bash", MingW etc.
I use it for ad hoc scripting and things like interacting with webservices (curl), massaging text files with tools like jq, sed, awk and to use Azure and AWS cli tools to interact with cloud infrastructure.
I donβt see who WSL is for.
My guess is that this time they really wanted to pull the developer demographic over into the M$ sphere of influence. MSYS, MingW, and Git Shell already fill the same niche as WSL, so it wasn't destined to succeed. Thing is, they probably didn't expect it to succeed either. Microsoft's strategy has always been to throw a hundred dicks at the wall and hope that one of them sticks (think Zune, Windows Phone, etc). This time, Azure kind of stuck. WSL didn't. When you're as big as Microsoft, the occasional win more than covers the cost of a hundred fails.
Linux is Linux.
WSL is Bill Gates' wet fart of an OS running Linux.
Definitely not the same thing.
Is it not? It's basically a Linux container running on Windows, isn't it?