When the WebAudio constructor is called, it should only build the serverside object and only sync to the clients / be created clientside when trying to transmit.
This would allow for:
Creating a ton of streams at once and not needing a cooldown to creating the objects
Potentially allowing for a neater way to solve #11
I don't think there's any problems with the idea but if I think of any I'll just close this
When the WebAudio constructor is called, it should only build the serverside object and only sync to the clients / be created clientside when trying to transmit.
This would allow for:
I don't think there's any problems with the idea but if I think of any I'll just close this