Error occurs when microphone is not plugged in and when I deny microphone permission in browser. Probably a very rare case, but my microphone connection is a bit wonky and sometimes I have to re-plug it to work. It would be awesome if your app showed that I might have a problem on my end.
hmm i guess ill have to do some reading. I am using sockets.io and from what I read is it does exactly what you said. First http and then sockets (but i could be wrong).
This is anyway been a sideproject of mine to learn about web sockets.
> It seems the audio is not sent over WS until the capture is complete.
The info block indicates this is by design - 20s seems like a lot of latency, but possibly if it's got to pull down the entire audio blob before it can start playing?
Show who is talking currently. If there are more than 2 people in a convo it would be nice to have a visual of everyone there and who is talking when.
Also this would be an interesting feature for people who do podcasts and want to involve their listeners, however, there should be a way to limit or a way for the owner of the channel to grant privileges to when people can talk so not everyone jumps in at once.
29 comments
[ 2.9 ms ] story [ 61.5 ms ] threadWhen I tested, I noted a lot of latency. It seems the audio is not sent over WS until the capture is complete.
Even after finishing a recording, the other side did not receive and hear it for up to 20 seconds.
The info block indicates this is by design - 20s seems like a lot of latency, but possibly if it's got to pull down the entire audio blob before it can start playing?
Show who is talking currently. If there are more than 2 people in a convo it would be nice to have a visual of everyone there and who is talking when.
Also this would be an interesting feature for people who do podcasts and want to involve their listeners, however, there should be a way to limit or a way for the owner of the channel to grant privileges to when people can talk so not everyone jumps in at once.