ZoneMinder Forums

Ok so this is related to the 8 second event issue, so I am experimenting at home with a single IP camera. Obviously no load issues because its only a single cam, the issue I have is events are being cut off and its creating loads of small 9 second events. My idea of a surveillance system would be that when motion is detected it should record until the motion has stopped then after a period stop recording.

My system isnt doing that what it does is starts recording when it detects motion then stops recording at 9secs even if there is still motion in the frame. So after googling the 8 second issue I changed the Post Event Image Count to 25fps x 20 = 500 which helps but now there are 2 issues 1st if there is no motion after a few seconds I still get a 20 second recording and if the motion is longer than 20 seconds its still cut off....

what am I missing here? Its as if ZM only uses the 1st detected motion to determine values instead of moving that timestamp to the next motion timestamp if you know what I mean?

What I am trying to achieve is if motion is detected create a single event/recording until the motion stops for x amount of time/frames?

sorry settings for monitor currently are

Id: 1
Name: Front Garage
Notes:
ServerId: 0
StorageId: 0
Type: Ffmpeg
Function: Modect
Enabled: 1
DecodingEnabled: 1
LinkedMonitors: NULL
Triggers:
ONVIF_URL:
ONVIF_Username:
ONVIF_Password:
ONVIF_Options:
Device:
Channel: 0
Format: 0
V4LMultiBuffer: NULL
V4LCapturesPerFrame: 1
Protocol: NULL
Method: rtpRtsp
Host: NULL
Port:
SubPath:
Path: rtsp://admin:xxxxxxxx@192.168.1.10
SecondPath: NULL
Options: NULL
User: NULL
Pass: NULL
Width: 1920
Height: 1080
Colours: 4
Palette: 0
Orientation: ROTATE_0
Deinterlacing: 0
DecoderHWAccelName: NULL
DecoderHWAccelDevice: NULL
SaveJPEGs: 0
VideoWriter: 2
OutputCodec: 0
Encoder: auto
OutputContainer: NULL
EncoderParameters: # Lines beginning with # are a comment
# For changing quality, use the crf option
# 1 is best, 51 is worst quality
crf=23

RecordAudio: 0
RTSPDescribe: 0
Brightness: -1
Contrast: -1
Hue: -1
Colour: -1
EventPrefix: Event-
LabelFormat: %N - %d/%m/%y %H:%M:%S
LabelX: 0
LabelY: 0
LabelSize: 1
ImageBufferCount: 5
MaxImageBufferCount: 0
WarmupCount: 0
PreEventCount: 10
PostEventCount: 500
StreamReplayBuffer: 0
AlarmFrameCount: 1
SectionLength: 600
MinSectionLength: 10
FrameSkip: 0
MotionFrameSkip: 0
AnalysisFPSLimit: NULL
AnalysisUpdateDelay: 0
MaxFPS: NULL
AlarmMaxFPS: NULL
FPSReportInterval: 100
RefBlendPerc: 12
AlarmRefBlendPerc: 3
Controllable: 0
ControlId: NULL
ControlDevice: NULL
ControlAddress: user:port@ip
AutoStopTimeout: NULL
TrackMotion: 0
TrackDelay: NULL
ReturnLocation: -1
ReturnDelay: NULL
ModectDuringPTZ: 0
DefaultRate: 100
DefaultScale: 0
DefaultCodec: auto
SignalCheckPoints: 0
SignalCheckColour: #0000be
WebColour: #6ee90a
Exif: 0
Sequence: 1
ZoneCount: 1
Refresh: NULL
Latitude: NULL
Longitude: NULL
RTSPServer: 0
RTSPStreamName:
Importance: NULL

Not sure this is even on the radar. anymore.
Storage is cheap.
So I think most of us just use Mocord to get everything, even if motion that is there is too small to trigger detection.
Not saying this isn't a problem, but the workaround is simple.

understood, well test and see.

ok not so happy with mocord it just wastes space... this is all testing so I can carry on with that 64cam NVR replacement. So whats weird about modect is that sometimes it does whats needed but its still cutting off events midway when there is still motion in the frame and then other times it works as expected?

Are you sure that ZM agrees that there is motion? Turn on saving alarm frame jpegs and see what it thinks.

ZM's default zone settings were design when the images were 640x480 or less. I find that I have to make them drastically more sensitive. Start by choosing1% or less for all the min alarm pixel and min blobs etc. Or switch units to pixels and go 3000 or less.

iconnor wrote: ↑Wed Sep 15, 2021 1:10 pm Are you sure that ZM agrees that there is motion? Turn on saving alarm frame jpegs and see what it thinks.

ZM's default zone settings were design when the images were 640x480 or less. I find that I have to make them drastically more sensitive. Start by choosing1% or less for all the min alarm pixel and min blobs etc. Or switch units to pixels and go 3000 or less.

Thank you for the input

where would I change these?

"ZM's default zone settings were design when the images were 640x480 or less. I find that I have to make them drastically more sensitive. Start by choosing1% or less for all the min alarm pixel and min blobs etc. Or switch units to pixels and go 3000 or less."

Zone mods:
go to the Console.
Click the zone column of the camera (probably/should be 1 default)
You'll see a view of the camera. If the default zone is there, it'll be all reddish - the active zone. If not, make a new one.
Click on the image or zone - the options appear.
You can adjust the zone area by dragging the corner dots - may be touchy...

thank you