Motion latency on first movement

Depending on the camera setup, there can be noticeable latency (about 1.5 seconds) when first attempting to move the camera, either via a left/right/up/down or by going to a preset.

The problem occurs the first time an HTTP request is made when the HttpClientHandler has its UseProxy property set to true (the default)

https://github.com/victor-david/camera-eye/blob/ca99d81edbf13b42c7643b212ca9c9f73b09db2a/src/Restless.Plugin.Framework/Base/HttpPluginBase.cs#L38

If the UseProxy property is set to false, the latency does not occur.

var clientHandler = new HttpClientHandler()
            {
                UseProxy = false
            };

Some cameras (Foscam) make an HTTP request during initialization to obtain values from the camera. Therefore, the latency is "hidden" in startup. Other cameras (Amcrest) do not obtain values from the camera during initialization.

If only Amcrest cameras are mounted on the camera wall, the latency occurs for the first camera to be moved. After that, the underlying .NET doesn't attempt the proxy lookup again and the second camera suffers no latency.

Same if an Amcrest and a Foscam are mounted. The Foscam performs its HTTP request during initialization ("hiding" the latency in startup) and the Amcrest suffers no latency.

Not sure this can be called a "bug" exactly and it may be something particular to my machine. But it is annoying. To fix, I propose to add a camera flag that conditionally sets the UseProxy property according to the flag. This would be an "advanced" config item and involves modifying the camera management window.

victor-david / camera-eye

Motion latency on first movement #12