I have just a few cams setup. I have created zones to watch for activity.
With them set to mocord, they record continously. A new file is created every 10 minues. I have made sure there are no trees or bushes in the zones. Ideas?
Thanks!
Mark
mocord
Better...much better. However, I hae a B/W cam that did fine on motion & record during the evening, but during the day...nothing. I have an IP cam setup, and it is working fine. Any ideas of a cause?
Source Port is enabled
Max FPS: 20
NTSC
Capture Palett Grey
320x240
Zone is 100%
Type: Active
Preset: Fast, High Sensitivity
Alarm Color: 255/0/0
Alarm Check Method: AlarmedPixels
Mark
Source Port is enabled
Max FPS: 20
NTSC
Capture Palett Grey
320x240
Zone is 100%
Type: Active
Preset: Fast, High Sensitivity
Alarm Color: 255/0/0
Alarm Check Method: AlarmedPixels
Mark
-
- Posts: 5111
- Joined: Wed Jun 08, 2005 8:07 pm
- Location: Midlands UK
what do you mean 'nothing'?
James Wilson
Disclaimer: The above is pure theory and may work on a good day with the wind behind it. etc etc.
http://www.securitywarehouse.co.uk
Disclaimer: The above is pure theory and may work on a good day with the wind behind it. etc etc.
http://www.securitywarehouse.co.uk
To be honest, it took me some time to really understand the difference between mocord and modect from your readme. This is probably because of this:pigpen wrote:Well, maybe I am missing the point of morecord. I though it was to record only when there was activity, not all the time, to save disk space.
Non-native English speakers, like me, find difficult to understand exactly the meaning, as in non-English languages hybrid means that the result is partly made of the two.README.html wrote:This is a hybrid of Modect and Record
While, as far as I understand, mocord = modect + record. So not partly, but functionally fully, am I right? Perhaps this is why pigpen is missing its point.
Also
does not state clearly that the events generated actually mean recordings generated.README.html wrote:Modect – or MOtion DEteCTtion. All captured images will be analysed and events generated where motion is detected.
Or do I understand well, that in the eyes of ZoneMinder, event = recording? In that case, what extra events are generated during mocord, when motion is detected? Because recording is always on...
Could you please rephrase these?
Perhaps some explanation would also be good in sense of deifining 'event' and other terms used in the document.
Thanks alot, in the name of the non-native English speakers, who may be a bit confused when certain phrasing is there.
The Fast, High Sensitivity preset defaults to 8% of the zone needing to be alarmed for the record to happen. Probably works fine at night due to headlights and the like, the daytime, a person walking by the camera off 30ft probably won't trigger 8% of the zone. Try switched to Units: Pixels and dropping it down to 600 or so for the min alarmed area and see if that works. I use a min of 250 for our parking lot (has stalls more than 60ft from the camera, so need it for car prowls), and about 550 in large in-door rooms.Better...much better. However, I hae a B/W cam that did fine on motion & record during the evening, but during the day...nothing.
Preset: Fast, High Sensitivity
Alarm Check Method: AlarmedPixels
Hybrid actually is a combination of two sources, so mocord is always on recording + motion detection overlayed in the result. Great way to view, from the thumbnail, where all the activity happened across the duration of the recording, rather than having to actually watch it.Non-native English speakers, like me, find difficult to understand exactly the meaning, as in non-English languages hybrid means that the result is partly made of the two.
While, as far as I understand, mocord = modect + record. So not partly, but functionally fully, am I right? Perhaps this is why pigpen is missing its point.