Looked at the WebSocketAudioSource class to realise that the server will only support one client at a time. Also leads to this weird (but expected, i guess) behaviour - when two clients connect sequentially, the later one has response offsets that carry over from the first one.
I can see a way to add multi-client support - happy to make a PR - but wondering if this choice is intentional? And if i am missing something?
New here, and really appreciate the detail and thought that has gone into this work already!
Looked at the
WebSocketAudioSourceclass to realise that the server will only support one client at a time. Also leads to this weird (but expected, i guess) behaviour - when two clients connect sequentially, the later one has response offsets that carry over from the first one.I can see a way to add multi-client support - happy to make a PR - but wondering if this choice is intentional? And if i am missing something?
New here, and really appreciate the detail and thought that has gone into this work already!