SpacingBat3

I've realised that actually it might not be the best idea to use any stream for the screen recording. You see, any modification is likely to be found by Discord...

> If you are going to record the monitor then users will hear their voice back on the stream (...) This is actually an issue in Windows (see #186). Maybe...

> (...), also Chromium can't capture monitors Yes and no. For me it works when the monitor is set as the default device (in system settings, likely `pavucontrol` on many...

> ~~The most recently updated PulseAudio client module for Node.js~~ As a side note, I've played with this module and even if I've patched it to work with Unix sockets,...

> so basically the plan is to set the monitor as the default input device system wide? At least for now, but I may just add a flag to force...

> What do you need the sockets for? For communication with the server (both PulseAudio and PipeWire are servers and use that). Other solution is using libraries to control PulseAudio/PipeWire...

@NyaomiDEV Thank you for your information! While reading this I've realised I forgot about Wayland capturer, which I'm unsure if returns audio or not. It's definitely using PipeWire and Chromium...

> I've compiled a version with the latest commits and screen share is broken when using the --force-audio-share-support flag, the window/screen selection screen doesn't pop up and it's stuck on...

> The error is gone but unfortunately audio sharing still doesn't work for me 😢 I need to look myself how it works and if any `MediaTrack` is used for...

> still I would not ship it as is I've made it as a flag since it is not meant to be something that everyone should be able to set...