obs-cli VS Screenshare-with-audio-on-Discord-with-Linux

Leverage OBS' API and use https://github.com/muesli/obs-cli or something similar.

Your WM/DE can respond to global hotkeys though, so you can presumably set some to issue obs-cli commands.

The only tip I'd have would be for Wayland users who suffer from not having global shortcuts work with OBS: obs-cli with obs-websocket have you covered. Set a keyboard shortcut or Stream Deck button (using streamdeck-ui) to execute an obs-cli command and you're done.

There is an obs-cli application that you can use to pass commands to OBS. Last time I tried it it wasn't fully compatible with the last OBS version, but check it out none the less, maybe they updated it.

I am on the same boat as you, though for not professional reason, but personal. Ive been using ubuntu for 3 years, off and on before that. I got a streamdeck about two years ago when I started streaming for fun and the streamdeck + OBS intergration is lack luster. There are projects that are helping to fill the gap (obs-cli and Streamdeck UI) but they lack a lot of the features offered from the official elgato control panel.

So with a little manual setup, anything that can be done from command line can be done with global shortcuts, e.g. using obs-cli for OBS shortcuts: https://i.imgur.com/NZOg68p.png

So I came up with kind of a hacky solution with a Powershell script. It disables the sceneitem in OBS with obs-cli, restarts the entire USB port with devcon64, and then reenables the OBS sceneitem.

In the meantime, you could probably use something like obs-cli, set up scripts to start and stop recording, and bind them to hotkeys in KWin.

For the moment, I'm thinking about using ahk to detect the mouse position, which would then speak to obs-cli which would switch scenes.

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