Hi and welcome to the ST forums!
To make a long story short; it's all good news! You are doing everything right. When launching Wipe (with Tracking on), it should have told you something to the effect of "...it is highly recommended to re-do your global stretch afterwards. This ensures the dynamic range that has been freed up can be put to good use."
The latter is exactly what is going on in your Wipe screenshot; the bias and gradients seem to have been successfully removed and you are now left with just the celestial signal we're interested in. Right now the dynamic range your monitor can display is not allocated very well to the signal we're left with; just a sliver of it is allocated to the signal (the rest used to be
allocated to the gradient/bias). Therefore a re-stretch (suing AutoDev or Develop) is appropriate, this time for just the signal in all its glory without the yucky bias/gradient. Setting "temporary autodev" to "yes" in the Wipe module will give you an idea of what to expect in AutoDev.
A full process of your data could look something like this;
--- Auto Develop
To see what we got. We can see heavy light pollution, vignetting, oversampling, guiding/stacking errors, (small) stacking artifacts, coma and noise.
To make guiding error less apparent and reduce noise. You could also run the Lens module prior to
Parameter [Scale] set to [(scale/noise reduction 25.00%)/(1600.00%)/(+4.00 bits)]
To get rid of stacking artefacts You could also run the Lens module prior to to Cropping to ameliorate the coma.
Parameter [X1] set to [4 pixels]
Parameter [Y1] set to [4 pixels]
Parameter [X2] set to [1178 pixels (-4)]
Parameter [Y2] set to [783 pixels (-4)]
Vignetting preset. The gradient is pretty severe and tapers off fast.
It is clear no flats are used (they are not optional!) and dust donuts/smudges on the CCD can be seen. Some minor banding is also visible (if becoming a problem, this could be corrected by dithering between frames, using bias frames, or using the Band module)
Parameter [Precision] set to [512 x 512 pixels] (needed if gradients taper off fast or undulate fast).
Parameter [Dark Anomaly Filter] set to [6 pixels] to catch the smaller dust specks (also needed if data is noisy) - bigger specks or donuts would need to be masked out.
Parameter [Corner Aggressiveness] set to [100 %]
Parameter [Aggressiveness] set to [82 %]
Parameter [Temporary AutroDev] set to [Yes], so we can see what an AutoDev result would roughly look like.
--- Auto Develop
RoI over M42 "wing".
Parameter [Ignore Fine Detail <] set to [4.8 pixels] to make AutoDev ignore the noise grain (otherwise it will start optimising the dynamic range allocation for this - what it thinks is - "detail").
Bring out some detail in the core.
Parameter [Radius] set to [2.2 pixels]
Default color balance looks good; you captured the core wonderfully (green O III emissions, mixed with blue of the trapezium stars) as well as the outer regions (mixture of blue reflection, dominant Ha and some Hb). Pay particular attention to the pink shockwave "serpentine" feature bordering the green core at 8 o'clock as it extends into the fainter nebula - great stuff. There is some cross-channel alignment trouble with the stars, causing color fringes, but in general a good "random" representation of all star colors/temperatures can be seen.
Parameter [Dark Saturation] set to [6.30] to introduce a bit more color in the darker regions.
Parameter [Bright Saturation] set to [3.90] to remove some color from the brighter regions (to counter the color fringing described above in the stars a little).
--- Wavelet De-Noise
Switching Tracking off.
Parameter [Color Detail Loss] set to [15 %]
Parameter [Brightness Detail Loss] set to [12 %]
Parameter [Grain Size] set to [9.2 pixels]
Parameter [Smoothness] set to [81 %]
And that's it!
All you need is more frames (it's never enough
), acquire some flat frames, dither between frames, check your guiding/alignment and you are seriously in business.
Hope this helps!