ZoneMinder Forums

OK - so the error I get when using 'remote' is caused by I frame - I set the interval to 10 and the FPS to 10 and the error occurs every 100 frames now. I thought that I frame interval was in frames - obviously it's seconds.

I did try setting it up using the native rtsp 'remote', and I could indeed get it to work - however the logs were filling up pretty quickly (every 30th frame - odd): 2015-05-08 16:06:03.398631 zmc_m4 15226 ERR Error while decoding frame 421 zm_remote_camera_rtsp.cpp 302 2015-05-08 16:06:00.414303 zm...

..oh well, I suppose it makes a change! 2015-05-08 15:17:01.586927 zmf 6195 INF Frame server socket open, awaiting images zmf.cpp 86 2015-05-08 15:17:01.375753 zmf 6195 WAR Socket closed at remote end zmf.cpp 274 2015-05-08 15:17:01.371984 zmf 6195 ERR Only read 219224 bytes of 222498 zmf.cpp 267 20...

Season 1 episode 9. Due to the high load on the server caused by libvlc I resolved to get ffmpeg working (it simply didn't). Given that *buntu 14 uses libav I thought I'd look into that. Checked OPT_FFMPEG and set PATH_FFMPEG to /usr/bin/avconv. Set remote method to RTP/RTSP because I heard that enf...

Just out of curiosity, where does that 'sent time' come from? is it using the server time, or is it getting it from the camera somehow?

I wonder too......

Release 1.28.1 February 14th, 2015 ->Minor release focusing on RTSP improvements.<-

Still can't get it to stay connected. The issue for me is that I can connect via RTSP with VLC and I don't lose the stream. I can connect with a browser, with Xeoma.... and I don't lose the stream. last frame sent time 1430120263.528179 secs - to me, that sounds like an arithmetic over/underflow. I ...

I have two similar cameras, one is an Escam QD500, the other is a no-name but it's running the same/similar software. My setup is almost identical to the one shown in the link, with the exception that I have not specified FPS. ffmpeg does not work well. I get smeared images. Ubuntu 14.04 uses libav ...

Damn

2015-05-04 16:12:46.559886 zms 25803 ERR Terminating, last frame sent time 1430752366.059794 secs more than maximum of 10.000000 zm_monitor.cpp 4155

OK, I set my two monitors up such that the FPS was left blank. One camera I left the settings alone - capturing at 15 FPS with keyframe interval at the default 3 The other I dropped to 3 FPS and set the keyframe interval to 10. Just before I crashed last night I checked the monitors and bingo - stil...

OK, I'm going to give this a go (although I have tried many FPS/key frame combos to no avail), I'll report back.

I must admit it bugs me that I can't get this to work, but I simply don't have the time. Switched to Xeoma, it's rock solid with all my cameras. Cost 50 quid, but cheaper than replacing cameras and/or messing about for hours on end trawling through logs trying to make some sense out of them. It's a ...

Well I've tried this on two machines now with three different cameras (including a d-link one that works fine as MJPEG/HTTP) and I simply cant get a reliable RTSP connection.

I can't believe I'm the only person having this problem!

The camera I have that drops out is also MJPEG over HTTP. I can't get RTSP to work reliably, when signal is lost it stays lost.

You can set up the filter on a per monitor basis.

I set up a filter - cause equal to signal, run in background, delete all matches.

Might not be the most elegant solution but it works