Audio redirect works when using the thinlinc client, but I am not able to get audio from remote server when accessing though web access. Is this possible and if so, how do I set up? Thank you.
Any update on this issue?
Hi @asdestefano, not yet I’m afraid. Any progress updates will be noted on the bug linked above, so please feel free to subscribe to that if you would like notifications.
Checking back, looks like there has still not been any movement to resolve. Is this something you all are even considering to resolve?
It is absolutely something we’re considering, having audio in Web Access would be great! So far, we’ve been focusing our resources on other things, however.
Checking back, is there any status updates on Web Access Audio?
No updates yet, I’m afraid. If you wish to influence our planning, it would be helpful to hear your use case and arguments for this?
An update here; some groundwork is ongoing that will enable future audio streams (and other types of data) to flow in parallel with the video stream.
The old infrastructure in ThinLinc Web Access was not constructed for scaling up to multiple types of streams. Recently, our developer @tobias has created a promising prototype for a new architecture that solves this problem. While we still might have to wait a while longer for audio support in Web Access, things are moving in the right direction!
You have been basing your design on OpenSSH’s battle-proven multiplexing principles, right @tobias?
That’s right! The implementation of the multiplexed WebSocket connection is based heavily on OpenSSH and SSH multiplexing protocol. This provides the foundation for audio in parallel to VNC and other potential features like printing. There’s still some work to be done on the audio front though since there doesn’t seem to be an open source project out there appropriate for our use case, so we’ll likely have to build that ourselves