cross-posted from: https://lemmy.zip/post/26986197

Wayland and audio is fixed, but only on the canary branch for the moment, this isnt lazy either, they changed the whole screenshare flow to suit linux’s permission prompts

  • x00z@lemmy.worldEnglish
    1·
    34 minutes ago

    I’ve been using Vesktop since forever. They have had it working already for a looooong time.

  • highduc
    8·
    6 hours ago

    Whish Steam would put some effort into this too.

  • sixdripb@lemmy.world
    16·
    7 hours ago

    people on reddit are saying audio-sharing is still broken for every app using pipewire audio API directly

  • Blisterexe@lemmy.zipOP
    47·
    13 hours ago

    Note that the flathub version has not yet been updated. The version with the screenshare is 0.0.79.

  • Mikelius
    5·
    9 hours ago

    For those of us not using Wayland, any idea if this still applies? Waiting on my flatpak version to support audio sharing with screen share… And please performance improvements.

  • Zangoose@lemmy.world
    11·
    12 hours ago

    Can we get actually working global keybinds in Wayland next? Or is that a chromium/electron problem?

    • Blisterexe@lemmy.zipOP
      151·
      12 hours ago

      wayland global keybinds are not really ready yet, they’re only properly implemented in one desktop, so i don’t blame the discord devs for not adding them.

        • Zangoose@lemmy.world
          2·
          9 hours ago

          They don’t work for discord in hyprland unfortunately, it only works when I have discord tabbed in (I tried passing the shortcuts in the hyprland config file)

          AFAIK kde’s way of doing it is kind of hacky because it was called something like “legacy global keybinds” in settings but I switched off KDE a few months ago so I don’t remember the exact details.

          • Communist@lemmy.frozeninferno.xyzEnglish
            2·
            8 hours ago

            https://wiki.hyprland.org/Configuring/Binds/#global-keybinds that’s a bug then, it should be working according to the docs.

            honestly if this is for push to talk, i have a mic mute toggle in my config that might honestly be better depends on wireplumber and ripgrep though. If you bind it to something and then have it run again on release you can make it a proper push to talk key for every single application.

            $micmute = wpctl set-mute @DEFAULT_SOURCE@ toggle ; wpctl get-volume @DEFAULT_SOURCE@ | rg -q 'MUTED' && notify-send ' Mic Muted' -h string:x-canonical-private-synchronous:mic-state || notify-send --urgency=low '  Mic unmuted' -h string:x-canonical-private-synchronous:mic-state

    • jonesy@aussie.zone
      2·
      2 hours ago

      Screen sharing is a big social thing for my friends and I, lacking this functionality would mean I wouldn’t be able to interact as much sharing goofy game moments and watching movies together.

      I tried Vencord for a while, but my friends said that the quality of the stream on their end was consistently stuttering, an issue which isn’t happening for me in the official client, so the release of screen sharing on Discord stable after working so well on canary is a welcome update for me.

    • teawrecks@sopuli.xyz
      18·
      8 hours ago

      Aside from it being a main way that I spend time with friends, it’s good to see mainstream products spend effort supporting Linux as a viable gaming platform. I have friends who haven’t made the jump to Linux yet, but giving up core discord functionality was simply a dealbreaker for them.

    • Blisterexe@lemmy.zipOP
      51·
      12 hours ago

      because it’s the communications platform for gamers™.

      But seriously discord screenshare was a massive painpoint for gamers switching to linux, so it’s very nice to see it finally, properly, solved.

    • Maxx@lemmy.ca
      24·
      12 hours ago

      people like to share their screens with friends. generally so they can stream a game for them to watch or so people can watch stuff together