Recently Browsing 0 members
No registered users viewing this page.
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!
Hi guys, it's my first post here, so Hello!
My synscan goto upgrade started to act like in this video of mine SynScan GOTO Skipping after being disassembled for few weeks in the closet. There were no such problems before.
When it slews at rates above x3 everything is fine and smooth but as soon as it starts tracking at x3, it skips steps or something like that.
My setup is eq3-2 on alu and SW 150/750 with Canon 700D attached.
Thanks in advance for any clues or ideas!
Ok, so this is a really annoying bug / problem that I have with my setup:
From time to time, in non regular intervals the image my guiding cam (ZWO ASI120) send seems to get flipped / mirrored or looks like it's from a completely different patch of sky.
When I'm paying attention to the guide images I can clearly see that the image seems to be flipped in some way.
It only happens for 1 frame PHD send a warning ( No star found / Star lost Mass changed) and after that everything is fine again. My gear is all connected to a single USB3 Hub which then runs via powered USB3 cable to my Pc.
I'm not binning and have the noise reduction off (though PHD might got hickups while processing) but it still happens. Sometimes there are minutes between two events sometimes it happens 5 times in a row.
It also seems like it's only happening during guiding, I haven't seen it happen during calibration yet...
I'm completely clueless what's happening or how to get rid of it, any help / idea is greatly appreciated.
Taken on Sunday evening with a 98% Moon.
Comprising of 12 x 600s subs using an ED80 with a 0.85x FF, an Atik 383L+ and a 7nm Optolong Filter.
Stacked in DSS, and processed in PS.
Full frame and cropped, mono and h-alpha colour using NC Actions.
Thanks for looking