You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@guacamole.apache.org by john <ba...@gmail.com> on 2017/01/10 12:44:32 UTC
0.9.10 audio input not working in firefox and chromium
hi all,
i have a working 0.9.10 setup.
i use it wih rdp and audio out works ok.
but microphone input does not.
i have enabled it in the connection settings of guac.
i can see an "record from extrernal device" in the host, and de microphone
connected to the client is working.
anyone?
where should i start debugging?
i a using FreeRDP-1.2.0-beta1-android9
--
View this message in context: http://apache-guacamole-incubating-users.2363388.n4.nabble.com/0-9-10-audio-input-not-working-in-firefox-and-chromium-tp236.html
Sent from the Apache Guacamole (incubating) - Users mailing list archive at Nabble.com.
Re: 0.9.10 audio input not working in firefox and chromium
Posted by john <ba...@gmail.com>.
here is another log from this morning.... windows 7 client and windows 7
host.
no dice...
Jan 11 10:35:29 bassan guacd[26490]: Creating new client for protocol "rdp"
Jan 11 10:35:29 bassan guacd[26490]: Connection ID is
"$d4eb0c99-efbb-4183-8d88-dec36af2d7d1"
Jan 11 10:35:30 bassan guacd[21709]: No security mode specified. Defaulting
to RDP.
Jan 11 10:35:30 bassan guacd[21709]: Resize method: none
Jan 11 10:35:30 bassan guacd[21709]: User
"@d8819d64-4c50-4d63-a62d-0496c2c1edd7" joined connection
"$d4eb0c99-efbb-4183-8d88-dec36af2d7d1" (1 users now present)
Jan 11 10:35:30 bassan guacd[21709]: Loading keymap "base"
Jan 11 10:35:30 bassan guacd[21709]: Loading keymap "en-us-qwerty"
Jan 11 10:35:30 bassan guacd[21709]: guacdr connected.
Jan 11 10:35:30 bassan guacd[21709]: guacsnd connected.
Jan 11 10:35:30 bassan guacd[21709]: Connected to RDPDR 1.12 as client
0x0009
Jan 11 10:35:30 bassan guacd[21709]: Ignoring server capability set
type=0x0001, length=44
Jan 11 10:35:30 bassan guacd[21709]: Ignoring server capability set
type=0x0002, length=8
Jan 11 10:35:30 bassan guacd[21709]: Ignoring server capability set
type=0x0003, length=8
Jan 11 10:35:30 bassan guacd[21709]: Ignoring server capability set
type=0x0004, length=8
Jan 11 10:35:30 bassan guacd[21709]: Ignoring server capability set
type=0x0005, length=8
Jan 11 10:35:30 bassan guacd[21709]: Sending capabilities...
Jan 11 10:35:30 bassan guacd[21709]: Capabilities sent.
Jan 11 10:35:30 bassan guacd[21709]: Client ID confirmed
Jan 11 10:35:31 bassan guacd[21709]: User logged on
Jan 11 10:35:31 bassan guacd[21709]: All supported devices sent.
Jan 11 10:35:31 bassan guacd[21709]: Unknown cliprdr event type: 0x5
Jan 11 10:35:32 bassan guacd[21709]: Accepted format: 16-bit PCM with 2
channels at 44100 Hz
--
View this message in context: http://apache-guacamole-incubating-users.2363388.n4.nabble.com/0-9-10-audio-input-not-working-in-firefox-and-chromium-tp236p250.html
Sent from the Apache Guacamole (incubating) - Users mailing list archive at Nabble.com.
Re: 0.9.10 audio input not working in firefox and chromium
Posted by john <ba...@gmail.com>.
yes, it is not working at all.
syslog:
Jan 10 22:58:21 bassan guacd[26490]: Creating new client for protocol "rdp"
Jan 10 22:58:21 bassan guacd[26490]: Connection ID is
"$694964a9-39fc-4c17-9436-3c6d1be49470"
Jan 10 22:58:22 bassan guacd[27793]: No security mode specified. Defaulting
to RDP.
Jan 10 22:58:22 bassan guacd[27793]: Resize method: none
Jan 10 22:58:22 bassan guacd[27793]: User
"@b559b100-31c8-4a25-969d-5081cec9f004" joined connection
"$694964a9-39fc-4c17-9436-3c6d1be49470" (1 users now present)
Jan 10 22:58:22 bassan guacd[27793]: Loading keymap "base"
Jan 10 22:58:22 bassan guacd[27793]: Loading keymap "en-us-qwerty"
Jan 10 22:58:22 bassan guacd[27793]: guacdr connected.
Jan 10 22:58:22 bassan guacd[27793]: guacsnd connected.
Jan 10 22:58:22 bassan guacd[27793]: Connected to RDPDR 1.12 as client
0x0008
Jan 10 22:58:22 bassan guacd[27793]: Ignoring server capability set
type=0x0001, length=44
Jan 10 22:58:22 bassan guacd[27793]: Ignoring server capability set
type=0x0002, length=8
Jan 10 22:58:22 bassan guacd[27793]: Ignoring server capability set
type=0x0003, length=8
Jan 10 22:58:22 bassan guacd[27793]: Ignoring server capability set
type=0x0004, length=8
Jan 10 22:58:22 bassan guacd[27793]: Ignoring server capability set
type=0x0005, length=8
Jan 10 22:58:22 bassan guacd[27793]: Sending capabilities...
Jan 10 22:58:22 bassan guacd[27793]: Capabilities sent.
Jan 10 22:58:22 bassan guacd[27793]: Client ID confirmed
Jan 10 22:58:23 bassan guacd[27793]: User logged on
Jan 10 22:58:23 bassan guacd[27793]: All supported devices sent.
Jan 10 22:58:23 bassan guacd[27793]: Unknown cliprdr event type: 0x5
Jan 10 22:58:28 bassan guacd[27793]: Accepted format: 16-bit PCM with 2
channels at 44100 Hz
--
View this message in context: http://apache-guacamole-incubating-users.2363388.n4.nabble.com/0-9-10-audio-input-not-working-in-firefox-and-chromium-tp236p247.html
Sent from the Apache Guacamole (incubating) - Users mailing list archive at Nabble.com.
Re: 0.9.10 audio input not working in firefox and chromium
Posted by Mike Jumper <mi...@guac-dev.org>.
I'll have to give this a try myself and see if I can reproduce the
problem you're seeing. I don't see any reason at the moment why audio
input shouldn't be working (assuming you haven't explicitly denied
access to audio within the browser, of course).
I believe Chrome recently changed things such that audio can only be
recorded when HTTPS is being used. I don't believe Firefox has gone
this route (yet?), however, and that may not be related to what you're
seeing. If this is the case, there should be a message to that effect
in Chrome's JavaScript error console.
- Mike
On Mon, Apr 3, 2017 at 5:31 AM, john <ba...@gmail.com> wrote:
> any update on this? microphone input is not working...
>
>
>
> --
> View this message in context: http://apache-guacamole-incubating-users.2363388.n4.nabble.com/0-9-10-audio-input-not-working-in-firefox-and-chromium-tp236p704.html
> Sent from the Apache Guacamole (incubating) - Users mailing list archive at Nabble.com.
Re: 0.9.10 audio input not working in firefox and chromium
Posted by john <ba...@gmail.com>.
any update on this? microphone input is not working...
--
View this message in context: http://apache-guacamole-incubating-users.2363388.n4.nabble.com/0-9-10-audio-input-not-working-in-firefox-and-chromium-tp236p704.html
Sent from the Apache Guacamole (incubating) - Users mailing list archive at Nabble.com.
Re: 0.9.10 audio input not working in firefox and chromium
Posted by john <ba...@gmail.com>.
can you conclude something for my logs Mike?
thanks,
--
View this message in context: http://apache-guacamole-incubating-users.2363388.n4.nabble.com/0-9-10-audio-input-not-working-in-firefox-and-chromium-tp236p256.html
Sent from the Apache Guacamole (incubating) - Users mailing list archive at Nabble.com.
Re: 0.9.10 audio input not working in firefox and chromium
Posted by Mike Jumper <mi...@guac-dev.org>.
So ... to be absolutely clear, you're saying that audio input is not
working for you with 0.9.10 at all?
What do you see in syslog from guacd?
On Tue, Jan 10, 2017 at 10:58 AM, john <ba...@gmail.com> wrote:
> nope,
> on IE, both audio in and out does not work...
>
>
>
>
> --
> View this message in context: http://apache-guacamole-incubating-users.2363388.n4.nabble.com/0-9-10-audio-input-not-working-in-firefox-and-chromium-tp236p243.html
> Sent from the Apache Guacamole (incubating) - Users mailing list archive at Nabble.com.
Re: 0.9.10 audio input not working in firefox and chromium
Posted by john <ba...@gmail.com>.
nope,
on IE, both audio in and out does not work...
--
View this message in context: http://apache-guacamole-incubating-users.2363388.n4.nabble.com/0-9-10-audio-input-not-working-in-firefox-and-chromium-tp236p243.html
Sent from the Apache Guacamole (incubating) - Users mailing list archive at Nabble.com.
Re: 0.9.10 audio input not working in firefox and chromium
Posted by Mike Jumper <mi...@guac-dev.org>.
When you say that this isn't working on Firefox and Chromium, does
that mean it has been working for you with other browsers?
- Mike
On Tue, Jan 10, 2017 at 4:45 AM, john <ba...@gmail.com> wrote:
> oh, and the host & client are both windows 7 machines.
>
>
>
> --
> View this message in context: http://apache-guacamole-incubating-users.2363388.n4.nabble.com/0-9-10-audio-input-not-working-in-firefox-and-chromium-tp236p237.html
> Sent from the Apache Guacamole (incubating) - Users mailing list archive at Nabble.com.
Re: 0.9.10 audio input not working in firefox and chromium
Posted by john <ba...@gmail.com>.
oh, and the host & client are both windows 7 machines.
--
View this message in context: http://apache-guacamole-incubating-users.2363388.n4.nabble.com/0-9-10-audio-input-not-working-in-firefox-and-chromium-tp236p237.html
Sent from the Apache Guacamole (incubating) - Users mailing list archive at Nabble.com.