What I see in the "stargazing" mode of the Seestar is this: It does 10 seconds exposures, then it does ...something... for the next 5 seconds and then it continues with the next 10 second exposure, giving you only a 66% duty cycle of exposure. 5 seconds is way more than what is needed for the readout of the CMOS sensor, and most/all of the image enhancing & plate solving & tracking computations should be able to go on while the electronic "shutter" of the sensor is "open" and the sensor is exposing ... if all those computations take longer than 10 seconds then maybe the exposure could be a bit longer than 10 seconds perhaps. It also doesn't seem like the scope is moving only discretely in those 5 second intervals between exposures but continuously (judging by the sound it makes).
So I wonder whether it might be possible in future versions to improve on the dead-time between exposures?? Is ca 5 seconds for every 10 seconds of exposure really necessary?
Thanks in advance
HBE