From user-return-4055-archive-asf-public=cust-asf.ponee.io@guacamole.apache.org Sun Jun 17 01:58:47 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id BD1FE180625 for ; Sun, 17 Jun 2018 01:58:46 +0200 (CEST) Received: (qmail 65105 invoked by uid 500); 16 Jun 2018 23:58:45 -0000 Mailing-List: contact user-help@guacamole.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@guacamole.apache.org Delivered-To: mailing list user@guacamole.apache.org Received: (qmail 65096 invoked by uid 99); 16 Jun 2018 23:58:45 -0000 Received: from mail-relay.apache.org (HELO mailrelay1-lw-us.apache.org) (207.244.88.152) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 16 Jun 2018 23:58:45 +0000 Received: from mail-lf0-f46.google.com (mail-lf0-f46.google.com [209.85.215.46]) by mailrelay1-lw-us.apache.org (ASF Mail Server at mailrelay1-lw-us.apache.org) with ESMTPSA id B5CBECC5 for ; Sat, 16 Jun 2018 23:58:44 +0000 (UTC) Received: by mail-lf0-f46.google.com with SMTP id x13-v6so4158193lff.10 for ; Sat, 16 Jun 2018 16:58:44 -0700 (PDT) X-Gm-Message-State: APt69E3uZSpN2o3yP3nmt5DvVAwTvEClyCv+rdNTrCAD9UdZ+uWu/yUU e9TBUlnxG8VMR2iIV6WZRN7U9DIYhbIqg2ZKNlk= X-Google-Smtp-Source: ADUXVKLslRpryMXDsUiN082D7V/w1FJcHuNmexAziHARrYMTplDXlYDnzxP3uxBjsqFMsjRqMSLbAoc1UeieKWfbD2Y= X-Received: by 2002:a2e:9187:: with SMTP id f7-v6mr4996860ljg.98.1529193523701; Sat, 16 Jun 2018 16:58:43 -0700 (PDT) MIME-Version: 1.0 References: <1529009381540-0.post@n4.nabble.com> <1529014681046-0.post@n4.nabble.com> <1529015774758-0.post@n4.nabble.com> <1529016956630-0.post@n4.nabble.com> <1529024136937-0.post@n4.nabble.com> <1529025961908-0.post@n4.nabble.com> <1529191827099-0.post@n4.nabble.com> In-Reply-To: <1529191827099-0.post@n4.nabble.com> From: Nick Couchman Date: Sat, 16 Jun 2018 19:58:32 -0400 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: adding audio support for vnc connections To: user@guacamole.apache.org Content-Type: multipart/alternative; boundary="000000000000c5ecab056ecb1c87" --000000000000c5ecab056ecb1c87 Content-Type: text/plain; charset="UTF-8" On Sat, Jun 16, 2018 at 7:30 PM robertkwild wrote: > hi, > > now i have pulseaudio working on a vnc users connection > > how do i add audio for the other vnc connection users, so they all have > audio > > atm it just works for one vnc user and not the others > > is this because pulseaudio only uses one port number? > > This gets a little beyond my knowledge of PulseAudio - I think you're probably on the right track in thinking that the single port number is the issue - not necessarily the single port number, but the single instance of PulseAudio on the VNC server, and the fact that PulseAudio is not "coupled" in any way to the VNC session, means that it's hard (impossible) for PulseAudio to know which user session should be associated with which PulseAudio client. There are two ways to work around this - one is to have a single user (VNC Session, Pulse Audio Session) per VNC server so that you just avoid the problem - you can use load balancing on the front-end to make it easy for folks to connect, and the load balancing, either through Guacamole (Connection Groups), HAProxy, or somethings like Amazon's Elastic Load Balancer (ELB) would allow you to send the VNC and Pulse connections to the same system. With 1 VNC/Pulse session per system, you don't have to worry about it. The other option would be to run PulseAudio as a user process rather than a system process, and start it up with the VNC session. The theory would be that you could put each user on a different PulseAudio port and have PulseAudio start up as a user process when VNC launches their session. In reality, I don't know how well this would work - for one thing, you'd either have to delay the startup on the PulseAudio client on the client-side until PulseAudio were running on the server side (doable with VNCViewer + PulseAudio, but harder with Guacamole), and, for another thing, you'd have to have some way to dynamically calculate and allocate PulseAudio ports, and communicate that over to the client such that either the user knows which port to connect to or the client is able to determine it automatically. This wouldn't really work at all with Guacamole, it's really only doable in a VNCViewer + PulseAudio setup, and, even then, it would take a little doing to make it happen. -Nick --000000000000c5ecab056ecb1c87 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Sat, Jun 16= , 2018 at 7:30 PM robertkwild <= robertkwild@gmail.com> wrote: