Some personal observations - sorry but it was a Windows version of ASTAP running on my test rig - an older AMD A6 8GB Win 10 64bit with SSD. I used a DSLR and no Scope set up. Old stored images were used for he live stack. Nothing else out of the normal being used except MQTT broker on Windows!
1. Too complicated IMHO - by that I mean you just need to set the folder where the images are going to be stored and allow the user to end the session and change the stacking source does matter that the scope has slewed in the mean time as I would expect the Live stacking to "Lag" behind by a number of images anyway - ok more difficult when using automated sequence. Plus Astrotoaster allows a fair amount of simple changes,in real time, to the stack (well the viewers displayed image) just by using simple sliders on various parameters via a simple cild window called "Col Adj" - something like that would be great in ASTAP
2. On my test rig ,which runs DSS Live and Astroaster ok ,I was unable,once live stacking started, to do anything within ASTAP as it kept displaying the dreaded revolving circle and "no responding". Task Manager showed very high processor usage but no more than either DSS or Astrotoaster - figure shown was around 34% with only 2.7gb out of 7gb of memory used.
3. I could not find a way to just monitor RAW (CR2 files) as per DSS etc and let ASTAP do the conversion if required to FITS. I know ASTAP will convert RAW files to FITS for normal stacking,
4. Personally I would prefer the Live Stacking to be a separate application and NOT part of ASTAP - simple and clean which both DSS Live and Astrotoaster are ,even though they use DSS in the backgound - but I never need to start or see DSS !
5. The ability to reject some images in the Live Stacking list and restack would be nice.
As I say this is my EAA personal observations and know it will be used in other ways ,so it is a blinkered view
Plus what is the hardware testing set up beings used by others - RPI ? or other - obviously running ASTAP on new faster kit and maybe Linux OS would my problem as noted by point (2) but would be interested on what others are using during this test / development phase.