Now hear this: Please test 1.26-beta.3!

[jarlel]

windracer, how did you fix the outdated libavcodec issue? I have the same problem related to avcodec_encode_video2..

Thanks.

Ok, I managed to compile 1.26b3. It was indeed some outdated libavcodec libraries that was causing my error. After getting all of that cleaned up, the compile finished and I was able to upgrade my existing 1.25 installation.

Still have a little work to do ... all my monitors are in black-and-white now instead of color.

edit: ah, all of my monitors' target colorspace settings had reverted to 8-bit grayscale for some reason. I set them back to 24-bit color and I'm back in business.

[windracer]

What I ended up doing was rebuilding ffmpeg from source and used shared libraries instead of static. I followed this guide:

https://ffmpeg.org/trac/ffmpeg/wiki/Ubu ... ationGuide

And it resulted in this (see below for my configure parameters):

Code: Select all

ffmpeg version git-2013-09-06-bcd1c20 Copyright (c) 2000-2013 the FFmpeg developers
  built on Sep  6 2013 10:34:00 with gcc 4.7 (Ubuntu/Linaro 4.7.3-1ubuntu1)
  configuration: --enable-gpl --enable-shared --enable-swscale --enable-nonfree --enable-version3 --enable-libass --enable-libfaac --enable-libfdk-aac --enable-libmp3lame --enable-libx264
  libavutil      52. 43.100 / 52. 43.100
  libavcodec     55. 31.101 / 55. 31.101
  libavformat    55. 16.101 / 55. 16.101
  libavdevice    55.  3.100 / 55.  3.100
  libavfilter     3. 83.104 /  3. 83.104
  libswscale      2.  5.100 /  2.  5.100
  libswresample   0. 17.103 /  0. 17.103
  libpostproc    52.  3.100 / 52.  3.100

[jarlel]

Hi, thanks windracer.

I managed to get everything to compile, but have an issue where ZM doesn't "see/find" ffmpeg.
It says: "You must have ffmpeg libraries installed to use ffmpeg cameras for monitor 1"

When I run "which ffmpeg" I get /root/bin/ffmpeg. It has enough rights etc and the PATH_FFMPEG is correct.

Any idea?

I also see in the logs issues with "Can't open memory map file '/dev/shm/zm.mmap.1': No such file or directory".
Do you know what causes this?

Thanks!

[windracer]

Does the user you run zoneminder as have the proper permissions to /dev/shm?

[jarlel]

Yes, it has...

[windracer]

I'm just guessing here, but what was your ./configure line like for zoneminder before you compiled? Maybe you were missing "--enable-mmap=yes"?

[jarlel]

It was there, the line was:

./configure --prefix=/usr/local/zm --enable-debug=no --enable-crashtrace=no --enable-mmap=yes --with-libarch=lib64 --with-mysql=/usr/bin --with-ffmpeg=/root/bin --with-webdir=/var/www/zm --with-cgidir=/var/www/zm/cgi-bin --with-webuser=www-data --with-webgroup=www-data

[windracer]

I found this:

That error is what happens after something else fails (e.g. its not the root cause). The million dollar question is why didn't the memory map file get created in the first place? Look for an error or warning in your log file just prior to the mmap error. It might be tough if your screen quickly fills up with error messages and the only important one is the very first. Also, /dev/shm is a filesystem that resides in your computer's memory. You can browser it like a normal filessytem. Make sure it exists, has enough free space, and the account running your webserver service can write to it.