ZoneMinder Forums

Like I wrote, I'm currently using only the PV-981 PCI e and the problem is NOT gone, I noticed now, so I doubt it is a bandwidth problem. The images are almost always error free, but only almost... I just had a monitor window (ZM v1.23.3) with 8 cameras (2 per channel). Two running Modect , all ...

gertjan wrote:Are you still using CAPTURES_PER_FRAME = 3 ? as this should result in a much higher internal framerate ?

No, I'm using CAPTURES_PER_FRAME=1 all the time.

I don't think there any bandwidth problem there. I had the same framerates with the same grabber card on an other motherboard (+kernel) with no errors at all. I'm grabbing 3 or 5 (alarm) 720x576 frames per second. Even if there is a bandwidth problem, this should result in lost frames, not in image ...

PROBLEM PARTLY SOLVED: As I already wrote in my my other thread , I have a - PV-981 16 port PCIe card from bluecherry.net, 2 channels used - 8 channel Kodacom clone card (with 8 bt878 and PLX PCI6150 PCI bridge, appears to be from China), picture here , 8 channels used I had image errors in ALL ...

"52 seconds" problem is fixed. Not sure what is was:
I installed a debian kernel update (2.6.26-2-xen-amd64), reinstalled dvb-multiproto v4l drivers, reinstalled ffmpeg, recompiled ZM, cleared the database and the problem is gone now.

Several Intel chipsets and VIA chipsets seem to be affected and also 32bit and 64bit kernels. So I think these are most likely not the cause. The following I observed within the last days: - If I got nothing else running except ZM and open a monitor view with 9 cameras and there is no huge movements ...

Out of curiosity, have you guys tried using V4L2 on Zoneminder 2.4.2 and have the same problems? Yes and I had the same problems: Debian Lenny with ZM 1.24.4 and SVN ffmpeg running in a Xen DomU using V4L2 and BGR24, as far as I remember. But I know that I had definitely interrupt problems with ...

Did you changed the slot when reinserting the card with heatsinks? My picture problems look exactly the same as the above screenshots. In my case I observed that the bad lines always come from other channels pictures. Since I got independent bt878 chips for each channel, the mix-up could not happen ...

With my current setup I do have some new problems, which doesn't exist before: Every 52 seconds , I got timeouts for every channel on both bt878 cards (one at the time, not all together): kernel: [88361.070183] bttv8: timeout: drop=10498 irq=4465235/8687415, risc=afec204c, bits: HSYNC OFLOW I'm not ...

I have the same problems with no solution yet and opened I thread in December 2008 (more informations about software/hardware inside): mixed up lines from different channels with 8 ch bt878 card My grabbing hardware was running stable with no picture problems with ZM 1.22.x, an older kernel (32bit ...

I have the same problems with no solution yet and opened a thread in December 2008: mixed up lines from different channels with 8 ch bt878 card Heatsinks didn't help for me at all (I tried). My grabbing hardware was running stable with no picture problems with ZM 1.22.x, an older kernel (32bit) and ...

Changed my configuration to: - Debian Lenny, kernel 2.6.26-2-xen-amd64 - ZM 1.23.3 (1.24.2 doesn't compile with Lenny's ffmpeg) - dvb-multiproto v4l drivers (forgot to mention these before) - Running everything in Dom0, after I thought DomU/shared interrupts could be the cause -> no change, problem ...

cat /proc/interrupts (inside DomU) CPU0 16: 159 Phys-irq-level bttv0 17: 31399 Phys-irq-level bttv1 18: 39229908 Phys-irq-level bttv2 19: 175673 Phys-irq-level bttv3 20: 1704220 Phys-irq-level bttv7, bttv11 21: 7995482 Phys-irq-level bttv6, bttv10 22: 1701471 Phys-irq-level bttv5, bttv9 23: 407392 ...

Your options do work, but not better than my old: the problem still exists. But it really speeds up booting, thanks! I know now I little more than before: If I start only the DomU with ZM everything works fine, no image problems. If I start a second DomU it still works fine, until a certain point ...

Sorry for the delay, I had no camera.