Jump to content

Seestar S50 images


M40

Recommended Posts

I have had a Seestar since April but this week has been my first chance to use it under darker skies.  I am on holiday in Norfolk where it is Bortle 4 compared to my Bortle 8 East London home. ik have used the darker skies to image objects low in Sagittarius impossible from home.  Total integration for these images varies from 10-20 minutes.

M8 - Lagoon Nebula

 

 image.thumb.jpeg.d92d4ed9f9a6fe96fe54ef1ffae0e366.jpeg

M20 - Triffid Nebula and M21

image.thumb.jpeg.0ec1e02b9fd582cbf5a3cb30de3a5e90.jpeg

M22

image.thumb.jpeg.414c9fb9eff854fe7b07ae7240126249.jpeg

M24 Sagittarius Star Cloud

image.thumb.jpeg.8059c74c72e05bcc76d8f52a8712739e.jpeg

  • Like 13
Link to comment
Share on other sites

I reprocessed my M16 Eagle Nebula, with 11.5h of integration, and tested some detailing workflows on the Pillars of Creation. First is the original image and the second is the comparison to the famous Hubble picture, not for actual quality but to see how many features the Seestar actually captured. Stacked and processed in Pixinsight.

 

Image280d.png

cscscsc.png

  • Like 14
Link to comment
Share on other sites

14 hours ago, Recretos said:

I reprocessed my M16 Eagle Nebula, with 11.5h of integration, and tested some detailing workflows on the Pillars of Creation. First is the original image and the second is the comparison to the famous Hubble picture, not for actual quality but to see how many features the Seestar actually captured. Stacked and processed in Pixinsight.

That's amazing, how much work did that take in Pixinsight?

 This is my version after 10 minutes exposure and no further processing. I guess that extra 11 hours does help :)

image.jpeg.405b699cba10345c6e7739f6cba04d3f.jpeg

  • Like 4
Link to comment
Share on other sites

17 hours ago, Recretos said:

I reprocessed my M16 Eagle Nebula, with 11.5h of integration, and tested some detailing workflows on the Pillars of Creation. First is the original image and the second is the comparison to the famous Hubble picture, not for actual quality but to see how many features the Seestar actually captured. Stacked and processed in Pixinsight.

 

Image280d.png

cscscsc.png

This picture is making me reconsider my life choices 😆 Love it!

  • Like 2
Link to comment
Share on other sites

7 hours ago, John_D said:

That's amazing, how much work did that take in Pixinsight?

 This is my version after 10 minutes exposure and no further processing. I guess that extra 11 hours does help :)

image.jpeg.405b699cba10345c6e7739f6cba04d3f.jpeg

Actual processing from start to finish took around 15-20min max. 

And yes, M16 is a rather high SNR target, almost like the M42, so having several hours of data makes a big difference. :) 

  • Like 1
Link to comment
Share on other sites

It never occurred to me that I would be able to capture the Veil Nebula or any part of it from my garden, I don't really know why but it just seemed a bit to exotic! For some reason I opened Stellarium on my PC the other night

and on a whim searched for the Veil for it's position that evening, to my surprise it was visible to the East for a relatively short period before it would be obscured by surrounding trees. With the night skies being what they are at the moment

I didn't really want to set up my main rig as from it's optimal position for PA the Veil might be obscured very quickly by the trees so I thought I'd have a go with the Seestar this evening. The image below is just the jpg directly from the Seestar with literally 10 minutes in Microsoft Photos and DXo Photolab, I'll do some "proper" work on it tomorrow.

Eastern Veil_DxO.jpg

  • Like 9
Link to comment
Share on other sites

I've had a play around with stretching, mostly in Siril but also DXo PhotoLab and MS Photos. I tried Affinity Photo which is supposed to be like Photoshop but couldn't get much out of it.

29 minutes of total integration time.

Eastern Veil_DxOMSPhotos.jpg

Edited by LaurenceT
  • Like 5
Link to comment
Share on other sites

 

17 hours ago, LaurenceT said:

It never occurred to me that I would be able to capture the Veil Nebula or any part of it from my garden, I don't really know why but it just seemed a bit to exotic! For some reason I opened Stellarium on my PC the other night

A couple of nights ago I did the same, on the offchance that I could image something. This is the result for 27 minutes, without any post-processing, as downloaded from my tablet.

