@Sybertiger Wow, TV browsers do some weird stuff. Which is not really surprising because they are usually based on very old forks of chromium and are buggy and not kept up to date. It is a small miracle they work at all.
Based on the video with the rapid errors you showed, I've made a tweak to audio context diposal that should (in theory) prevent that issue from happening again.
The
indexOf
error message includes a line number which indicates the true problem is the HTML5 video element raised an error event, but did not provide the error message in the field that is defined in the HTML5 spec. So when UI3 tried to use the string function
indexOf
on the error message, it failed because the error message string doesn't exist. Well now UI3 will substitute in a placeholder error message
[player.error.message unavailable]
in this case so it won't crash in the same way. But you will still likely get a failure, we just won't know why it failed. You probably need to try changing UI3's H.264 player to the JavaScript player in order to completely bypass the broken component. If it lags, then limit the streaming quality to a low resolution to compensate for the inefficiency of the JavaScript player.
As for the last screenshot showing the URL, that is also strange because it should not be showing the text
&
in the address bar. That should just be
&
but for some reason the text got HTML-encoded by the web browser. Probably just another weird browser bug. Hopefully a benign one.
The changes are in
UI3-260. Please try and see if you get better results.
ALSO, if you're using the "direct to wire" streaming function, turn that off. It could cause compatibility issues especially with weird devices like a TV. But it wouldn't affect a group stream showing multiple cameras, so I'm not sure it is related here.