ZoneMinder Forums

I disabled all alarms (don't need 'em) and got three motion images up this time...CPU load mainly around 41%, a few spikes higher now and again.

So this is performance-oriented...

Oh yeah: what do you mean by:

"try changing the path from nph-zms to just zms in the config - paths"

You lost me completely .

Resources...yeah, lesse, ZM running and the console up with no images, CPU utilization is bouncing a bit but hovering just under 20% basically. Fire up my one "moving" image and... Well not bad, it's mainly around 22-25%, a few real brief jumps to 30ish, one quick jump to 58% for a split s...

Unless somebody can explain otherwise, what my testing says... OK, I have a pair of ImpactVCB cards with three ports each. I have three cameras per card. I can start two terminal windows, and on each do: xawtv -device /dev/video0 xawtv -device /dev/video1 ...and then in each instance, pick a composi...

Yeah, I'm back to 82, no problem there, and I've been at 320x240 for a while now. And I've made damned sure I'm all synced up - identical settings on all six cameras. At present ZM says I'm pulling between 3.3fps and 4 on each, which is usable for my application. BUT I can only pull up and watch (at...

Well THAT didn't work. Under "84" I had just one composite input that sorta halfway worked (as tested in XAWTV). "82" is reporting the right number of ports and XAWTV is perfectly happy (so long as the ZM console process is stopped).

James Wilson: you're suggesting setting the modprobe stuff to "84" instead of "82"?

I can do that...any other ideas!?

OK, with the ZM console STOPPED xawtv goes back to it's normal thing. In fact, I can run it twice from two console windows and get one video image from each camera (right now just two cameras in testing). If I restart the ZM console xawtv goes back to "rolling wacky mode". The issue with o...

OK, NOW what? XAWTV's behaviour has changed - a lot. Now, on both cards, it's rapidly "rolling" through it's three input ports per card. In other words, I get one flash of image interspersed with two flashes of blue "no input". And it behaves this way no matter which card (/dev/v...

Still some issues. Right now I've got one camera on each card. They're at what turns out to be the #3 position. In XAWTV I can now select each card device as stated, and then once it's running pick "composite 3" (and NTSC) as sources. Even though the two cameras are supposed to be identica...

Lee: It looks pretty damn promising: camera@camera-desktop:~$ xawtv -hwscan This is xawtv-3.95.dfsg.1, running on Linux/i686 (2.6.20-16-generic) looking for available devices /dev/video0: OK [ -device /dev/video0 ] type : v4l2 name : BT878 video (Osprey 100/150 (87 flags: overlay capture /dev/video1...

More info: camera@camera-desktop:~$ sudo zmu -d /dev/video0 -q -v Password: Video Capabilities Name: BT878 video (Osprey 100/150 (87 Type: 171 Can capture Can tune Overlay onto frame buffer Can clip Scalable Video Channels: 4 Audio Channels: 0 Maximum Width: 768 Maximum Height: 480 Minimum Width: 48...

OK, just starting out, trying to get a six-camera setup working (no audio). I'm running Ubuntu Feisty 32bit (I know, not Dapper) but I do seem to have all the parts together. Just...no video in ZoneMinder. Parts list: * Two Hauppauge ImpactVCB cards, the low-profile type with three RCAs and an S-Vid...