mike-jumper edited a comment on pull request #337: URL: https://github.com/apache/guacamole-server/pull/337#issuecomment-850708878
> Works perfectly smooth btw in Chrome for Mac and Chrome for Linux. It's a windows issue. I'd wager it's due to using the scriptProcessor instead of audio worker api and the UI thread is bottlenecked. This was verified on 3 different windows PCs I'm skeptical that usage of `ScriptProcessorNode` would be the cause of any issue. There is very little processing involved in streaming each packet of audio data. If the issue were that there is so much processing occurring in the UI thread that audio data is dropped, I would expect the issue to occur across all platforms and for the entire interface to feel unresponsive. The nature of the changes in this PR is to allow the server side to adjust for variance in client-side buffer size, automatically spreading things out while throttling the data rate to ensure we don't deviate from the expectations of the remote audio buffer. Perhaps there is some platform-specific difference in the client-side buffer on Windows that results in these changes not behaving as expected? What specific version of Windows and Chrome are you testing against when you see the issue? Do you see the issue when using something like Audacity (rather than Microsoft Teams, which I do not currently have access to test against)? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
