Fixed unable to press Cancel button in batch processing. Fixed caption of frame view in batch processing. Fixed caption of frame number at bottom left, it didn’t update properly in batch processing. There should be no more lockups caused by out of memory on 32-bit OS. AS!2 is now aware of OS limitations on amount of memory available per process. The default location works 95% of the time, but sometimes AS!2 surface alignment loses track because there is nothing interesting to see in the center of the screen. You should set it around a feature that stays in the FOV at all times. Added option to manually set coarse alignment window location in surface mode. Changed name of Coarse Alignment to Image Stabilization, which makes a bit more sense. Whether or not I do something with those suggestions depends on 1) my mood, 2) if I'm convinced it makes sense, 3) how time consuming it will be to implement. You can use the software or make suggestions either way Of course donations are appreciated, but remember that you don't HAVE to donate. as you commented earlier, one can go on a merry-go-round with all this trialling and analysing - but then again you programmers most probably think that's a wondrous pastime.! Hmmmmm.Well, image distorting is a major element of the weird seeing effects we've been experiencing here, and AS edge alignment might prove beneficial thereon (I haven't done those trials yet - sleep (or lack of it!) got the better of me last night.)īut don't forget that Ninox does offer several other command line switches/function variations such as altering the number of downsampled images it takes it's particular form of Gradient2 quality estimation from and "-dbf=planet" which is for discarding badly-formed frames (both of which have no impact with the particular problem I've encountered of late alas! )Īlso there's the morphing switches/commands.hmmm, maybe they are actually "anti-morphing" controls and these are my next stage of inclusion in the Ninox-regulated processing comparisons which should be stacked up against AutoStakkert!'s performance in various modes - time to get to work but I have to confess that pre-processing as well as processing with my current regimens makes for a super-workload (why I haven't tried the morph switches in Ninox to date - Registaxing for the morphing sample, then Ninoxing, then final Registaxing!) so I hope I find some genuine satisfaction/advantages in your program Emil: a pity wavelet sharpening isn't part of your software, but if it really does run very fast then that's a real bonus. Interesting comments Emil: strangely, I'm finding Ninox isn't handling my Mars capture so far at all well and I've put that down to the peculiar type of seeing myself and another AA'er here in South Australia have noticed a lot so far this apparition.MAP just isn't producing acceptable results in R6 using Gradient2 and I've had to resort to C of G alignments - I'm still Ninoxing but loading all the bmp's into R6 because regardless of MAP or C of G Registax is determining quite different quality selections, and am really only using Ninox to speed the R6 process up by virtue of the cropping & centring functions.Ĭontrary to one of your comments above, I haven't had any problems using Ninox with the larger targets in recent time, such as Saturn at present and Jupiter a month or so ago.it's little Mars that is troubling Ninox.and the seeing between Mars and Saturn shoots has been pretty much the same so that doesn't seem to be a differentiating factor for those 2 at least.īut I'm about to give AS a go in a few minutes, and the points you've already made plus those in your last post about SAP & MAP, and particularly AP's in general are good to know beforehand - will report back when I think I have something to comment further about.!
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |