StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>In order to make it accurate, there are two possibilities: </p> <p>Using framerate from the streaming server. In this case, the client needs to keep the same framerate (calculate each time when you get frame, then show and sleep for a variable amount of time using feedback: if the calculated framerate is higher than on server -> sleep more; if lower -> sleep less; then, the framerate on the client side will drift around the original value from server). It can be received from server during the initialization of streaming connection (when you get picture size and other parameters) or it can be configured.</p> <p>The most accurate approach, actually, is using of timestamps from server per each frame (which is either taken from file by demuxer or generated in image sensor driver in case of camera device). If MJPEG is packeted into RTP stream, these timestamps are already in RTP header. So, client's task is trivial: show picture using time calculating from time offset, current timestamp and time base.</p> <p><strong>Update</strong> For the first solution:</p> <pre><code>time_to_sleep = time_to_sleep_base = 1/framerate; number_of_frames = 0; time = current_time(); while (1) { get_image(); show_image(); sleep (time_to_sleep); /* update time to sleep */ number_of_frames++; cur_time = current_time(); cur_framerate = number_of_frames/(cur_time - time); if (cur_framerate > framerate) time_to_sleep += alpha*time_to_sleep; else time_to_sleep -= alpha*time_to_sleep; time = cur_time; } </code></pre> <p>, where alpha is a constant parameter of reactivity of the feedback (0.1..0.5) to play with. </p> <p>However, it's better to organize queue for input images to make the process of showing smoother. The size of queue can be parametrized and could be somewhere around 1 sec time of showing, i.e. numerically equal to framerate.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload