I’m well aware of what the console is and is not intended for, hence my opening statement of “this isn’t causing me any actual problems”, but perhaps I wasn’t clear. My integrations are of course working just fine, as you’d expect.
Yes, but counterpoint: imagine designing exactly that functionality into a service knowing you are unable to deliver it. If the console being used in this fashion by hundreds of people is causing issues, then perhaps something like a timeout on live streaming should be implemented? It turns out that it doesn’t matter if I have left the console open, or have just opened it.
Anyway, I digress. I don’t actually have an issue with dropouts from this free service that neither you or I are paying for. What I found interesting, and what was really the thrust of my initial post, is what causes the dropouts to occur for every 3rd packet, and timed precisely with the node uplinks?
Are the stream dis-/re-connections between:
- the console web server and the TTS v3 back end,
- whatever JS etc is running in my browser and the console web server,
- something else?
This is really just a question about how the console is implemented, and not a problem that needs fixing per se.