I'm slightly confused about the difference between the “enhanced” image that is saved at the end of an observation plan (or a sequence of captures), and the one you can obtain by applying Deep Sky Stack afterward (I've read the tutorial, but I'm still unsure).I mean: even though Seestar says “Enhancing”... isn’t what it’s actually doing during stargazing real-time stacking, or am I wrong?Sure, in Deep Sky Stack I can choose which frames to include, but are the ones made available to me actually the same ones that were used for the enhanced image?Can someone help me understand?Attached: the image with 107 minutes is the result of "Deep Sky Stack" having not used a few subframes that in my opinion were bad enough. The image with 119 minutes is what was left after the complete plan execution, let's say the "default" enhanced image. Both have been cropped, AI denoised and saturated, all in Seestar App, no external processing. To my eyes, surprisingly enough, the Deep Sky Stack is much worse...

请问尼康D5100满阱电荷多少？QE多少？去拜尔滤镜后QE又为多少？

As far as I know, three out of the four predicted eruption dates have already passed without an outburst. Does that mean the eruption could still be months or even years away?

What can i do, i wanna leave my telescope overnight but im scared itll rain its a seestar s30 pro and im in Puerto Rico

我第一次用望远镜，第一次发作品，参加了月相追踪者活动，拍了一个整个盈凸月，但没看到进度变化，也没有看到对应形态被点亮，自我推测可能是作品不符合要求或描述内容不够，但不知道错在哪。请问各位大佬参加月相追踪者发布作品时须注意什么啊！比如说必要信息及注意事项什么的。

Sorry for posting yet another suggestion, but since I am still in my first weeks with the Seestar, I keep noticing small features that might perhaps be useful to other users as well.I know that Seestar already has the planning/scheduling function, but I would like to suggest a very simple additional safety option: an automatic shutdown when the number of consecutively rejected frames exceeds a user-defined threshold.For example, this could happen when the frames are rejected because they are overexposed, meaning that astronomical darkness is over, or because not enough stars are detected, meaning that the target has gone behind an obstacle such as a tree, a building, a balcony, etc.In my specific case, I had started an imaging session on M17 and I had not checked carefully enough in advance when the target would become too low. So I left the Seestar running overnight, and in the morning, at about 6:00, it was still “imaging”, but of course it was only capturing completely white frames.I hope this did not damage the sensor, but I would have found it very useful if the device had been able to shut itself down automatically, so to speak as a form of self-protection.The option could be something very simple, for example:“Shut down Seestar after N consecutive rejected frames”with N chosen by the user, or perhaps with a reasonable default value.This would not replace proper planning, of course, but it could be a useful safeguard for unattended overnight sessions.If you like the suggestion, please like or support it!Best regards,Claudio