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

Mike Jumper closed GUACAMOLE-236.
---------------------------------
    Resolution: Invalid

I've reproduced this effect by testing with Audacity running within an RDP 
session, however the problem does not seem to be due to Guacamole. Calculating 
the number of bytes that should be recorded for a given number of seconds, I've 
verified:

# The Guacamole client sends the correct number of bytes
# guacd receives and processes the correct number of bytes
# The {{AUDIO_INPUT}} implementation within Guacamole's RDP support processes 
and sends the correct number of bytes

As the audio recorded by Audacity isn't faster in the sense that audio is being 
received overall at too slow a rate (this would result in high-pitched playback 
as well as faster playback), it looks more like Audacity is simply dropping 
part of the input, resulting in a choppy recording that seems faster. The data 
actually sent by Guacamole is correct.

Recording using a different tool, such as an online voice recorder running 
within Chrome within the RDP session, the recording sounds fine.

> Audio recorded at incorrect rate
> --------------------------------
>
>                 Key: GUACAMOLE-236
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-236
>             Project: Guacamole
>          Issue Type: Bug
>          Components: guacamole-common-js, RDP
>            Reporter: Mike Jumper
>            Assignee: Mike Jumper
>            Priority: Minor
>
> From GUACAMOLE-228:
> {quote}
> Then I've tried Firefox and it asks me every time I want to record something, 
> BUT: it works. *The sound is recorded a bit too fast, so it sounds like it's 
> sped up a bit when played.* ...
> ...
> With SSL enabled it works with Google Chrome too. What's still rather weird 
> is that all sound is played at way too much speed. *It's at least like 2x the 
> speed of the actual recording.*
> {quote}
> (emphasis added)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to