ZoneMinder Forums

Still awaiting solution. If the command line for ffmpeg could be provided, I could then troubleshoot. I kind of think it could be the libjpegturbo.

I wonder if it could be libturbojpeg. I would like to use the regular one. Anyone know how to disable the turbo stuff?

http://i423.photobucket.com/albums/pp317/zntch/yard3.jpg after running 1/2 hour. I've already checked the log files. and posted what I got out of them. I wouldn't be here if that wasn't something I already tried. I have discovered that occasionally executing ffmpeg from shell seems to reset things ...

Camera: Lorex CVC6994CL High Resolution Color Security Camera http://lorexstore.lorextechnology.com/pdfs/CVC6994CL-SPECS_R4.pdf tuner card composite input hauppauge WinTV-PVR-150 My picture above is just the worst of how it looks. It starts out with little boxes and gradually moves up to that ...

Maybe if I could get the command line for ffmpeg it might help me in acquiring assistance?

Here is a picture of a nice yard, fence, fire pit, back alley. After running for an hour. You might even notice me standing there!

When I first start up zoneminder I get a nice crystal clear image. After a period of 15 minutes I get boxy rainbows all over the jpeg. Worse yet It detects these boxy rainbows as motion. To make sure it wasn't the driver I did a cat /dev/cxm0 >> deleteme.mpg and was able to play a nice crisp picture ...

The harddrive I was using was bad. swap space was all corrupt. I replaced the harddrive, made a fresh install. with defaults everything is working. Also 10gigs of swap space. This bug is 'closed' =)

Shared Memory:
T ID KEY MODE OWNER GROUP
m 65536 1 --rwa------ root wheel

don't know why it's root now, and at one time it was www.

I did lots of reading, tried different configs. maybe one that works? can't really know... now I get.. Jun 27 23:04:08 digitalweb zmwatch[1036]: ERR [Unable to read 'shared_data:size' from memory for monitor 1] Jun 27 23:04:08 digitalweb kernel: cxm0: encoder dma not enough buffer space free Jun 27 ...

%ipcs -l ipcs: illegal option -- l usage: ipcs [-abcmopqstyMQST] [-C corefile] [-N namelist] [-u user] %ipcs -m Shared Memory: T ID KEY MODE OWNER GROUP m 65536 2053963777 --rwa------ www www %ls -l /dev/cxm0 cr--r--r-- 1 root wheel 0, 81 Jun 27 21:02 /dev/cxm0

With no help from irc. Very useless. b# ipcs -m Shared Memory: T ID KEY MODE OWNER GROUP m 65536 2147418113 --rwa------ root wheel So I throw 2147418113 in the field that had the hex. It's kind of weird. Now I just get tons of this... Jun 25 16:14:06 digitalweb zmwatch[2905]: ERR [Can't get shared ...

Heres a better question. How do I figure out what the memory key is from freebsd?

Can anyone tell me whats wrong? Jun 25 03:25:23 -zmc_m2[10575]: ERR [Can't shmget, probably not enough shared memory space free: Invalid argument] Jun 25 03:25:23 -zmdc[1205]: ERR ['zmc -m 2' exited abnormally, exit status 255] # sysctl -a |grep shm kern.ipc.shm_allow_removed: 0 kern.ipc.shm_use ...