#Chameleon Nebula, Bernes 142
125 messages · Page 1 of 1 (latest)
You still gonna try?
I still had some mild colour gradients which i managed to fix myself
In post
idek how to
I might try, don’t except anything good 
like i can process it but its gonna be worse than yours and then it wont be worth it
Nah it’ll be fine
Cmon
I just process for the experience man
likr where do u even put the dbe points???
Not comeptiting or anything
^
too few and theres colour, too many and there no dust
or do u use a lot for RGB, few for L?
I’ll send a lil friend of mine
This is a wider dataset shot by LMC, it works well for MSGR
god has answered my prayers
🤑
This was tough, and this is as good as I've been able to get it, after several attempts. 😅
I didn't do the MSGR stuff, I couldn't get it to work with my limited skillbase. 😅
For the fun of the experience, I’m gonna just DBE it
I also couldn't get any good result with DBE. I had to rely on pixinsight's gradientcorrection tool
hated my edit but loved the data
Damn, are you guys struggling?
In my defense, I don't live where I can image these sort of structures and have little experience in dealing with this type of data. 🥺🥹
How do you even use that as a reference, is what I'd like to know.
For MSGR?
https://www.nightphotons.com/guides/multiscale-gradient-removal/ this guide explains Msgr well
is this even possible at siriL?
yes i'm siriL fr
This is quite old, the processes referenced have different settings that don't match up.
did u use standard MSGR or MGC?
i spend a while yesterday trying to get MGC to work
but the scales are incompatable apparently
so ill just process it with normal MSGR td
I'd be interested in knowing how you get the star alignment to work >.>
dynamic crop to align them roughly (widefield has to completely cover narrow)
then staralignment to align exactly
I think that's where I went wrong. My crop likely didn't cover the entire area. 😅 I might try again later.
I’m working on trying to figure that out and gonna write a guide
It’s possible
the only problem is having only one image open at a time
I keep getting this error.
MGC -> Instant Source Code -> "P.enforceFieldLimits = false;"
although apparently this voids ur warranty, but since this is software idk what that even affects
probably nothing
lol. that didn't work either.
also wtf did u do to the msgc??
why is the reference image overcorrected
u realise by using mgc u dont need to use much DBE at all?
@rare juniper bro it doesnt even look any better
that's an autostretch
nah looks like some awful dbe to me
i'll start from scratch again with that, see if something else goes wrong. i appreciate your patience and help 😛
for the widefield just do a really really smooth dbe
YAY!
yeah thats a big problem
this is what mine looked like
make sure u put any dbe points on background only
not even on the faint dust
did u press the tick after changing the value to true?
yeah, it saved.
show me what the error say
this also shows the tail end of the flux calibration

both are plate solved, and i cannot understand why it concludes the target image isn't in the wider image
whys msgc ur target image?
it should be ur reference
msgc is the reference, i think the msgc error is just called msgc. i'll rename the reference to be sure
ru sure u didnt just drag the MGC process onto the "msgc" image by accident?
no i was dragging it to QQQ's image.
hmm then it wouldve said processing view: image06
do it again, make sure ur dragging it onto image06
that was the original error. the second one i think i hit the square instead of dragging 😅
ok now it worked, but i need to do a proper dbe, as you said.
i didn't have the image cropped or rotated this time, and ran bx in correct only on both first.
LMC's shi is so good
yeah the square just applies onto the selected image, which is harder to tell
yeah, use maximum smoothness and select on the darkest points possible
not necessary to run bxt for MGC
could mess with flux measurements if u run it first
this is what i have for the reference rn
Ok, now this is better for sure 😛
That’s pretty good, getting close to what my process looked like
lets be honest LMC's data is kinda carrying yours
Nah you don’t understand h bruh
i wanna see a good process without that MSGR
🏓 Pong!
Latency: 480ms
🏓 Pong!
Latency: 346ms
🏓 Pong!
Latency: 477ms
🏓 Pong!
Latency: 264ms
Plus it ain’t my fault that i live in like the worse skies ever
🏓 Pong!
Latency: 206ms
Ill cook, no MSGR reference
Prove em wrong
Yeah dont use graspers ever lol
In the middle of processing this, but gotta say your process is really impressive, those gradients in RGB are crazy
Yeah, they’re certainly pretty complex… tried just DBE for the challenge, did like 35 different DBE’s
I haven’t had time to sit down and do an MSGR one yet
Gave it a shot, although i have to pack up my rig so i stopped abit earlier than i wanted too. Messed up DBE a small bit in the bottom right, but overall i can defo see a good process (yours is amazing already) coming, just gotta reprocess it with more time and be more careful with certain things
Very nice
