* Add framerate limit, print delay in debug dump.
* Add global variable and #define in config to set default.
* Add new parameter in /control handler and preferences.
* Add max fps control in full index page for ovh2640.
* Add max fps control for ov3660 index page.
* Update API documentation.
* Use better name for framerate limit variables.
* Change UI to show the same values of framerate control as used in command interface.
* Apply framerate limiting delay after serving content boundary.
Putting delay after finishing serving the frame causes image to appear
in stream with a lag. The reason for this appears to be that browser
relies on next frame content boundary in order to determine the end of
image.
That means that in order for browser to show frame right after receiving
it, server needs to send next frame content boundary right after image
itself, and delay to limit framerate should be applied after content
boundary, not before it.
According to https://www.w3.org/Protocols/rfc1341/7_2_Multipart.html
sending first frame without content boundary will likely cause its
content to be ignored, which seems to be acceptable price for not
treating first iteration of the loop as special case.
* Fix delay before first frame by sending first request boundary before
entering the loop.
Co-authored-by: 15498th <user@localhost>
Co-authored-by: Owen Carter <owen.carter@gmail.com>
* Slightly longer flash delay, #188
* Framebuffer delayed frames
* Fix Travis, again
* show XCLK in dump output
* comment on slow XCLK for slow clones
* pump up the wifi watchdog default
* latest IDE and esp core
Putting delay after finishing serving the frame causes image to appear
in stream with a lag. The reason for this appears to be that browser
relies on next frame content boundary in order to determine the end of
image.
That means that in order for browser to show frame right after receiving
it, server needs to send next frame content boundary right after image
itself, and delay to limit framerate should be applied after content
boundary, not before it.
According to https://www.w3.org/Protocols/rfc1341/7_2_Multipart.html
sending first frame without content boundary will likely cause its
content to be ignored, which seems to be acceptable price for not
treating first iteration of the loop as special case.
* Fix rotate -90 degree bu
Adding a style with flex-direction: column; and align-items: flex-start; does the job 😀
* replaced \n\r with \r\n
\n\r gives strange results in other than Arduino serial monitors.
