- Joined
- Sep 5, 2015
- Messages
- 662
- Reaction score
- 484
Thanks, Ill send you a PM. If anyone has 4.2.9.3 I'm still interested in getting a copy of the update file.I have 4.2.9.1 if you want it--PM me and I'll send you a dropbox link.
Thanks, Ill send you a PM. If anyone has 4.2.9.3 I'm still interested in getting a copy of the update file.I have 4.2.9.1 if you want it--PM me and I'll send you a dropbox link.
That's EXACTLY what I was seeing before! Thanks for posting it. I will apply the latest update and check my "dancing mulch" to see if it's still doing it.I was getting the dancing motion on one of my cams prior to installing 4.3.0.4 today. I am not getting this same thing any more (currently any how).
I've been getting this issue for some time, looks like the whole 4.3.0 and beyond has fixed it for me. Had 'dancing' grass for a few months.That's EXACTLY what I was seeing before! Thanks for posting it. I will apply the latest update and check my "dancing mulch" to see if it's still doing it.
I currently have a zone A and B setup on my driveway camera. Zone A is on the street/sidewalk and zone B is on the driveway itself. I also have it set to alert on A-B crossing and it seems to be going well so far.4.3.0.4 has fixed my alert issues but using multiple zones seems to cause "corruption". I was setting up a 3 zone trip when all of a sudden my zone masks got all messed up almost looked like random masking (all the letters instead of just the 3). Disabling zone edits and using just the one mask (A) solved it..sucks was really hoping to get zone to zone trips setup.
Welcome to the forums davem.Can I have multiple rules setup?
Example I used to have a hotspot setup on the same kind of driveway setup you have (street/sidewalk and driveway) on the driveway for any motion, now I've added a zone for the sidewalk/street and put the object detection to A-B so it should only trigger when someone/something crosses from one into the other, but can I also have another rule setup to record anything moving inside the driveway zone (like we used to have before the zones) too, but just not alert me for those ones?
You can in fact achieve this as this is exactly what I am doing. I have a clone of my driveway cam. One is set to record on all motion and the other is set to use the zone rules and trigger an alert when someone/something crosses from A-B. Clone the camera and you should be all set.Can I have multiple rules setup?
Example I used to have a hotspot setup on the same kind of driveway setup you have (street/sidewalk and driveway) on the driveway for any motion, now I've added a zone for the sidewalk/street and put the object detection to A-B so it should only trigger when someone/something crosses from one into the other, but can I also have another rule setup to record anything moving inside the driveway zone (like we used to have before the zones) too, but just not alert me for those ones?
The zone crossing rules are not working very well for me. It works OK when an object starts say in the middle of zone A and moves to the middle of zone B, but I'm finding that a small object can start in zone A but near the zone B border, move just a few pixels into zone B, and set off the alert. I realize i can make more zones and have it cross from A to B to C or set the object detection size larger, but that only delays the issue: it's still there. This brings me to my next question which is not mentioned in the help:
In the object detection dialog, there are two checkboxes so you can set the object movement to say 100 pixels and check the top box and you can also check the bottom box and enter A-B so that objects crossing from A to B or B to A will trigger. The question is, are these two boxes an AND or an OR? If you have both boxes checked as in my example, does it require than an object travel between zone A and B AND it must travel at least 100 pixels? Or is it an OR operation: an alert is triggered when something passes between A and B OR moves 100 pixels (even in a single zone)?
Mike
Thanks. That's what I figured (would make sense) but I asked because I've seen a couple instances where a small object moved from the very edge of Zone A just barely into Zone B and it set off an alert (Motion AB). To me, it looked to have moved far less than 100 pixels even though that was my setting and both boxes were checked. I'll keep an eye on it and post a clip if I can get one that is definitive but I'm wondering if the "object crosses zones" is overriding the minimum pixel path and it shouldn't be. I suppose maybe I could set a minimum pixel distance that is greater than the frame width (which should never be satisfied) and then see if cross-zone motion still sets it off. I'll try that and report back.From what I can tell they are ANDed so long as you have a check in both boxes. So you check'em both and the rule would be like you said, the object must move 100 pixels AND move from A to B BUT... it also must meet the min. object size and contrast rule before it will be considered for the object detection and zone rules.
From my testing, it appears that the pixel distance doesn't depend on which zone it is in. I have a couple 640x480 cameras split into A-G zones, equal width, left to right, so no one zone is even 100 pixels wide and alerts still fire as expected so the 100 pixel distance must be allowed to cross zones. I think where the two might conflict is if you have zones that are not overlapping or adjacent (there's a gap)... then the gap could stop the motion and not allow for the pixel distance you are looking for.Thanks for testing this for us, Mike. What I can't tell for sure about the object travels in pixels is when it starts assessing that rule. If I have a rule setup to trigger on A-B and walk around in zone A for enough time to trigger MAKE time and I have traveled back and forth across the screen in zone A to satisfy the travel distance rule too, does that mean that as soon as I cross into zone B that the event will fire? In my scenario I could infact satisfy your 2000 pixel rule even on a 640x480 camera if I am walking back and forth and BI keeps track of that. My guess is that it doesn't track it but...
That leads to another question really. Is the distance to travel based on being in zone A, zone B, or any combination to amount to 100 pixels?
No argument from me. I won't use anything else! That said, I just wish I understood some of what is going on under the hood so I could more effectively utilize it.This is pretty much what you get from BlueIris.....and by no means am i canning it as it is a fantastic bit of kit.
But it comes with very little...for want of a better word....instructions when a new version is out....or what that version contains.
But hey....i like a challenge and i must admit that the motion algorithms are getting slicker NICE!
Edit....and you wont get any bit of software updated as much as BL does