Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

What is the "fps" overlay? #297

Closed
jeff-h opened this issue Aug 31, 2016 · 4 comments

Comments

Projects
None yet
3 participants
@jeff-h
Copy link
Collaborator

commented Aug 31, 2016

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

This comment has been minimized.

Copy link
Owner

commented Aug 31, 2016

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

This comment has been minimized.

Copy link
Collaborator Author

commented Sep 1, 2016

Wow, awesome. Thanks for the explanation!

@jeff-h jeff-h closed this Sep 1, 2016

@enieuwenhuis

This comment has been minimized.

Copy link

commented Nov 19, 2016

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...)
schermafdruk van 2016-11-19 11 47 56

@ccrisan

This comment has been minimized.

Copy link
Owner

commented Nov 19, 2016

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.