RTP/RTSP won't detect motion / record?

[diluted]

I was using RTP/Unicast but was getting dropped frames on my wifi cameras so I switched to RTP/RTSP and now the video is perfect but my zones don't detect motion & record. I'm hoping someone can help shed some light.

Source Type: Ffmpeg
Function: Modect
Enabled: Check
Max FPS: 20

Source Path: rtsp://admin:admin@192.168.1.23:554/cam/realmonitor?channel=1&subtype=0
Remote Method RTP/RTSP

[knight-of-ni]

You either need to leave both the MAX FPS and Alarm MAX FPS field empty, or make sure the values you use are never less than the actual fps value of the incoming stream. Otherwise you get exactly the symptoms you just described.

[pcglue]

You either need to leave both the MAX FPS and Alarm MAX FPS field empty, or make sure the values you use are never less than the actual fps value of the incoming stream. Otherwise you get exactly the symptoms you just described.

I came across this while trying to setup a "mocord" monitor on a RTSP stream that records at 1 fps but at 20 fps during an alarm. I guess this isn't possible to do when using RTSP? Is it something specific with RTSP that precludes doing this?

[knight-of-ni]

Those fields were never intended to work with IP camera streams.
They will only work with local devices, and retrieving images via snapshot mode.

I have an open pull request which adds a warning to the end user:
https://github.com/ZoneMinder/ZoneMinder/pull/1033

For ip camera streams, the only useful function for those fields is to keep the cpu from running away in the event the camera falls off the network. In that case, placing a fps value higher than the incoming streams will prevent that.

There are many, many posts in this forum that alert the end user about these fields.