Stargazers Lounge Uses Cookies
Like most websites, SGL uses cookies in order to deliver a secure, personalised service, to provide social media functions and to analyse our traffic. Continued use of SGL indicates your acceptance of our cookie policy.
-
Recently Browsing 0 members
No registered users viewing this page.
-
Similar Content
-
By tooth_dr
I scrapped all the Oiii and Sii data I previously took during a full moon (about 15 hours worth) and retook it all when the moon was a bit smaller at 76%. Ha was taken during 98% and 67% moon. All the lights were taken on the following nights: 12th, 19th and 20th September 2019.
Integration times, all in 600s subs unbinned:
Ha = 28.33 hours
Oiii= = 5.67 hours
Sii = 5.67 hours
The Ha data is really nice, and unsurprisingly the Oiii and Sii is not as strong (or nice).
I'm missing that (vital) step in my processing routine of getting the Sii and Oiii properly stretched to match the Ha, before combining. I dont really know how to deal with the weaker data properly. Any pointers would be appreciated.
What I do currently:
All the data is loaded into APP into separate channels/sessions.
The data is stacked and registered against the best Ha sub
This produces individual stacks of Ha, Sii and Oiii that are all registered
Each channel is processed with DPP in APP and then saved as a 16bit TIFF
Each is opened in PS
Stars removed with AA and any remnants removed and tidied up
I then open a blank RGB document in PS
I paste Ha into Green, Sii into Red and Oiii into Blue
Adjust the selective colour settings to get 'Hubble palette'
Adjust levels, curves, saturation until looks ok
All the Ha Sii Oiii data is then combined together in a single 'super' stack in APP using quality weighted algorithm to create a 'luminance'
That luminance layer is adjusted using levels, curves, and NC tools such as local contrast enhancement and deep space noise reduction (using masks to apply as required)
The luminance is pasted onto the above colour layer, and incrementally added using gaussian blur
Cropped and saved.
Here it is anyway I haven't intended on any more exposure time for this one, but will consider it, if the expert opinion dictates otherwise!
CS
Adam
-
By LR Watanabe
Okay, I'll try to make this as short as possible.
Info: I have a EQ5 mount (soon to become motorised and GOTO'd) and, after reading countless astrophotographers praise the QHY PoleMaster, I thought it'd be a good idea to follow in their footsteps and buy myself a PoleMaster.
I saw nothing about the PoleMaster supporting the EQ5, so I thought I'd ask whether or not the PoleMaster would make my life easier by supporting the EQ5.
Clear skies,
Leon.
-
By Amajed
Hi, this is my first time using my new Esprit 100ED, my first time processing using Pixinsight, and it's my first image using a Mono + filters.
I loved them, can't wait to try on more targets.
here's the result:
Equipments:
SkyWatcher Esprit 100ED
SkyWatcher EQ6-R
SkyWatcher EvoGuide 50ED Guidescope
Imaging cam ZWO ASI1600MM Cool Pro
ZWO EFW
ZWO LRGB+NB 36mm filters
Guiding cam ZWO ASI290MM Mini
Seeing was avarage
Location was in a Green Zone
Exposures:
Ha 11x1800sec
L 39x300sec
R 13x300sec
G 15x300sec
B 15x300sec
Darks:
24x300sec
10x1800sec
Bias:
70
Thanks
-
By DMouse
Hi, here is last nights shot at M101. This is a luminance run only and was to test to see if the central Halo was still there, and it is, grrrr. I have a sneaky suspicion it is coming from the edge of the secondary mirror. I have pretty much painted everything else matt black, so far. Anyway, Here is the Luminance run.
Subs: 10x 300sec, 5x 420sec
Processed in Pixinsight. BIAS, DARKS and FLATS applied.
Cheers
Paul
-
By Yogesh
Hi
I am looking for the QHY Polemaster for doing polar alignment. If you have one and no longer need it please send me a message and I will get back.
Thanks and Regards
Yogesh
-