ZoneMinder Forums

As I mentioned in another post, I'm using ffmpeg to capture images and detect motion from Ubiquiti AirCams. Some of my cameras are working perfectly, but others are giving me false motion detection with images that look like the one attached.

The only smoking gun I can find is messages like the following in the logs: I have tried increasing the ring buffer size and tweaked the fps to no avail. I don't believe it is a shared memory issue as the max seg size is already up to 2GB and I'm not seeing any shmget errors in the logs. It's possible that it's just ffmpeg mis-intrepreting the stream, but I don't really have a way to tell.

Does anyone have any tips on how to track this down and fix it? At the moment, ZM is fairly useless to me for motion detection because of this problem and the corrupted images.

Thanks!

I had something like this once and it was duplicate processes. I had to stop ZM and then look for the remaining process and kill them. Worked ok after that.

I think I found the solution. If you're using an ffmpeg stream you have to leave the FPS boxes empty in the camera General tab. I changed that last night on all of my Ubiquti cameras and haven't had a single glitched frame yet.

Unfortunately I can't say the same thing for my TrendNET TV-I262PI, now I have to figure out the magic settings to get it working reliably. I had it working with snapshots, but the frame rate was horrible. I found the magic URL to get mpeg4 from it but it is occasionally glitchy.

if your camera permits, can you reduce the FPS from its interface?

tkalfaoglu wrote:if your camera permits, can you reduce the FPS from its interface?

Yep, I'm also going to play with the resolution to see if that will make a difference. It's a shame to have a 1MP camera if I can only use 640x480 @10FPS (for example) though.

If that's any relief, I didn't have to reduce the resolution on my FI9805; just the frame rate.. It seems to behave well at 5FPS at 1280x720
-t