Our HTML5 client doesn't support audio redirection in any form. An option would be to implement a PulseAudio server in JavaScript on the client-side similar to how the native client does. +Proper solution. -Is quite time consuming to implement.
Some useful URLs: http://en.wikipedia.org/wiki/HTML5_Audio http://www.w3.org/2011/audio/ Also very interesting: http://caniuse.com/#search=audio In short, apparently the "Audio element" is supported by todays browsers, but is perhaps too limited for us. Investigation needed. We probably want http://caniuse.com/#feat=audio-api, but this is not supported by todays browsers. But if this is what we need, it could still be an option. For example, Firefox 25 will include support for this API and is scheduled for release tomorrow.
(In reply to comment #2) > We probably want > http://caniuse.com/#feat=audio-api, but this is not supported by todays > browsers. Not a fully accurate description; already supported by current versions of Chrome, Safari, and Opera, apparently even the Mobile version of Safari.
*** Bug 4701 has been marked as a duplicate of this bug. ***
Created attachment 663 [details] Patch for client-side We have decided to open up the client side of the EsounD server patch. When we implement this in the future we want a PulseAudio server, not EsounD.
https://github.com/novnc/noVNC/issues/302
https://community.thinlinc.com/t/web-access-audio/927
