As you can see from the left image there seems to be some sort of tearing in the lower portion of the screen. The right half is the same image, 2 seconds later. I have several monitors that do this to varying heights of the artifacting.
There are 16x Q-See QSC48030 cameras attached to 2x PV981 analog cards on a quad core Dell with 8gb RAM. Most of the cameras seem fine, but these 3 are throwing out a 500-1000 motion events a night.
Any idea if the cameras might be bad? The card? Bad install of the software?
Make sure you have just one camera on each capture chip in your two cards. To verifiy this, set all your monitiors to use device channel zero.
The artifacts in your picture look a lot like artifacts that occur in Zoneminder 1.24.x when you have more than one camera on a capture chip and you have the option V4L_MULTI_BUFFER enabled.
I do have V4L_MULTI_BUFFER turned off. I also have 2 cameras per chip. 4 chips, 8 channels, using channels 0 and 1. This works fine as I'm only recording at 5pfs anyway.
Do we really need to only have one camera per chip?
As you can see from the left image there seems to be some sort of tearing in the lower portion of the screen. The right half is the same image, 2 seconds later. I have several monitors that do this to varying heights of the artifacting.
There are 16x Q-See QSC48030 cameras attached to 2x PV981 analog cards on a quad core Dell with 8gb RAM. Most of the cameras seem fine, but these 3 are throwing out a 500-1000 motion events a night.
Any idea if the cameras might be bad? The card? Bad install of the software?
Something may need a UPS or new PS on computer.
Had same kind of problem under a windows set up.
Camera on same circuit as fridge, moved fridge to other circuit.
Hi, I have the same video overlay problem as you . I'm running ZM 1.24.2 on CentOS with 6 cameras attached to one 8 port PV981. Just innstalled it yesterday and didn't have time to troubleshoot. Did you fix your prb.?
Hi all, new to the forum.
Just like to say I had exactly the same issue, using ZM 1.24.1 (previously had no problems using 1.23.x) with a BT878 card installed on Debian Lenny. Switching off the V4L_MULTI_BUFFER option helped a little, but it was only when I changed CAPTURES_PER_FRAME up to 3 that this cleared up.
My grabbing hardware was running stable with no picture problems with ZM 1.22.x, an older kernel (32bit) and older motherboard for months (see thread above).
