Major INDI Library release v1.9.0 bring significant internal changes championed by @pawel-soja to modernize core INDI Library drivers and clients. New drivers for DeepSkyDad Flat Panel & Pegasus devices plus further improvements to PCM8 drivers.
I notice a lot of Stellarmate users are connecting via VNC rather than the native Indi client - server option. With Kstars /EKOS available on all major platforms I can see no reason for using VNC.
Anyone care to explain / enlighten on their preference for VNC?
I would love to use something more native to the environment (I'd be faster and smoother I would assume).
I use it because it has the whole package, from any device at the same time (running on my PC, Tablet and Phone). Meaning, I can see the KStars planetarium app running and the whole EKOS interface as if I had a key board/monitor plugged right into the SM.
I've 'sorta' tried the INDI client never really got it running. It looks like simpler version without the GUI interface or the planetarium interface.
Maybe I need to commit to it and give it some time. Oh the noVNC needs to time to learn .
I always use VNC because then KStarts and EKOS run on the mini-pc that I use to control all my imaging hardware. That way I can safely shut down my MacBook ans there is no need for it to run all night. Also, in case of a WIFI/network glitch, KStars and EKOS keep running without being interrupted.
Wouter van Reeven
ASI6200MM and 7 slot 2" filter wheel with a SkyWatcher Esprit 80 ED on a SkyWatcher HEQ5-Pro
ASI1600MM-Pro Cooled and 5 slot 1.25" filter wheel with an 8" TS Ritchey-Chrétien on a SkyWatcher EQ6-R
At home, I run KStars client on my laptop and INDI Server App on the Pi. I also run PHD2 on the Pi. I use VNC once in awhile in case PHD2 is doing something I don't like, or if I need to shut down. The rest of the time, I am not looking at the desktop of the Pi.
If I were in the observing field, then I might run everything on the PI simply because I could turn off my laptop to save power once everything is set up and running. Also, you can run more than one session on different Pi's this way, all over VNC.
I run everything on PI and connect to it via VNC.
I think it is more reliable - no chance that network glitch or your client deciding to go to sleep or just crash to interrupt your session.
It used to be a challenge to run everything on Pi due to low memory, but with Pi 4 all is running very smoothly on 2GB version.
With VNC approach, I can start a session from a PC and then monitor it from phone or tablet.