Tips needed to remove "muddy" appearance of Jupiter

[chiltonstar]

Tips required please>

Whatever I do, I always end up with slightly muddy looking Jupiter images - any tips on getting better results at the software stage. Image best of 3000 frames two nights ago (average seeing only), Mak 180, ASI224, then PIPP, Registax and PS Elements.

Chris

[Grotemobile]

I think U have done very well there. A lot of it is down to the seeing.

I see U have got a moon there as well.  A lot better than I am getting.

[Owmuchonomy]

I'm wondering why have you used PIPP? 

[chiltonstar]

38 minutes ago, Owmuchonomy said:

I'm wondering why have you used PIPP? 

...mainly to stack multiple avi's, crop and centre - cuts down the processing time in Registax too, which can be lengthy with my normal home lappy.

Chris

[Owmuchonomy]

Ok. I moved on from all that to using Autostakkert.  It does it all in one pop and with a much easier interface. The only thing I refer back to Registax for is RGB align.  Unlike most, I don't use wavelets either as it smashes the hell out of my data.

[spaceman_spiff]

Hi Chris,

I'm not sure what you mean by muddy exactly, the stack looks good to me. Perhaps there is some smearing from Jupiter's rotation. Can you up the frame rate and shorten the recording time? Maybe try 640x480 at 300fps with a recording time of 30s, to give 9000 frames. Then use pipp to extract the best 2000 and then run them into Registax, this should give a sharp result.

Also, maybe try a good Barlow lens to extract all the detail, with the 2700mm focal length, adding a Barlow will give a big image scale.

HTH Dan

[chiltonstar]

Thanks for these replies:

Chris: I've just tried AS and although it's slow (no patience I'm afraid) it is sharper and cleaner looking, so clearly the way ahead! For example, one avi extracted below (Jupiter, Europa and Ganymede)

Dan - I do use a Barlow (x1.5) screwed into my flip mirror, but I had to take it out this time because the seeing wasn't good enough for f27!

Chris

 

[AKB]

The last week or so is the first I've ever tried to image Jupiter, so any tips welcome too!

I stack in AS2! then do some colour adjustments and unsharp masking in Nebulosity.  Looks like you might be hitting RegiStax wavelets quite hard?

Here's one I got on March 25 at 22:47 UT, for comparison... I think you have a bit more detail than I do (C9.25 with ASI120MC.)

 

[ronin]

My offering is take a shorter movie, say 60 seconds and stack the best 300 or 500.

If I recall Jupiter rotates too fast and after something like 90 seconds then the surface features have mnoved too much so nothing aligns quite right and I suppose you get this "muddy" image.

It is a memory and I think the max time was estimated at 90 seconds but maybe try it and see.

[chiltonstar]

On 3/27/2017 at 16:32, ronin said:

My offering is take a shorter movie, say 60 seconds and stack the best 300 or 500.

If I recall Jupiter rotates too fast and after something like 90 seconds then the surface features have mnoved too much so nothing aligns quite right and I suppose you get this "muddy" image.

It is a memory and I think the max time was estimated at 90 seconds but maybe try it and see.

Less than 90 secs certainly sharpens the stack a little - thank you for the tip, eg a couple of nights back. Amazing how much the GRS moves between avi's a couple of minutes apart!

Chris

 

 

[CraigT82]

I have just begun to experiment with sharpening the RGB channels individually, I stack the colour image, then split the channels apart and sharpen each individually before recombining.  This ismy results so far (only tried it on this one image as that's all I've got from this scope/cam combo - 150 mak and ASI185mc)

First image is original, second is the split and recombined data.

[AKB]

24 minutes ago, CraigT82 said:

I have just begun to experiment with sharpening the RGB channels individually, I stack the colour image, then split the channels apart and sharpen each individually before recombining.  This ismy re

Wow!  That's a big improvement... definitely worth a go.

[Freddie]

At that image scale you wouldn't have a problem with 2min AVIs. Seeing, the number of frames from the AVI you stack and maybe focus and collimation are going to be your main issues, not the length of a single AVI. You have to take into account image scale when looking at the length of AVI, most people forget that and think one duration applies to all set-ups.

[Stub Mandrel]

If your brain can take the strain, take a series of relatively short videos, process each one, then use WinJupos to create a 'stack of stacks'. here's Jupiter from last week:

2017-03-25-2253_8_pipp_g4_ap26_Resample20.tif:

Six two-minute sessions 'de -rotated by Winjupos'.

The difference is subtle, but the second is less noisy with fewer artefacts, rather than more detailed.