Albert Einstien
Young grasshopper
Thanks BP. I'll give it a go. Boy, I have yet to stump you!
EDIT: Whoo! that is really cool!
EDIT: Whoo! that is really cool!
Alas, this isn't possible. BI doesn't report the IP addresses of cameras. If it did I would have put web config links into the camera properties or something@bp2008 I may have asked this previously, but is it possible to have ui3 report the IP Address of each camera, perhaps to administrators only? And would it be wise to have the ip address have "click to load" in a web browser functionality?
FYI: Make a window stay Always On Top in Windows 10/8/7Feature Request
I like to put UI3 in the corner of my screen when I am using the computer for other things, and with ctrl ~ , and All Camera's Cycle it works very well indeed. I do perform one additional step though, and that is I use a little utility to keep it Always On Top.
Any chance of having Always On Top in the options?
The one I use is a tiny, one line code utility, found here
Always on Top: Keep Any Window Visible Always
Thanks
Oh, I get it now. I forgot that UI3 is not a stand alone application, it is a web interface. Guess I'll keep on doing it the way I'm doing. ThanksWeb sites definitely don't have the power to be always on top!!
When you record continuously you don't really have a choice and the latest alerts will usually be part of the active clip. On my main BI system I record only on motion detect without combining, so my clips are almost never still being recorded when I view them.I do have the recordings being cut to 1 hour. Is the only solution to turn that off? I'm new to BI so maybe I don't understand how it all works yet, but wouldn't the latest alert always be in a file that is still being recorded? I'm trying to view an alert right after I've been notified.
I just don't have enough verifiable information about the problem to be sure of anything. I'd need access to a clearly broken system to analyze it myself.I looked at the requests being made by UI3 and, assuming that the "time" parameter in the API is in milliseconds, I can see that the request to the server for the clip is correct. In other words, UI3 is requesting 2248121 for 10:37 where the recording file starts at 10:00 (2248/60 = 37). Wouldn't that mean the problem is in the server?