In my case, I would like to add a Siril-edited version to an image that was created only with the Seestar-App.

从2024年的5月份用S50拍出第1张深空摄影的照片，到目前已有两年有余，这两年期间从只会用S50拍图片，到学会后期，学会传统设备一路走来成长了很多，也把童年的理论运用到了实践，真正探索属于我自己的星辰大海，也从原来不明白拍戏的规律，以为什么时候都能拍到后面，只知道什么时候拍戏效果最好，而规律性出摊。

I already have a device in a remote observatory in the same timezone as the one where I live, but considering a second one elsewhere with a substantial time difference. I have a hard time figuring out whether this will work natively, or whether I need to have 2 accounts / 2 terminals for this to work. Has anyone tried this ?

@jinouss you could try this out since you are good at Siril processing,@DILCHSKY ,@StuartTheAlien👽🖖 in case you didn't already try this target with your telescopes The reason? Simply because using a external battery will give the Seestar enough energy to shoot for the whole night instead of only 3-4 hours. After gathering as much light as possible, stack separately each of the panels in Siril or the app, and no matter what your astrophotography skill level is, do your best to process them with any astro software like Siril, PixInsight, GraXpert, Cosmic Clarity, Astroforge etc. After that, assemble your 6 panels with Microsoft ICE, PixInsight, Google Photos if you don't care about anything, or any other software you like.

哪位大佬能教我后期剪辑，搞不懂延时摄影。 Who can teach me post-production editing? I don’t understand time-lapse photography.

When "Save Each Image" is enabled, the Seestar currently saves both the FITS file and a JPEG version (plus its thumbnail) for every frame.For users who perform their own post-processing, the FITS files are usually the only files that matter. In my case, I routinely delete all the JPEGs immediately after copying the data to my computer.It could be useful to add a small option next to "Save Each Image" allowing users to choose what to save:☐ FITS + JPEG (current behavior)☐ FITS onlyThis would reduce storage usage on both the device and the mobile device, especially during long imaging sessions where hundreds or thousands of frames are collected.The current behavior would remain the default, while advanced users who only need the scientific data could save considerable storage space.

I have a question about theLevel Sensor Calibration function in the Seestar S50 app.When using EQ Mode, the app shows the current latitude as 44°— which is correct for my location near Bologna, Italy — but the actual tilt angle shown by the app is about 46°, with a polar alignment deviation of about 0.3° downward.If I understand this correctly, this would imply an effective angle of about 45.7°, which is still noticeably different from the local latitude of 44°. I am not sure whether I am interpreting this display correctly, but it looks a little inconsistent to me.For this reason, I am wondering whether it would make sense to perform the Level Sensor Calibration shown in the app tutorial, placing the Seestar on a truly level surface and recalibrating its internal leveling sensors.However, I have also heard from some dealers and experienced users that this calibration should generally be avoided unless really necessary, because it overwrites the existing factory calibration values.So my question is:Is Level Sensor Calibration a safe and legitimate operation to perform when the EQ Mode angle/latitude indication seems inconsistent, or is it better to leave it untouched unless there is a clear and serious problem?I am not trying to “improve” the factory calibration unnecessarily. I just would like to understand whether this discrepancy could indicate that the level sensor calibration is off, and whether recalibrating it is considered a normal maintenance operation or something that should be avoided.Any experience or clarification would be very welcome.

🤷‍♂️A bunch of us get together and share our subs to compile into one massive image.