ZoneMinder Forums

has anyone solved this problem. I am getting the identical problem here.

I found the solution. it is here
http://www.zoneminder.com/forums/viewto ... zmpathlogs

I am installing 1.22.0 for the first time. I already have 1.21.3 running. for configure (on debian) I have ./configure --with-mysql=/usr --with-webdir=/var/www/html/zm --with-cgidir=/var/www/cgi-bin --with-webuser=www-data --with-webgroup=www-data and I ended up with error zm requires openssl/md5.h ...

ok, I found my own answer.

you can use xawtv in the verbose mode with -v 2 option. this printed out the resolution being used.

somehow, xawtv is able to query to workable resolution. for zoneminder, I filled in manually, but don't know how to query for this resolution.

I am not sure if timbo_nz solved his/her problem. I am having the identical problem. xawtv is displaying in frame grab mode ok. so there is something else preventing zoneminder from capturing the video properly. quite possibly, the device has restrictions on resolution which xawtv is able to figure ...

that's what it was? how embarrassing. ok, now when I submit, all the right events come up. and after a while the events do automatically get deleted, as I wanted. one questions though, the event deletion takes a little delay, event when I manually do submit. is the filter suppose to execute right ...

so, now I understand what the submit button is for. right now there are a lot of events piled up. when I click on the All button on one of the camera names, a page with the complete list of events popup. I click show filter window, the filter page pops up. I use the pull down to display the filter ...

yes, by waving my hands in front of the camera, I can generate new events, which, as explained, continue to accumulate.

the filter is defined and saved, I assume that means it must be running.

I eliminated all email functions, both from options menu and from filter definition. there is not much in zmfilter.log except it is scanning for eents. the filter has two expresssion for selecting 2 monitor ID's, the auto delete box is selected when saved. nothing else! still the events accumulate ...

I setup a filter with automatically delete matches set to true.
this used to delete each event soon after it is collected. But, now with the same filter setting, the events don't auto delete anymore, it just accumulates with time.

what could I be doing wrong?

I did a search to find out how to make use of the monitor states. it does work, functionally, but the reaction time is VERY long. this is not meant to be something you do as a regular app feature. prob, if you only change state 2 times a day, it would be great. my question is can I possibly have the ...

in my application, there is an independent program reading frames from the same capture card. the 2nd application has its own selection of camera channel. when zm rotates thru the cameras, it affects what the 2nd app is picking up. when you say set other cmonitors to null, where should I insert the ...

this may sound like a strange question. I have a 4 channel capture card which share a single chip. zmc is rotating thru the four cameras connected to the card. zmc knows there are 4 monitors defined and go thru them in a loop. for my requirements, I sometimes need for the capture proc to stay on one ...

is there a way I can send printf statements to the shell for debugging purposes, instead of to the .log file by default?

ok, I solved the mystery. zm_monitor does run, but the printouts don't get written to file until I do a zmpkg.pl restart. so I added a fflush().

I put a bunch of printf statements in zm_monitor.cpp, and I used be able to see the print outs in zmdc.log whenever I generate alarm events. But now, no matter what I try in generating events and configuring filters. nothing is printed out. all the necessary zm daemons are running, and the web pages ...