I've tried over and over again on the data I captured this morning and I keep getting this.
Registax started going funny when I was working on Mars last night, it took 4 tries at stacking and finally had to do a reload of the software to get a final image out of it.
why why why why ????
For planets in my case it always works fine if you align by center of gravity, if you use align points it does funny things.
If you are already using center of gravity and the results are still bad one workaround is to use Avistakker2 to stack and then load the result in Registax6 for wavelets and final processing.
Avistakker works fine and is fast. I use it for moon images.
Nettie, that type of artifact looks like it could be one of two things.
1. You are using multiple alignment points and the alignment "boxes" are too close together or overlapping. try spacing them out or using smaller alignment boxes.
2. You have some dropped frames in your video which are included as black frames. MY DMK used to drop dropped frames completely from the video, buit I notice with the newer drivers it keeps them in there but they are black. There's a couple of things you can do here:
a. If you are using a webcam type camera, make sure your HDD has plenty of free space and is defragged. I actually get rid of all my previous session files off my lappy so it doesn't waste time looking for a clear sector (which may cause dropped frames).
b. Once you have dropped frames in your video, try alternate initial alignment frames to see if you can stop registax from picking them up. Also try making a reference frame from say the best 10 frames before optimising. Often I find the reference frame will pick up dropped frames, but the final optimisation pass won't. It doesn't work all the time, but you try all sorts of thing to recover data, don't we?
As for the number of frames selected, where are you telling to select the best 2000? Are you using registax 6 (cause I have no experience with it yet)? registax will usually cut off at a specified quality, but you can over ride it by manually moving the cut off slider before you select Limit on the Align tab.
Al, the data is from my Canon 550d. I'm using the same settings as I've always used with Registax. Which makes me think it's the data causing the problems.
I've spent literally hours and hours trying to find out what is going wrong here, and why.
It's strange how this has happened all of a sudden eh.
I might try reconverting my .mov file.
When I switched from registax 5 to 6 - one simple thing that caught me out is you have to click the 'set alignment points' tab at the top left after loading the avi. Then you slide the slider across until you've got somewhere from 60 to 100 and let it go. I've found for planets the defaults are pretty good. Of course, if your data manifests excessive awesomeness, you may need to apply an appropriate pre-filter
cheers,
Andrew
Good call - just downloaded and tried autostakkert on yesterday's solar mosaic. It's as close to idiot proof as I need - absolutely painless. One question - what do you use for post processing then? It seems I still need registax for the wavelet enhancement step? (Sorry for the attempted thread hijack..)
cheers,
Andrew.
I'm onto my 4th codec, trying to find one that AS!2 will read.
Any suggestions would be appreciated.
Am downloading Castrator now. Hoping this will help. lol Castrator won't read any of the .avi's either.
Update. Managed finally to get AS!2 to accept .bmps.
I use avidemux to convert the Avi to mpeg4 encoding then use castrator to read that and the output of castrator is friendly to both Avistakker2 and Registax.