[jira] [Issue Comment Deleted] (GUACAMOLE-25) Add support for audio input

["Michael Jumper (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/GUACAMOLE-25?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Jumper updated GUACAMOLE-25:
------------------------------------
    Comment: was deleted

(was: Github user jmuehlner commented on a diff in the pull request:

    https://github.com/apache/incubator-guacamole-client/pull/9#discussion_r64326188
  
    --- Diff: guacamole-common-js/src/main/webapp/modules/AudioRecorder.js ---
    @@ -213,6 +240,14 @@ Guacamole.RawAudioRecorder = function RawAudioRecorder(stream, mimetype) {
         var writtenSamples = 0;
     
         /**
    +     * The audio stream provided by the browse, if allowed. If no stream has
    --- End diff --
    
    browser?
)

> Add support for audio input
> ---------------------------
>
>                 Key: GUACAMOLE-25
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-25
>             Project: Guacamole
>          Issue Type: New Feature
>          Components: guacamole, guacamole-common-js, libguac, RDP
>            Reporter: Michael Jumper
>            Assignee: Michael Jumper
>             Fix For: 0.9.10-incubating
>
>
> {panel:bgColor=#FFFFEE}
> *The description of this issue was copied from [GUAC-1511|https://glyptodon.org/jira/browse/GUAC-1511], an issue in the JIRA instance used by the Guacamole project prior to its acceptance into the Apache Incubator.*
> Comments, attachments, related issues, and history from prior to acceptance *have not been copied* and can be found instead at the original issue.
> {panel}
> Guacamole's protocol does already technically support audio streams in either direction, but this is only currently implemented in the server-to-client direction. The same support can be added such that client-to-server audio streams are initiated automatically (when enabled).
> The procedure could be as follows:
> # Guacamole client attempts to create an audio stream be sending an "audio" instruction to the server.
> # If audio input is supported and enabled, the server responds with an "ack" instruction indicating success. The Guacamole client then requests access to the microphone via JavaScript.
> # The browser prompts the user for access if they have not already granted/denied it. If access is granted, the audio stream begins. If access is denied, the audio stream is simply closed.
> This would require adding support for RDP's audio input channel (not part of RDPSND, but very similar). The same could no doubt also be done for PulseAudio.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)