Blue Iris

I had everything setup and working at one point. I've long since updated, and started using h.265, Intel Beta, and substreams. I don't even know what my original configuration was.

I would assume I could still get motion detection working though. I have tried Edge Vector algorithm, as well as the Gaussian (deprecated). I have tried both Zones and just simple change detection. It does not trigger on motion though. As in, I will walk out in front of the camera and jump around. However, it did just randomly trigger at one point, but there was absolutely no motion at all, this was a very static (fixed) image.

Could one of the new things be affecting it?

There are other experts that can help much more than I here but one thing I've found, and can't remember if it was by default or if I selected it, is on recordings I used the right-click menu to enable "Add motion overlays from direct-to-disk BVR". This helps you see what BI is seeing as far as motion. Some motion that is tracked (but not sufficient to trigger) will show as well as what is triggering. This assumes you're doing D2D and BVR files, and also not sure if this even helps... but it did for me in tuning my triggers.

I resolved it, it had to do with the new substream functionality.

First was that I had defined the zones I was using with the main stream. So I had to recreate the zones.

The 2nd issue was that the 'object travels pixels' was set to 100 pixels. Which is probably fine when it is 2590x1492 or whatever it was. But when using substreams it is 980x768 and 100 pixels is a HUGE amount of movement required. I set it to 30 and it is getting better now.

Thanks for the explanations, I did some testing at home and I now got it to work with lower resolution and lighting as well!

Thanks also for the explanations here.

I am learning on some old cameras - Axis 221's. Price was right.

The video resolution is 640x480. Could this be a contributing factor on why motion detection is not working with 'object detection' selected??



I can get the motion sensor to work with zone/hotspot selected. But if I also select the 'object detection', no more triggers.

Zone triggering is working well, but I would like to see if zone crossing and max size can be used to eliminate cloud/scene change triggers.

I did set the 'pixels moved' to 16, seems to be the lower limit. I do see yellow boxes around objects, but no trigger.

I have left 'object crosses zones' and 'reset detector when object size exceeds' unchecked for testing. Heck, you can leave all 3 unchecked and it makes no difference.

Sorry if this reeks of n00bness, I certainly have RTFM.