knro wrote: Maybe another idea is to release the raw data buffer completely after the initial stretch is done. So no more operations on the raw buffer because it's gone. That would cut utilization by half. Any thoughts on this?
I like this idea the most!
I need FITS Viewer while I do my manual operations and keep track of things while I image (not full automated yet). I also wouldn't like a conversion from RAW to JPEG, as that would slow down download times even more: I just posted a wishlist where I say that I would love if download times wouldn't be affected by dithering or HFR calculations. JPEG conversion would probably add to the time for the image to be displayed and increase the timer before the next exposure is started even more.
But, yes, I would love some RAM optimization. I have a Raspberry Pi 4 4GB and with everything running (KStars, EKOS, PHD2 and FITS Viewer) I am at about 50% RAM consumption. Sometimes PHD2 even hangs and does not issue any command for multiple cycles of guide camera exposures (might be 10-20s, even)...