Haven't visited this thread in awhile so please excuse my ignorance.
1. What happened to default2.htm?
2. What's the difference between livestream.htm and default.htm?
3. I get poor framerate (~10 fps) when viewing through UI2, and even worse framerate (~3 fps) when viewing a single camera through UI2. What can I do to get as much framerate as possible?
4. What's the recommended option for maximizing framerate? For that, is it still best to stay with the Internet Explorer ActiveX plugin?
Thanks in advance.
1) I think default2.htm is still in the zip... is it not? It is just a slightly modified version of default.htm that I have not updated in years. One of my first attempts at a better web interface.
2) Livestream.htm plays live video efficiently in any modern browser, but that is all it does. default.htm lets you view clips, change cameras, operate PTZ, etc, and only works in Internet Explorer.
3) The reason you get a low frame rate is that UI2 streams jpeg images to create the video, which is all kinds of inefficient. To get a higher frame rate you can use the experimental H.264 mode that is buried in the settings under HTML5 Canvas, but it only works in Chrome for live view and only after you've changed
Blue Iris's encoder settings. Another way to improve the frame rate is to use the low quality jpeg mode. It is this funny looking icon.
When it is red you are in low quality mode. You can configure the quality of low quality mode in UI2's settings.
4) For now, when frame rate really matters, the default.htm page is best. However rest assured I am working on a better solution and I expect it to be ready within a few months.
I'm just getting started with Blue Iris and all the features. I really love this web app you made.
Is there a feature to cycle through active cameras in full screen at timed intervals?
Only what Blue Iris supports natively. You can load any camera cycles you have configured via the dropdown box at the top of UI2.