Jump to content

Hello! 👋

Our forums have moved to: discourse.symless.com

These forums are now archived (read only).

Leaderboard

  1. Rohini Dorbala

    Rohini Dorbala

    Synergy User


    • Points

      1

    • Content Count

      4


  2. Calder Lewis

    Calder Lewis

    Synergy User


    • Points

      1

    • Content Count

      4


  3. Daniel Vassy

    Daniel Vassy

    Synergy User


    • Points

      1

    • Content Count

      1


  4. josegalvez

    josegalvez

    Synergy User


    • Points

      1

    • Content Count

      28


Popular Content

Showing content with the highest reputation on 10/31/23 in all areas

  1. not sure when wayland support is planned, but linux is moving pretty fast in that direction. Doesn't effect me at the moment, but I'm sure my next upgrade will see wayland on my computer either alone or alongside X. Either way X is clearly on its way out.
    1 point
  2. Add the ability to share audio hardware as we do with peripherals like keyboard and mouse. I am aware of other projects/API available like PulseAudio ([url]https://www.freedesktop.org/wiki/Software/PulseAudio/[/url]), Jack ([url]http://jackaudio.org/[/url]) that can do audio routing through network but limited in several aspects (not user-friendly mainly). The ease of configuring synergy inspires me to have such a thing for audio hardware too.
    1 point
  3. installed RC3 into Ubuntu 23 with no problems following the 22 instructions. works great.
    1 point
  4. I will try to make a video of the issue, kind of hard to explain honestly. I just cant wait to stop using x11... feels like i'm living in the past XD
    1 point
  5. to whomever this might concern: this can simply be solved by using pulseaudio system (it's *nix native, but has binaries for Windows and OS X AFAIK). server side can be configured by adding following line to default.pa (wherever it my be on your system, *nix default is at /etc/pulse/default.pa) load-module module-native-protocol-tcp auth-ip-acl=127.0.0.1;[column separated IPs or IP ranges] auth-anonymous=1 on server you can then list sinks with pactl list sinks and then tunnel the sound from client pactl load-module module-tunnel-sink "server=[IP OF SERVER] sink
    1 point
  6. Absolutely ! This would be my #1 priority for additional features It is so frustrating to have two computers sitting next to each other, and only one producing reasonable sound... Daniel
    1 point
  7. 1 point
×
×
  • Create New...