• LiveLM@lemmy.zip
      link
      fedilink
      English
      arrow-up
      5
      ·
      edit-2
      11 months ago

      Nope. This will only be fixed when Discord gets their head out of their ass, unlikely to happen soon.

    • WaterWaiver@aussie.zone
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      11 months ago

      Can you describe the issue? I don’t use Discord (and I presume the problem might depend on what browser you use).

      • Clever_Clover [she/her, comrade/them]@hexbear.net
        link
        fedilink
        English
        arrow-up
        4
        ·
        11 months ago

        on discord on linux you can’t screenshare with desktop audio, I think this might be already fixed in newer electron versions (but discord is closed source and has not updated their electron in a long time)

          • mackwinston@feddit.uk
            link
            fedilink
            arrow-up
            1
            ·
            11 months ago

            As a workaround, you could use OBS and use OBS’s virtual camera so Discord is streaming what it thinks is a camera, and set up whatever you want to share on your desktop through OBS.

      • unce@lemmy.dbzer0.com
        link
        fedilink
        arrow-up
        2
        ·
        edit-2
        11 months ago

        I have discord installed from the flatpak. Screen sharing works but it doesn’t share audio from the applications. Discord-screenaudio and web browser discord have been suggested to me but they don’t work with unfocused push to talk. I’ve also tried xwaylandvideobridge but that didn’t stream the audio either.

      • peanutbutter_gas@lemm.ee
        link
        fedilink
        arrow-up
        1
        ·
        11 months ago

        I’m assuming this is a “dedicated app” (i.e. apt install discord). I was capable of streaming the video, but sound was a different beast. Audio streaming on discord was a no go. I was finally able to do it with pipewire and using discord-screenaudio

          • peanutbutter_gas@lemm.ee
            link
            fedilink
            arrow-up
            1
            ·
            8 months ago

            Sorry for late reply. I just now noticed this.

            The difference would be that a browser would likely have multiple web pages fighting for resources whereas the dedicated client would not have to fight over so many resources.

            The OS has a dedicated task scheduler that alots cpu time to each process. Some processes get preferential treatment, but most processes started on user space ( i.e.double click UI icon) are just “normal” priority.

            When a task scheduler hits on a process, that process can start executing whatever it needs to do. The problem with running discord in a browser is that the application is splitting its attention across multiple pages ( and probably other stuff ) instead of a single page.

            Basically, it’s faster to focus on painting a single canvas than it is to painting 3 at the same time.

            I’m not going to discuss shared memory and separate processes or forking. You can goggle search if you want to know more about that.