Something is definitely out-of-whack. Network delay can be caused by either the network or the BI server (if it is overloaded). Player delay is pretty much always the fault of the machine you are running UI3 on being too slow. What are you running it on? a raspberry pi?
Could be hardware accelerated decoding on your BI box being overloaded? Maybe the hardware acceleration circuits are overloaded, and switching to H.265 makes it fail to use hardware acceleration?
I was having zoom crashes and found unchecking Use RTSP/stream timecode on all my cameras stop the crashes.ok, so one thing possibly related to the UI3 interface. I have one camera that is working as it should but when as soon as I use my mouse wheel to zoom in on the camera, the screen goes black. At "fit' it reappears, but any zoom level it goes black. This is both on my normal chrome profile, and in private/incognito mode. Any ideas?
ETA: NM. I only had to wait for server to crash and restart BI server. now it's working again. this is so frustrating.
A long time ago I found a setting in UI3 that stopped any screen / sleep on my pc when I left UI3 open. Not the Timeout setting in the UI Settings, but one that stopped the PC going to sleep or the screen turning off, but only while UI3 was in the foreground. I can't find any settings to do this now and don't remember how or what I did to make this work.
@erkme73 I stopped using Intel beta as on my system it would randomly disable itself in some or all of my cams and like you I just went in and re-enabled it but clearly this indicated that there was an issue.
Since then I’ve switched to Intel VPP and I’ve since not has the acceleration disable itself so might be worth a try.
I also have a 6500 box but with an i5 so very similar hardware.
Click the icon circled in red to turn it off
View attachment 109656
I did everything possible, even factory reset the firetv still did not work.@newcomer9087
I have no idea why only some of the graphics would be missing, as they are all loaded from the same file. Normally it would be all or nothing.
I suggest you try clearing the cache in the browser, exit the browser, and open it again. Maybe try the same procedure on a different device just to make sure your UI3 files did not get corrupted.