Motioneye: What is the "fps" overlay?

[jeff-h]

I'm hoping someone can help me understand what the fps overlay is for e.g. I see something like "5.8/3.0 fps" overlaid over my camera images.

[ccrisan]

If you hover it with the mouse you'll see a tooltip saying "streaming/capture frame rate". Streaming refers to the actual rate as seen by the UI (the javascript page) and capture refers to the rate with which motionEye captures frames from the motion daemon. On a fast enough system, the capture framerate should be very close to the framerate configured in motion.

[jeff-h]

Wow, awesome. Thanks for the explanation!

[enieuwenhuis]

Hi, in my case there is a gap between streaming and capture.
Question: is this a problem and what is a solution (Other than buying a faster system...)

[ccrisan]

You have two framerate settings in the settings panel: the first one (under the Video Device section) controls the _capturing_ framerate. The second one (under the Video Streaming section) controls the _streaming_ framerate.

Now they both are just "hints" for the underlying mechanism. That is, the actual capture framerate will depend on the performance of the device as well as on the available bandwidth when communicating with the camera.

The actual streaming framerate will also depend on the network bandwidth between the motionEye server and your browser, at least.

Having a higher streaming framerate than the capture one doesn't make too much sense, as many displayed frames will be duplicates of the previous ones. However this is not a bug and definitely not something to worry about. It often happens with network cameras when the netcam simply can't provide as many frames per second as requested.

I hope this makes sense and answers your question.

[tobiaslohr]

You have two framerate settings in the settings panel: the first one (under the Video Device section) controls the _capturing_ framerate. The second one (under the Video Streaming section) controls the _streaming_ framerate.

Now they both are just "hints" for the underlying mechanism. That is, the actual capture framerate will depend on the performance of the device as well as on the available bandwidth when communicating with the camera.

The actual streaming framerate will also depend on the network bandwidth between the motionEye server and your browser, at least.

Having a higher streaming framerate than the capture one doesn't make too much sense, as many displayed frames will be duplicates of the previous ones. However this is not a bug and definitely not something to worry about. It often happens with network cameras when the netcam simply can't provide as many frames per second as requested.

I hope this makes sense and answers your question.

@ccrisan Thanks for the explanation. Quick follow up question on this: the settings under Motion Detection regarding frames, frame changes, number of frames before/after etc. they refer to the capturing frame rate configured under the Video Device section)?