Search found 24 matches

Can anything be done to speed up clip loading on the web UI? It's painfully slow....

I just in a bug report on this. Anyone else having this issue? An event logged in broad daylight and date/time consistent on the camera feed shows up in the search as having been logged in the wee hours of the morning. I've got several events that don't remotely match the time they actually occurred.

The vast majority of the ones I'm finding with audio don't do AAC.

In searching online, I'm seeing lots of G.711, G.722, G.726, and 3GPP.

Sighthound will need to know the login credentials of the cameras to get to the video stream.

I use a netgear 24 port gigabit switch that has 12 PoE ports.

It's actually simpler than that. No need for a DHCP server at all. Add another NIC, assign it a static IP. You'll need to be on a different subnet, or a completely different IP range. Assign appropriate IP addresses to your cameras statically as well. Sighthound will (should?) be able to communicate...

My Sighthound box has two NICs....one connecting that box to the normal house LAN, and another on a segregated network specifically for the cameras. The connections are not bridged. I'll admit I don't know enough to know if this is a kosher setup or not. The NIC with the cameras is attached to my pf...

Mine often flags dogs and cats as people. I don't mind it since it's usually pretty entertaining!

I'm actually having trouble finding cameras that have AAC audio.....most of them use older protocols.

Whoa, how do we get this grid view? I don't see an option for that!

Guys- Great job on the revised recognition engine and the processor use it saves...but I have noticed that it's not picking up events as well as it used to. Link to an example: https://drive.google.com/open?id=0B4PzCV0nHHMMdDdqSmRuNjR1WUE Not only did Sighthound not flag this as "people", ...