Thank you for always doing a wonderful job.
Currently, the Ekos guide module is imaged with a still image loop, but using a slow machine such as RaspberryPi 3 makes the delay very large.
Currently, most drivers support stream video (live video of capture module), so please change it so that it can be used with the guide module.
In the case of a stream image (live video), the image changes quickly and the guide becomes accurate.
(It will be very useful if the INDI driver on PHD 2 is handled in the same way.)
The guide INDI driver for PHD 2 is also slow as well. .
By setting LiveVideo Stream video to the driver default, the number of cameras that can be used increases dramatically.
well, the stream won't be much faster really. Currently, it's streaming is done via raw binary while regular capture is FITS and there isn't a huge difference in size.
Even though we mentioned earlier in solver processing, on a single computer like RaspberryPi 3, processing seems to be slow when processing FIT.
In stream video, it operates on average about 7 frames and it runs very fast.
In the FIT file loop used in the guide module, updating takes about 2 seconds.
Perhaps even in PHD 2, the driver may seem to hand over the FIT and perform loop processing, but the update is delayed and the guide can not be created. Stream video has speed comparable to native driver.
The native driver of PHD 2 and Linguider also deals with video streams.