1722552407757(NGC6992EVeilNeb).thumb.jpg.3d345a8f795480be294e6469302b5c90.jpg

Geoff

  • Like 5
Link to comment
Share on other sites

The Pacman nebula, with 3h of integration from Bortle 3 last night. Stacked (no Drizzle) and processed in Pixinsight in a HOO Hubble palette.

 

Pacman_3h_B3.png

Edited by Recretos
  • Like 8
Link to comment
Share on other sites

3 hours ago, Recretos said:

Yes, the nights are getting longer so its quite easy. 

A pleasure looking at your images and what you achieve with the seestar 👌

  • Like 1
Link to comment
Share on other sites

M51 - 920 x 10s over three nights between February and May. Stacked in Siril then followed Cuiv's tutorial on youtube using Graxpert, Siril and Gimp. Still new to processing so would be grateful for any tips, comments, etc.

Thanks

 

result_GraXpert_Siril_Gimp.jpg

  • Like 5
Link to comment
Share on other sites

20 minutes ago, Soupir94 said:

tips

Looks okay, the main issue is it's a bit out of focus by the looks of it, maybe the routine didn't nail it. Apo refractor optics give very sharply defined views, and the SS is apo.

Link to comment
Share on other sites

I might restack the subs for each night seperately and see what each is like. Perhaps that might indentify out of focus subs. Then run through the routine again. My eyesight is not the best 🙂

Thanks Elp

Link to comment
Share on other sites

Pelican Nebula (well, part of it), last night. 212 subs.

I tried processing this in Siril and Affinity Photo and the results were horrible so I simply stacked in ASIStudio and did a bit of further processing on the jpg in DxO Photolab and MSPhotos. Much much quicker.

Light_Stack_37_DxO-DeNoiseAI-standard-SharpenAI-StandardFinal_DxO.jpg

Edited by LaurenceT
  • Like 4
Link to comment
Share on other sites

On 05/08/2024 at 18:32, LaurenceT said:

So how do you cope with field rotation?

The most important is a good-quality stacking process, which Pixinsight does provide. Then, it helps to have a good reference frame selection to mitigate some of the field rotation in both directions. What's left can be slightly mitigated by processing and, in the end, with a crop. Even full-frame targets usually don't need much crop, depending on their location, of course. 

Below is my Crescent Nebula example. The first image is full-frame/uncropped, and the second image is the stacking pattern from Pixinsight, with obvious field rotation as I was recording over different parts of the sky over two sessions.

Image272.png

stack.png

Edited by Recretos
  • Like 5
  • Thanks 1
Link to comment
Share on other sites

2h of Helix nebula, captured at a low angle (15-20°), so with a lot of disturbance and dropped frames. One image is normal integration and one image is 2x Drizzle. Also added is a crop onto the main central star.

The 2xDrizzle file shows a fainter "eyebrow", due to the SNR reduction of the Drizzle process.

Integration.jpg

Drizzle_x2.jpg

Crop.jpg

  • Like 11
Link to comment
Share on other sites

For all the Pixinsight & Seestar users: I did a test of Pixel Rejection to remove satellite trails and even hot pixels in stacking. Basically, what this does is it rejects the satellite trails at the pixel level during stacking, removing only the satellite trail but keeping the rest of the frame in the stack. This means that you don't need to remove/delete your whole subs with satellite frames, but thanks to pixel rejection, you get to keep all the frames and reject the pixels of the satellite trail. As the satellite trails usually only appear individually on certain subs, removing them causes no visible artifacts or "dents," as the data from other frames covers that up.

Below is an example I created when testing 4h of M33 data. All images are raw stacks, unprocessed, with a preview stretch only.

The left image is the original stack without pixel rejection. The middle image is the pixel rejection result, showing what has been removed during stacking with Pixel Rejection activated. You can see it removed satellite trails that were not even visible, like over the core, and it did not remove any real galaxy signal, keeping the galaxy data intact. It also removed some patches that look like hot pixels. The right image is the final stack run with pixel rejection, looking much cleaner.

If you own Pixinsight, this is just one more reason to stack with it. You can stack and keep all your frames with satellite trails and remove them at the pixel level, keeping the rest of the data in the frame. Pixel rejection did not increase the stacking time meaningfully or at all, tested on 1500 subs.

 

TEST_PR.png

Edited by Recretos
  • Like 3
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. By using this site, you agree to our Terms of Use.