ZoneMinder Forums

Well who has the math? I don't know what numbers to use. I can get the bytes per frame. There must be more than that times buffers.

Yeah I need to build a new recorder. How much memory do you think for a dedicated machine hosting 6-8 hi res cameras? Is 4gb enough?

I have a new camera, a Hikvision DS-2CD2042WD-I, that will work with both LibVLC and FFMPEG. Does anyone have any thoughts on pros and cons of each?

Figured it out. Searched for Error 134 here and found a posting suggesting that you lower the number of buffers in the camera setup. I lowered buffers from 50 to 30 and the camera showed up!

This is a really hi res camera. I had already lowered the resolution to 1080p. I think I'll lower it further.

Figured it out. Searched for Error 134 here and found a posting suggesting that you lower the number of buffers in the camera setup. I lowered buffers from 50 to 30 and the camera showed up!

This is a really hi res camera. I had already lowered the resolution to 1080p. I think I'll lower it further.

No help. I see a few additional message for other cameras. But this one is the same: Jan 16 11:11:07 crystal zmdc[22008]: INF ['zmc -m 8' starting at 17/01/16 11:11:07, pid = 22117] Jan 16 11:11:07 crystal zmdc[22117]: INF ['zmc -m 8' started at 17/01/16 11:11:07] Jan 16 11:11:07 crystal zmdc[22008 ...

seanb-uk wrote:My ffmpeg is version 2.8.7

Can you access those URLs in VLC or similar?

My ffmpeg is 2.6.4. It's what installed from zmrepo for Centos 6.

Yes, the URL, copied straight out of my zm config, opens and plays just fine in VLC. I restarted zm again. Same 'crashed' message.

I have a camera I am trying to get working with 1.30, a Hikvision DS-2CD2042WD-I. Many posts here and the wiki say this camera should work fine with zm. Starting zm I see: zmdc[6782]: INF ['zmc -m 8' crashed, signal 134] All my other monitors start fine. The camera is up and accessible. Does anyone ...

Just to be sure, make sure you have followed these steps exactly to setup your dedicated events drive: https://wiki.zoneminder.com/Using_a_dedicated_Hard_Drive Yeah, I'm pretty sure those are the instructions I used. ZM is working now. It was just a bunch of work to manually install the RPM and ...

Discovered I had an old ffmpeg installed from RPMForge. I deleted it and installed the ffmpeg from zmrepo. Still nothing. Monitor still crashes with Error 134.

Edit:
Found a few more RPMForge packages that I deleted and replaced with zmrepo. Monitor is still crashing.

I upgraded to 1.30 but am still not getting anything in zm. I am using your URL to access the camera and libvlc. I briefly got green status under "source" but now it stays red. I have also tried ffmpeg but still get nothing. I see in the log: zmdc[2447]: INF ['zmc -m 8' crashed, signal 134] Which is ...

I forgot I was using bind mounts on my system to point to a larger file system to store events: http://unix.stackexchange.com/questions/198590/what-is-a-bind-mount That post doesn't say how to unbind a mount so I just uncommented the lines in /etc/fstab and rebooted. But I still got the same error ...

I am seeing files created in /usr/share/zoneminder/www
Even though zm is uninstalled an all monitors stopped. What could be creating these?

I am attempting to upgrade from 1.29 to 1.30 using RPMS on CentOS 6. I keep getting error: unpacking of archive failed on file /usr/share/zoneminder/www/events: cpio: rename failed - Is a directory I tried uninstalling zm 1.29. I made sure all the monitors were stopped. I have tried manually ...

I am not getting anything under ZM 1.29. I have tried libvlc and ffmpeg. I have tried your first URL and the H264 URL. Nothing in ZM.

The camera is up and accessible directly.