Continuous recording if motion still detected (IP2M-841B)

[Bat 'n' Ball]

Hello peeps,

I have an IP2M-841B camera hooked up to my NAS and all works fine with motion detection triggering recording to the drive.

However, recordings only ever seem to last 40 or 50 seconds regardless of whether there is still motion in the frame.

Is there a setting somewhere which allows a continuous recording, if ongoing motion is detected?

I'm pretty sure continuous recording used to happen on a previous firmware but since an update it no longer does it.

Thank you for any help.

• Software Version
  2.420.AC00.17.R, Build Date: 2017-03-22
  
  WEB Version
  3.2.1.434383
  
  ONVIF Version
  2.42

[chileheadcraig]

I have the same issue. There was acutally a dog that attacked our dog in front of our house. I was glad we had the camera until I found out that the clip stopped before the "action" happened. There was serious "motion" that should have told the camera to keep recording, but it missed pretty much the whole thing. This is an important and missing feature.

It should be simple... if there is motion... keep recording....

[Bat 'n' Ball]

Yes, this should not only be simple, this should be a fundamental feature of a camera which might be used for surveillance.

Have we missed an obvious setting somewhere or is it a limitation of the firmware which I have flashed onto the camera? If the latter, are there old firmwares available somewhere so I can revert back?

[Bat 'n' Ball]

@chileheadcraig...
I managed to sort the continuous recording issue out and I hope this helps you, too.

My Event >> Video Detection >> Anti-Dither setting was on 1. I changed this to 10 and now the system continues to record, if motion continues in the frame.

The Help page for the Anti-Dither parameter states:

System only memorizes one event during the anti-dither period. The value ranges from 0s to 100s.

If I understand this rather vague documentation correctly, the 'event' means the triggered recording event and the value of 10 would mean to check every 10 seconds for another event. If there is another event, then reset the Event >> Video Detection >> Record Delay timer. My Record Delay is set to 60 seconds.

The Help page for the Record Delay parameter states:

System can delay the record for specified time after alarm ended. The value ranges from 10s to 300s.

Again, if I understand the vague documentation, this simply means how long to continue the recording after the last detected alarm (triggered event). Not, how long to delay before recording begins, as could be misinterpreted.

So, with Anti-Dither on 10 and Record Delay on 60, my camera will record for 1 minute when a motion event is detected. It will keep checking every 10 seconds for another motion event and continue to record if it is already doing so. When there is no more motion, my camera will just record for 1 more minute after the last motion event was detected.

Why my original Anti-Dither setting of 1 did not work I have no idea. It should have checked for motion every second. Maybe the fact I use a NAS to record has something to do with it and a setting of 1 is too short a period for the firmware/network combination to react to? Maybe some drives which are set to spin-down (sleep) might be a problem, too, depending on how long it takes them to wake up?

Anyway, hope this helps you

@Amcrest Support...
Lack of a manufacturer's support influences whether or not people buy your products in the future. I have received 0% support on this topic and, needless to say, this will influence whether or not I purchase your products again.

-----

[mtnflyer]

@Bat 'n' Ball, you may be on to something as to why your 1s anti-dither setting did not work. But I use 5s for all my cameras and frequently motion is cut off at the end of my event recordings (I record to SD cards). How I understand Anti-Dither (AD) is that it keeps discreet motion events that are close together from being discreet recording events.

For example, assume I have AD set to 10s. Then if I get first motion from t=0 to t=3s, then quiet from 3-5s, then motion again from 5-7s, I get a single recorded event because both motion periods happened within the AD=10s window. At least, that's what I think anti-dither should do.

But here's a real-life example from today (Settings: pre=5, AD=5, delay=10). Garbage truck pulls up in front of the house. Lots of continuous activity in the frame for over a minute. But first event recording goes from 5 seconds before truck enters the frame and ends 29 seconds after first motion (total 34s), even though motion continues. Then another recorded event starts 10s later and records the next 34s of action. Why wasn't it all one recorded event? There were no quiet periods in the frame.

I also don't know how the delay segment at the end behaves. Seems to me if motion is detected during the delay period recording should continue. But clearly it doesn't always. Do you have any more thoughts on this? And I second your comment about support!

[Mildew]

I've have mine set to a 10 sec dither and a 40 second record delay and I still miss motion at the end.

[mtnflyer]

That just sounds like a bad algorithm to me. Would be good to hear from an Amcrest engineer on this.

[chileheadcraig]

Thanks for the reply. Just saw your response. I've kinda just accepted it. May try to mess with it again.

[Rog360]

Yeap! I have the same problem. I was hoping amcrest would have fixed or made a comment on how to set it up so it captures all movement in 1 mp4...