ZoneMinder Forums

might be a permission problem on your USB cam at /dev/video0 - set it to 777 just to be sure

it's a USB problem - ALL the available bandwidth gets reserved for the first cam, and if you plug in another one then sometimes noone gets the bandwidth (for reasons unknown to me) most motherboards have only one USB circuit - and all 6,8 or 10 usb ports run thru an internal hub from that one (look ...

some USB cams don't have the crop command properly built in, so they fail - i believe it's a cam problem and not ZM - there are many posts here in the ZM forums about it. try a different resolution and see if that works for your cam also you may run into trouble running several USB cams - depending ...

look at the log files and post some of them! without a more specific error message noone could help you ...

get 1.24.2 from ftp://ftp.northern-ridge.com.au/zoneminder/ and try it again IF the key problem comes up again try changing the config key to what's in the error messages eg 0x7a6d0001 etc they are usually numbers in sequence when you set up the cams but when you delete cams things might get a bit ...

shorten the path usually you don't need the http:// part of it anyways - IF you've checked HTTP as the protocol, and for the IP you could create an entry in your hosts file and call your cam e.g. 'C1' unfortunately the problem is mysql - there's some variable that handles the path and was set up too ...

i had problems setting a fixed bitrate for ffmpeg while creating a video from the events. basically the same happened here, the quality degraded towards the end of the file - my solution was to 'hardwire' my desired bitrate as you see here: http://www.zoneminder.com/forums/viewtopic.php?t=15202 if ...

another possibility would be a script that gets run as a cronjob every so often, and looks in the /events folder to get the latest folders to copy them on to the remote location via SCP etc with wildcards you could only back up the jpg that have set off the motion detection to save space/bandwidth ...

sorry i use ubuntu, the shared memory thingy seems different

you key looks weird though - usually it's something like 7A6D0001 etc, but BSD is a bit different

search the forums, i thought i'd seen a BSD guide somehwere here

i had a similar thought but you gotta re-write main parts of ZM problem is: the JPG from the cams need to be de-compressed for analysis - to detect motion or detect a dark/nonworking cam then ZM outlines the motion of the pic - and thus referres to past pics to reference the change in the pic then ...

" ... There are no other entries for nglayout ... " that's exactly why i suggested you create that entry: in the about:config page you make a right click new -> integer -> preference name : nglayout.initialpaint.delay value : 155 that's the # i use, and it works for me, but depending on your PC ...

" ...I looked for the 'nglayout. initialpaint. delay ' setting in about:config, but it is not there ..." try creating it, can't remember IF i had to or not i'm useing FF37a6pre from 06-25 (nightly) and everything seems fine also playing with the framerates/bitrates helps, of course depending on your ...

i'd install webmin, since it has nice easy tools to check/reconfigure mysql, and reinstall mysql

post a few more infos about which distro etc you're useing!

search for other posts with shared memory problems - this is very common since NO linux distro seems to have memory limits high enough for all the buffers that ZM uses check your use with: ipcs -l and see how much memory each camera uses and which key: ipcs -m post your results and someone will help ...

i believe that (with ip cams at least) the pic is captured/requested by zmc, then decompressed, then analyzed by zma, then timestamped and compressed, then saved you would have to look into the pipeline to read it from some buffer at the right moment easier would be no timestamps on the pic but ...