Differences

This shows you the differences between two versions of the page.

--- discord_screensharing [2025/12/25 16:47] – created particles
+++ discord_screensharing [2026/05/27 03:41] (current) – [The best solution so far] particles
@@ Line 7: / Line 7: @@
   * xwaylandvideobridge from KDE probably won't help unless it was bundled with your distro, which it won't be if you're using an Arch Linux derivative, like SteamOS or CachyOS.
   * Switching between the Discord flatpak and the Discord in your distro's repositories
+  * The CachyOS “discord-screenaudio” fork
 ===== The best solution so far =====
-As of December 25, 2025, the best solution I've found is to run the Flatpak version of Discord and screenshare by explicitly forcing whatever audio device is being captured to use ''pulse'' as the audio server. You can do this in some applications by setting the output to pulse directly. Some applications do not support this.
+<del>As of December 25, 2025, the best solution I've found is to run the Flatpak version of Discord and screenshare by explicitly forcing whatever audio device is being captured to use ''pulse'' as the audio server. You can do this in some applications by setting the output to pulse directly. Some applications do not support this.</del> As of May 11, 2026, my solution for sharing audio is still working, but video sharing no longer works.
 For example, if you want to use ''mpv'' and screenshare it, you can use ''mpv -ao=pulse file.mkv'' to screenshare ''file.mkv'' in Discord and have it capture automatically.
@@ Line 16: / Line 17: @@
 Incidentally, Firefox works out-of-the-box, which is interesting.
+For other apps, you can try ''SDL_AUDIODRIVER=pulseaudio,pipewire''.
 ===== qpwgraph =====
 ''qpwgraph'' is a nice Qt GUI that will tell you what the heck is going on with your audio. If you can't share audio with Discord, you can drag the audio's outputs to a Discord game capture interface if one exists manually.