ZoneMinder Forums

Hi, i wrote the 12 byte (24bit color) 16 byte (32bit color) limitation. On ARM i believe the 32bit color is 64 bytes. Technically its possible to remove it, by adding special handling code for the remaining bytes. I want to correct what has been said in this thread. The limitation is for the total ...

A bit late but this also happened to me today, after upgrading my ZM box from CentOS6 to CentOS7. The exact same error: "bttv: probe of 0000:06:08.0 failed with error -34" I know for a fact that the card is fine because it has been working fine for years. After many attempts with the options in bttv ...

A bit late but this also happened to me today, after upgrading my ZM box from CentOS6 to CentOS7. The exact same error: "bttv: probe of 0000:06:08.0 failed with error -34" I know for a fact that the card is fine because it has been working fine for years. After many attempts with the options in bttv ...

Its already there

Hi,

Thats pleasing to hear. I also use an Odroid-C2, its an excellent device, although for ZM, the HC2\HC1 (XU4 with SATA) is probably better.
ZM v1.31 includes some AArch64 (and AArch32) optimizations for the motion detect:
https://github.com/ZoneMinder/zoneminder/pull/1881

This camera supports H264 (through V4L2), but the current ZoneMinder code doesn't support H264 for local (V4L1\V4L2) cameras.
After support for H264 capture palette is added, you should be able to capture at 1080p.

Regarding the 24bit vs 32bit debate, i have an AArch64 VPS from Scaleway (ARM64-2GB) running 1.30.4 with the neon stuff in it. So i did some tests: ZoneMinder Version: v1.30.4 with ARM Neon code merged in OS: Ubuntu 16.04.2 LTS Server AArch64 CPU: 2 cores of Cavium ThunderX RAM: 2GB, unknown speed ...

The difference should be only in zma. Make sure to use 8bit grayscale or 32bit colour, the optimized delta function isn't used with 24bit colour. This is very similar to what i am seeing on my server. Thanks for sharing :) Sometime in the future i'll probably also optimize AlarmedPixels, which ...

You can fetch the master branch. The neon stuff (AArch32 only at this moment, AArch64 very soon) and its fix was merged to master. You can get a tarball of the master branch here: https://github.com/ZoneMinder/ZoneMinder/tarball/master Keep in mind it the master branch contains untested code. It ...

Yes, my bad. It is fixed in pull request #1878:
https://github.com/ZoneMinder/ZoneMinder/pull/1878

Also, this is AArch32 (32bit mode) only. I am still working adding the optimizations for AArch64 (64bit mode).
Raspbian is 32bit, so it should work

The image is interlaced by default when using V4L2.
Please select "V4L2: Capture top field only" or "V4L2: Capture bottom field only" in the "Deinterlacing" selection.
Regarding the corruption, what card are you using?

I did this once, but for development purposes.
If you have the events as videos, create a new monitor with ffmpeg source type, and feed it with the video file. It'll work.

Hi,

This happened because ffmpeg was compiled against different versions of those two libraries than what you have installed on your system.

Kfir Itzhak

Hi,

That error means there is a resolution mismatch. The resolution you entered for the monitor does not match the actual resolution of the stream.

mastertheknife

zmfix was removed in v1.27
You can safely delete the line that runs zmfix and it should work.